Compress an image to 500 KB

Where the 500 KB limit comes from

Half a megabyte is the point at which limits stop being about storage and start being about page speed. It is a common ceiling for images on a website, for forum and community avatars, for email signatures, and for marketplace listing photos on platforms that care how fast their pages load on a phone. It also turns up on older government and institutional forms that were sized for the connections of twenty years ago and never revisited.

This is the first limit on the way down where a modern photograph genuinely cannot pass untouched. A phone photo is five to fifteen times this size. Something has to go, and the interesting question is what.

This is where the two-axis search earns its keep

At 2 MB, compressing a little harder is enough and nothing else is needed. At 500 KB that stops being true. Holding a 12-megapixel photo at full resolution and forcing it into 500 KB means roughly 0.04 bits per pixel, which is far below what JPEG needs to represent detail. The result is visible: eight-by-eight blocks in smooth areas like sky and skin, ringing around hard edges, and fine texture reduced to mush.

Halve the dimensions first and the same 500 KB now covers a quarter as many pixels, so each one gets four times the data. The image is smaller on disk in terms of resolution, but far cleaner. On a screen — where nearly all of these images end up — the second version looks obviously better.

Which trade is right depends on the photograph, so FileBelow does not guess. It encodes candidates at several resolutions, scores each against your original, and keeps the winner. On our own test photograph, at this limit the two-axis result scores meaningfully higher than a quality-only search at the same 500 KB.

What usually goes wrong

The classic mistake is repeated compression. You compress once, it is still too big, so you take the already-compressed file and compress it again. Each pass encodes the previous pass’s artefacts as though they were real detail, so the damage compounds and the file barely shrinks. Always start again from the original.

The second mistake is leaving the format alone. At 500 KB, WebP typically carries noticeably more detail than JPEG for the same number of bytes. If your destination accepts WebP, it is close to a free improvement — and after a JPEG result FileBelow measures whether WebP would actually be better for your specific image and offers a one-click switch when it is.

If it still will not fit

At 500 KB the usual blocker is a minimum dimension. If a form insists on a large image and a small file at the same time, one of the two has to give, and FileBelow will tell you the dimensions that would work instead of failing quietly. PNG sources are the other blocker: converting to JPEG or WebP is nearly always the answer.