Why Does Compressing an Image Make It Bigger?
Compression is supposed to shrink a file. Sometimes the output is the same size — or larger — and that is not a bug in the math. Re-encoding already-tight JPEGs at high quality, saving a photo as PNG, or running Max quality with no resize can add container overhead without buying smaller pixels. Image Compressor is honest about it: when total output bytes are not below the input, it shows a warning-style result (“output is not smaller. Try WebP or a lower quality”) instead of a fake green “Compressed.” This guide explains why that happens and what to change. For the general pipeline (lossy vs lossless, resize-first, quality ranges), see How to Compress Images for the Web — this article is only about the “got bigger” case.
Compression rewrites the file — it does not guarantee fewer bytes
Image Compressor uses browser-image-compression in a Web Worker. It decodes your PNG, JPEG, or WebP, then re-encodes with initialQuality from the quality slider (presets: Max quality ≈ 92, Balanced ≈ 75, Max compression ≈ 45); optional longest-edge downsampling — none in Max quality, 4096px in Balanced, 2048px in Max compression; and output fileType auto, JPEG, PNG, or WebP.
If the new encoding is less efficient than the original (or the same efficiency with extra overhead), the download grows. The tool compares batch totals: smaller → success; not smaller → info warning with the WebP / lower-quality hint. Per-file size that grew is also flagged with a warning tone in the UI.
Common reasons the file gets bigger
| Cause | What happens | What to try |
|---|---|---|
| Already-optimized JPEG, high quality | Re-encode at ~90+ quality rebuilds the stream; Huffman tables and padding can exceed the old file | Lower quality (try Balanced / ~75), or switch output to WebP |
| Photo saved as PNG | Lossless PNG on photographic noise is huge; “compressing” to PNG often stays large or grows | Use JPEG or WebP, not PNG, for photos |
| Format / quality mismatch | Forcing PNG, or auto picking a poor path for the content | Set output to WebP or JPEG explicitly; drop quality a step |
| Max quality, no downsampling | Pixel dimensions stay full size; only a gentle re-encode runs | Use Balanced or Max compression so longest edge is capped, or resize first |
| Tiny / already-tiny assets | Icons and heavily optimized web images have little left to remove | Keep the original; further passes rarely help |
What Image Compressor will not do
GIF and SVG are rejected with a clear message — they are not silently “compressed” into a worse file. Use PNG, JPG, or WebP as inputs. Convert Image is the place for SVG or GIF rasterization if you need a still frame.
How to shrink an image that just got bigger
Fix a compression pass that grew the file
Work in the browser; change one lever at a time and compare sizes.
- 1
Open Image Compressor
Go to /tools/image/image-compressor and drop the original (not the oversized output), if you still have it.
- 2
Read the result status
If you see “output is not smaller…”, treat that as the signal to change settings, not to download and re-upload the larger file.
- 3
Switch format to WebP (or JPEG for photos)
Avoid PNG for photographs. Prefer WebP when browsers in your audience support it.
- 4
Lower quality one step
Move from Max quality toward Balanced (~75) or Max compression (~45) and compare.
- 5
Allow downsampling when dimensions are large
Balanced (4096) or Max compression (2048) caps the longest edge; Max quality does not.
- 6
Stop when the warning clears
Keep the smaller output; do not loop the same file through high-quality re-encodes.
Image Compressor
Re-encode JPG, PNG, and WebP in the browser with quality and format controls — and an honest “not smaller” warning when the pass did not win.
How this differs from the general compress guide
How to Compress Images for the Web covers when to use lossy vs lossless, resize-before-compress, and quality ranges for sites. This page assumes you already compressed and the size went the wrong way — fix format, quality, and downsampling, and trust the tool’s size check.
Common mistakes
Re-compressing the larger output at Max quality
Artefacts stack and size may keep climbing. Start from the original file.
Choosing PNG because it “sounds safe” for a photo
Lossless PNG on camera noise is the wrong container if your goal is a smaller download.
Ignoring the “not smaller” message
That status is intentional. Change settings instead of assuming the tool failed silently.
Expecting GIF or SVG to shrink here
Those types are unsupported inputs and are rejected with an explicit error.
Best practices
- Always keep the original until size and visual quality both look right
- Change one setting per pass (format, quality, or mode)
- Prefer WebP for another attempt when JPEG-to-JPEG at high quality failed
- For huge pixel dimensions, use a mode that caps longest edge, or resize before compress
Frequently asked questions
Why did compressing my image make the file bigger?
Re-encoding can be less efficient than the original stream — especially an already-optimized JPEG at high quality, or a photo forced into PNG. The new file is valid; it is just not smaller.
Does Image Compressor hide that and still say “Compressed”?
No. When total output bytes are not below the input, it reports that the output is not smaller and suggests WebP or a lower quality — not a false success.
Should I use Max quality to avoid this?
Max quality (~92) with no longest-edge cap is the mode most likely to grow an already-small JPEG. Use it when you need near-original fidelity and accept little or no size win — not as the default shrink pass.
Will WebP always fix a size increase?
Often it helps versus JPEG or PNG at similar visual quality, but not always. Still lower quality or downsample if WebP is also larger.
Can I compress GIF or SVG here?
No. Those types are rejected with an explicit error so they are not mishandled. Use PNG, JPG, or WebP.
Does compressing upload my images?
No. Image Compressor runs in the browser (Web Worker). Prefer local tools for sensitive photos.
Put this into practice
Image Compressor runs entirely in your browser — no upload, no account, no limits.
Open Image CompressorRelated tools
Related guides
How to Compress Images for the Web
A practical guide to image compression: lossy vs lossless, choosing quality levels, resizing before compressing, format choice, and compressing images in your browser.
PNG vs JPG vs WebP: Which Image Format to Use
Compare PNG, JPG, WebP and AVIF on compression, transparency, quality and browser support, with a simple decision guide for photos, screenshots, logos and animation.
Compress PDF Without Losing Quality
Honest guide to shrinking a PDF without wrecking it: Lossless (small safe savings), Compress images (re-encode photos, keep text selectable), and Rasterize (biggest savings, flattens pages). Pick the mode that matches your file.
How to Compress a PDF Without Wrecking the Quality
Understand what actually makes a PDF large, which compression settings matter, how much size you can realistically save, and how to compress a PDF privately in your browser.
How to Format Large JSON Files Without Your Browser Freezing
Why JSON formatters freeze on big files — and how a browser tool stays usable: 12MB live-analysis cap, size-scaled debounce, deferred tree/stringify, plaintext highlighting above 1.5MB, and on-demand nested/duplicate scans.
CSV vs JSON: Choosing the Right Data Format
Compare CSV and JSON on structure, nesting, file size, streaming, typing and tooling, with clear guidance on which to use for exports, APIs and analytics pipelines.