Guide · 6 min read · updated 2026-11-09
Compressing images: what actually makes a file big, and where the visible damage starts
Which settings cost bytes, which cost detail, and how to pick a quality level for the web, email or a size limit — with the reasoning behind each number.
ToolDock is free and shows ads. Google and its partners may use cookies to serve and measure them.Privacy Policy
Where the bytes actually are
An image file is mostly a record of detail: dimensions multiply, and fine texture costs more than smooth areas. That is why a photo of a forest is five times the size of a photo of a clear sky at identical dimensions — there is simply more information to store. Practical consequence: the cheapest reduction is usually fewer pixels, not a lower quality setting.
A 6000-pixel-wide photo displayed in a 1200-pixel column is wasting four-fifths of its pixels. No quality slider can recover that waste efficiently, because you are paying to store detail the screen will never show.
What the quality setting really does
For JPG and WebP, quality controls how aggressively fine colour and texture detail is discarded. The relationship is not linear:
- 90 to 100: effectively transparent changes, and a large file. Useful only for images that will be edited again.
- 75 to 85: the practical range for photographs. Most people cannot pick the compressed version in a side-by-side at normal size.
- 60 to 75: a visible softening in detailed areas, but fine for thumbnails, backgrounds and small on-screen images.
- Below 50: blocky patches around edges and a muddy look in gradients — the point where compression becomes the most noticeable thing about the picture.
Resize before you compress
If an image is destined for a specific place — a 1200-pixel article header, a 400-pixel avatar, a 1600-pixel product photo — resize to that width first, then compress to taste. Doing it the other way round either wastes quality on pixels that will be thrown away or forces a harsh quality setting to hit a size goal the dimensions already solved.
For hard limits ("must be under 500 KB"), work backwards from the number: a target-size compressor tries quality first and drops dimensions only when it has to, and reports what it managed so you can judge the result rather than trusting it blindly.
Format is a compression decision too
Choosing the container changes the baseline. WebP is typically 25 to 35 percent smaller than JPG at comparable quality and is supported by every current browser. PNG is the right choice for screenshots, line art and anything with transparency, but a photograph saved as PNG is often larger than the original JPG. For graphics with few colours, PNG's lossless compression wins outright over a lossy format at high quality.
One habit worth keeping: compress a copy, never the only copy. Each lossy re-save compounds, so the original is what you compress from next time.
Do it now
Ready to try it? The Compress image tool does exactly what this guide describes.
Open Compress image →Keep reading
iPhone photos arrive as .heic: what that means and when to convert them
Why iPhones save HEIC, which apps and websites still reject it, and how to convert HEIC to JPG in your browser without losing quality.
How to make a PDF smaller without ruining it
Why PDFs balloon in size, what quality loss actually looks like at different compression levels, and how to hit upload limits like 2 MB or 300 KB.