Compress JPG, WEBP and PNG images directly in your browser by quality or exact target KB.
Drag and drop an image here
Click to browse from your device, or press Ctrl+V to paste from clipboard
Supports JPG, PNG and WEBP · Processed locally in your browser
Original size
—
Compressed size
—
Saved %
—
Dimensions
—
When the form limits pixels as well as bytes, set the required dimensions with Resize Image.
Compress JPG, PNG and WebP images online using a manual 10–100 quality slider or an exact target size in KB (20 KB, 50 KB, 100 KB, 200 KB or custom) — every result is measured in real bytes inside your browser.
Whether you need to compress an image to 100 KB for an online application form, shrink a signature or ID photo to 50 KB or 20 KB, or reduce hero images under 200 KB for faster web pages, switch 'Compress by' to 'Target size in KB'. The compressor runs a binary search over encoder quality — and steps pixel dimensions down when needed, such as scaling a 3000 × 2000 camera photo toward 1200 × 800 when a 50 KB cap cannot be reached by quality alone — until the actual encoded file lands at or below your KB limit.
When you look for an image reducer or image size reducer, you are usually trying to reduce the stored byte count (in KB or MB) so a portal accepts the upload or a webpage loads faster. Quality mode reduces bytes by adjusting lossy quantisation while keeping your original width and height untouched. If your image also needs specific pixel dimensions (such as 1200 × 800 px or a passport/exam frame), set the dimensions first in Resize Image or Indian Exam Photo Resizer, or read how to reduce image size in KB.
PNG is lossless, so re-encoding a PNG as PNG at the same dimensions rarely saves much. The largest byte reduction on a photographic PNG comes from switching output to WEBP (which keeps transparency) or JPG, with a live comparison of the exact byte counts before you download.
Every compression pass encodes the file in your browser and reports its exact byte size against the original — never a formula-based guess. If a setting makes the file bigger, the result panel says 'Larger' instead of hiding it.
Keeping the original format is the safe default. For PNG uploads you can choose PNG — lossless, WEBP — smaller (preserving transparency), or JPG — smaller (with a Background colour picker); for JPG uploads you can keep JPG — smaller or switch to WEBP — smaller.
Quality mode keeps the source pixel dimensions and uses the 10–100 quality slider (for JPG or WebP output). Target size in KB offers 20, 50, 100, 200 and 500 KB quick-pick buttons or any custom ceiling from 5 KB up, searching encoder quality first and stepping dimensions down when needed.
75–85 covers most web images. Text-heavy or large hero images look better at 90+; below 70 you'll notice banding in skies and haloing around edges.
That's normal — PNG is lossless and a well-encoded original leaves little to gain. Switch the output format to WEBP or JPG, or use Target size in KB mode to see a real reduction.
Each lossy pass adds permanent damage on top of the last. Start again from the original file and pick a lower quality in a single pass instead.
This happens when the source was already efficiently compressed. Keep the original in that case — the result panel flags it as 'Larger' rather than a saving.
Target-KB searches and quality adjustments run in a loop inside your browser tab against a local copy of your image. Your file is never uploaded to a compression queue. Refreshing removes the unsaved preview and selection, leaving downloaded files intact. Usage analytics may include format and approximate megapixels, not your photo or filename.
Very low quality settings show visible blocks and smudged edges.
Full details are in the Privacy Policy.
Compression is not the fix when a portal rejects your photo for its pixel dimensions or proportions; resize or crop first, then compress.
Avoid pushing quality very low on photos containing faces or small writing that someone must read, such as ID cards. Check the preview at full size before you submit.
75–85 covers almost every web use. Go to 90+ for images displayed large or containing text; below 70 you'll see banding in skies and halos around edges.
Yes. It's computed from the byte length of the encoded output against your original file, not estimated from the quality setting.
When you switch to Target size in KB and enter a ceiling (such as 50 KB or 100 KB), the tool runs a binary search over encoder quality — and steps dimensions down if needed — to bring the encoded file at or below your limit (or the smallest size achievable within the quality and scale floor, with the exact byte count shown in the result panel).
No. Standard Quality mode keeps the exact width and height of your source image and only adjusts encoding compression.
Reducing file size in KB lowers the stored byte weight of the file using compression, whereas resizing changes the width and height in pixels. In Target size in KB mode, this compressor adjusts encoder quality first and only reduces pixel dimensions if quality alone cannot reach your KB limit.
JPG and WebP use lossy compression controlled by the 10–100 quality slider (JPG flattens transparency onto your chosen background colour, while WebP preserves 8-bit alpha transparency and verifies the RIFF/WEBP header with a local WebAssembly fallback). PNG is lossless, so re-encoding a PNG as PNG at the same dimensions often saves little — to shrink a PNG significantly, either switch Output format to WebP/JPG or use Target size in KB mode so the tool steps dimensions down until the PNG fits.