Image dimensions vs file size: why a bigger picture isn't always a bigger file
Pixels, quality and format each move file size independently. Understanding how they interact stops you fixing the wrong one.
Published Updated 6 min read
It's tempting to assume file size and pixel dimensions are the same thing, because they usually move together. They aren't the same thing. Dimensions describe how much information an image contains before compression; file size is what's left after format and quality have done their work. A 3000×2000 image can be smaller than a 1000×700 one if the first is a heavily compressed JPG and the second is an uncompressed PNG of a noisy photo.
Three independent levers
- Dimensions — total pixel count. Halving width and height removes roughly 75% of the pixels and, usually, a similar share of the file size.
- Format — JPG and WEBP discard information the eye barely notices; PNG keeps everything. This alone can be a 5–10x difference on a photograph.
- Quality setting — within a lossy format, how aggressively detail is discarded. Diminishing returns kick in fast above about 85.
Why a PNG won't shrink no matter what you try
PNG has no quality dial — it is lossless by definition. Running a PNG through a 'compressor' with nothing else changed will produce a file roughly the same size, sometimes even fractionally larger, because a competent encoder already found a near-optimal lossless representation. The only ways to actually shrink a PNG are to reduce its dimensions, reduce its colour count, or convert it to a lossy format like WEBP or JPG.
Which lever to pull first
Dimensions first, always. It's the only lever that reduces file size with zero quality trade-off, provided you're not displaying the image larger than the new size. Format comes second — moving a photo from PNG to JPG or WEBP is close to a free win. Quality is the last lever to touch, and the one to touch most gently, because it's the one most likely to introduce visible artefacts.
A practical example
| Step | Dimensions | Format | Quality | Approx. size |
|---|---|---|---|---|
| Original camera photo | 4032×3024 | JPG (camera default) | ~95 | 4.8 MB |
| After resizing to display size | 1600×1200 | JPG | ~95 | 650 KB |
| After converting format | 1600×1200 | WEBP | ~95 | 480 KB |
| After tuning quality | 1600×1200 | WEBP | 80 | 140 KB |
Each step targets a different lever, and each one is measurable — that's the point of doing them in order and checking the byte count after each, rather than guessing at a single quality number and hoping.
Tools for this
- Resize ImageUse it the dimensions lever — usually the biggest single saving.
- Image CompressorUse it the quality lever, with the byte count visible as you adjust it.
- JPG to WEBPUse it the format lever, often free of visible quality loss.
- PNG CompressorUse it to see why a PNG resists shrinking without a format or dimension change.
Keep reading
- How to reduce image file size without wrecking the pictureMost oversized images are oversized for one boring reason: the dimensions are far larger than anywhere they're displayed. Fix that first, then compress.
- How to resize an image without stretching, blurring or cropping the wrong partResizing looks trivial until the aspect ratio doesn't match and something gets squashed. Here is how to do it properly, every time.
- Understanding image quality and compression settings'Quality 80' means something different in every tool and every format. Here is what the number actually controls, and how to use it with confidence.