Why did my image get bigger after compressing it?
Updated
Compression is not a shrink guarantee. A JPEG re-encoded at a higher quality than the original often grows. Saving a JPEG as PNG stores noisy photo pixels losslessly, so the file usually gets larger. EditItAll shows the real in → out size after each pass — set quality, read it, and adjust. Nothing is uploaded.
Do it now — free, in your browser
Open the image compressorCompression does not promise a smaller file
A compressor re-encodes pixels. Whether the new file is smaller depends on the format, the quality you ask for, and how the original was already encoded. If the input is a tightly saved JPEG and you ask for a looser one, the encoder spends more bits and the file grows. That is expected, not a broken export.
EditItAll does not have a “make it smaller no matter what” switch. The controls are a quality slider and an optional max-dimension cap. File size is an output you read on each row of the results list. If out is larger than in, the settings asked for more data than the original stored.
Three reasons the file grew
These are the usual causes:
- Quality higher than the original JPEG. A photo already saved around 70–80, re-encoded at 95 or 100, often comes out larger. Quality 100 cannot restore detail the first encode dropped; it just spends more bytes describing the same pixels.
- You changed format to PNG. PNG is lossless. It will not bring back JPEG detail, and it stores photographic noise exactly, so the file usually balloons. Full diagnosis: why PNG files are so large.
- You only re-encoded, and the original was already small. A 200 KB JPEG of a simple graphic may already be near the floor. A lossless PNG pass on a well-packed PNG can also stay flat or grow by a few bytes of wrapper.
Resizing is a different lever. Leaving dimensions untouched keeps every pixel. If the photo is 4000 px wide and you display it at 800 px, compress after you downscale — or set the compressor’s max-dimension cap. See resizing vs compressing.
How to actually shrink it in your browser
Open the image compressor with the original, not the copy that grew:
- Photograph. Stay on JPG or switch to WebP. Start near quality 80, read in → out, and lower the slider until the listed size is under your limit. The readout rounds to whole KB, so aim a notch under a strict byte cap.
- Logo, screenshot, UI with transparency. Stay on PNG. Default PNG recompress is lossless. If the file still will not move, it may already be well packed — converting a photo PNG to JPG is the size win, and that step is lossy.
Work runs on your device. Nothing is uploaded, EXIF is stripped on export, batches download as a ZIP, and the page still works offline after it loads. More recipes sit in the compressing images cluster.
Ready to try it?
Free, no sign-up, and nothing you open ever leaves your device.
Frequently asked questions
Can compressing an image make it larger?+
Yes. Re-encoding a JPEG at a higher quality than the original, or saving a JPEG as PNG, often increases the file size. The compressor did what you asked — it stored more data, not less.
I set quality to 100 and the JPEG got bigger. Why?+
Quality 100 asks the encoder for a very expensive file. If the original was already a typical camera or phone JPEG, that request is higher than the source, so the output grows. It does not restore lost detail. Start near 80 instead.
Does EditItAll guarantee a smaller file?+
No. There is no target-size field and no “always shrink” mode. You set quality and an optional max dimension, then read the in → out size. If out is larger, lower quality or change format.
Should I compress the bigger copy again?+
Compress from the original. Running another pass on the enlarged copy stacks JPEG damage and may not get you back to the first file’s size. Keep a master and export delivery copies from that.
Are my images uploaded when I compress them?+
No. Compression runs entirely in your browser. Files never leave your device, and you can disconnect after the page loads.