Skip to content

Resize or lower the quality? Which shrinks an image file more, measured

7 minutes, updated 2026-11-19

When a photo is too big for a form or an email, you have two levers: fewer pixels, or a lower quality setting. Both make the file smaller, and both cost something. This guide measures how much each lever saves, works through two real targets, 100 KB and 50 KB, and explains the order of steps that gives the cleanest result.

How we measured: on 19 November 2026 we took three public-domain NASA photographs, each 1920 pixels wide, and saved them with Chromium's built-in JPG encoder, the same one the tools on this site use in your browser. Each photo was saved at full size at qualities from 95 to 30, and resized to 1280, 800, 600 and 400 pixels wide at qualities 80 and 60. A synthetic 1440 × 900 screenshot was measured alongside for the format comparisons. The worked examples use the two photos that are exactly 1920 × 1536: a crew group portrait with lots of fine detail, and an astronaut with two dogs in front of a soft painted backdrop. Sizes are in KB of 1024 bytes.

How to read the fidelity figures

Fidelity is given as PSNR in decibels (dB): above 40 is hard to tell from the source, 35 to 40 is good, 30 to 35 shows on close inspection, below 30 is obvious. One caution matters for this guide. At each reduced width, PSNR compares the saved file with the resized picture before encoding. It measures the damage done by compression, and it does not count the fine detail removed by having fewer pixels. Keep that in mind when a small image scores close to a large one.

Lever one: lower quality at full size

From 80 down to 30, the files shrank to about a third (32% and 30%), and the busier crew photo ended below 30 dB, where blocks are obvious. Even at 30, neither file came near 100 KB. In the range we measured, quality alone could not bring a 1920 × 1536 photo to a typical form limit.

QualityCrew (KB)Crew (dB)Dogs (KB)Dogs (dB)
8063836.449038.8
7039433.130234.9
6034432.426034.2
5030631.423333.1
4024630.818132.5
3020329.814631.6

Lever two: fewer pixels

Going from 1920 to 800 pixels wide at quality 80 made both files about six times smaller (638 to 109 KB, and 490 to 80 KB). Going from quality 80 to 30 at full size made them only three times smaller. Per kilobyte saved, fewer pixels is the stronger lever by a wide margin.

At quality 60, file size followed pixel count closely at first: at 1280 × 1024 the files kept 45 to 47% of their bytes with 44% of the pixels. At the smallest sizes bytes fell more slowly than pixels (about 7% of the bytes at 400 × 320, with 4% of the pixels), because each remaining pixel carries more of the picture's detail.

The same effect shows in the fidelity. At quality 80, the crew photo measured 36.4 dB at full size, 31.8 dB at 800 pixels and 29.6 dB at 400; the dog portrait went from 38.8 to 34.6 to 32.5 dB. A small image is denser, so the same setting does more visible damage. The practical rule: when you reduce the pixel size, keep the quality up. Do not pull both levers hard at once.

Size (px)Pixels (% of full)Crew at 80 (KB)Crew at 60 (KB)Dogs at 80 (KB)Dogs at 60 (KB)
1920 × 1536100638344490260
1280 × 102444247161188116
800 × 64017109738051
600 × 4801068454832
400 × 320434232517

Worked example: a 1920 × 1536 photo to 100 KB

The dog portrait reaches 100 KB comfortably at 800 × 640 and quality 80: 80 KB at 34.6 dB, with room to spare. The crew photo at the same settings is 109 KB, just over. It fits at 800 × 640 and quality 60 (73 KB, but 29.7 dB) or at 600 × 480 and quality 80 (68 KB, 30.8 dB). The best answer lies between those two sizes at a quality in the 70s, which is exactly the kind of in-between point the fit-to-size tool finds by trial.

Notice how different two photos of the same size are. At 600 × 480 and quality 80 the crew photo was 42% bigger than the dog portrait. A group in patterned suits has more detail to store than one face against a soft backdrop, so no fixed recipe of size and quality works for every photo.

Size and qualityCrew (KB)Crew (dB)Dogs (KB)Dogs (dB)
1920 × 1536 at 3020329.814631.6
1280 × 1024 at 6016131.311633.7
800 × 640 at 8010931.88034.6
800 × 640 at 607329.75132.7
600 × 480 at 806830.84833.7
600 × 480 at 604528.83231.9
400 × 320 at 803429.62532.5

Worked example: the same photo to 50 KB

At 50 KB the dog portrait fits at 600 × 480 and quality 80: 49,611 bytes, under both the 1000-byte and the 1024-byte reading of the limit, at 33.7 dB. Its 800 × 640 version at quality 60 was 52,257 bytes, just over. The crew photo needs either 600 × 480 at quality 60 (45 KB, 28.8 dB) or 400 × 320 at quality 80 (34 KB, 29.6 dB).

The honest trade-off: at 50 KB a 1920 × 1536 photo keeps 4 to 10% of its pixels. That is fine for what most 50 KB limits are for, a photo shown at a few hundred pixels on an application, a profile or a thumbnail. It is not enough to zoom in on or to print: 600 × 480 pixels prints sharply at only about 5 × 4 cm at 300 DPI. If the photo will be seen large, the limit is too tight for it, and the right fix is a different destination or a larger allowance, not more compression.

When the pixel size is fixed

Some portals demand exact dimensions or a minimum width. Then quality is the only lever left. For the crew photo at 1280 × 1024, quality 60 was still 161 KB; reaching 100 KB at that size means going well below 60, into the range where blocks show. If the rule is a minimum, use exactly the minimum and no more: every extra pixel is paid for in quality. In the fit-to-size tool, set the required width and height, or switch off the option that allows smaller dimensions, and it will search quality alone. The photo requirements pages list the pixel rules of common portals.

The order: crop, resize, then quality

Crop first, because cropped pixels are ones you did not want. Trimming 20% from each side of a photo keeps 60% of the width and 60% of the height, which is 36% of the pixels, and our measurements show bytes falling roughly in step with pixels. You get a saving similar to resizing while the subject keeps its full resolution. The crop tool does this in the browser.

Resize second, to the size the picture will be displayed at or the size the destination requires. That is the cheap lever: in our data, resizing to 800 pixels wide made the files six times smaller, against three times for dropping quality to 30, and it added no blocks. The resize tool and the resizing guide cover sizes, shapes and print dimensions.

Lower quality last, and only as far as the limit needs. Below 70 each step saved 10 to 30% and cost visible detail, so it is the expensive lever. Do all three in one pass from the original file: every extra JPG save adds its own loss.

Do not resize below the size the picture will be shown at. A 400-pixel image placed in an 800-pixel slot is enlarged by the browser and looks soft, which wastes the quality you kept.

Letting the tool do the search

When you enter a KB limit in the fit-to-size tool, it follows this order for you. It tries quality 95, then 72. If 72 is still too big, it reduces the pixel size to where 72 should fit, but not below 320 pixels on the short side, and only past that point does it lower quality further. Once a size fits, it searches upwards for the highest quality that stays under the limit. The option labelled 'Allow smaller dimensions when quality alone cannot reach the limit' is on by default; switch it off when the pixel size must not change. For the strict case of a 50 KB form there is a 50 KB page with the limit already filled in.

Enter slightly less than the stated limit, because portals count KB in two ways; what KB means on a form gives the safe numbers. How the quality setting itself behaves step by step is in JPG quality vs file size, and the general case for compression is in the image compression guide.

Tools for this

More guides