Why your phone photo is 8 MB

More pixels than you think

The obvious cause first. A phone from 2010 took five-megapixel photographs. A current one defaults to twelve and can be set to 48 or higher. That is roughly ten times the pixel count, and file size scales with pixel count, so the same scene captured today produces a much larger file before anything else is taken into account.

Most phones do not use their maximum resolution by default, because the top setting produces files that are unwieldy for very little visible benefit. If yours is set to 48 megapixels and you keep hitting upload limits, turning that back down solves the problem at source.

Computational photography adds detail that costs bytes

This is the less obvious half, and it is now the bigger factor. A modern phone does not take one photograph when you press the button. It captures a burst of frames at different exposures and merges them, aligns them to cancel out hand shake, applies noise reduction, and sharpens local detail.

The result is an image with much more fine detail than a single exposure would contain: texture recovered from shadows, highlights that are not blown out, and edges enhanced everywhere. Fine detail is exactly what image compression finds expensive. A processed photograph has more real information in it than a plain one, so it compresses less well — the file is larger because the picture genuinely contains more.

Aggressive sharpening compounds this. Sharpening works by increasing contrast at edges, which creates high-frequency content across the whole frame, and high-frequency content is the most expensive thing a compressor has to store.

Higher bit depth and wider colour

Phones increasingly capture in wider colour spaces, such as Display P3 rather than the older sRGB, and some store more precision per channel. Both give better colour reproduction on displays that can show it, and both mean more data per pixel.

HDR photographs go further, storing brightness information beyond what a standard image can represent, often in an additional layer alongside the main picture. That extra layer is invisible on older software and adds real bytes to the file.

Metadata is small but not nothing

Every photograph carries EXIF metadata: camera model, lens, exposure settings, the date and time, and usually the GPS coordinates of where you were standing. Some phones embed a thumbnail preview as well, and depth or portrait-mode data can add more.

In size terms this is typically tens of kilobytes rather than megabytes, so it is not why your file is 8 MB. It is worth removing for a different reason: the location of your home is embedded in every photograph you took there, and it travels with the file when you send it to a stranger. Re-encoding an image strips all of it, which FileBelow does as a side effect of processing.

The gap that causes the problem

None of this would matter if upload limits had moved. They have not. A 2 MB maximum was generous in 2010 and is restrictive now, but changing it means touching a working system, so the default has been inherited through years of software.

The practical consequence is that the gap between what your camera produces and what forms accept is wider than it has ever been, and it is still widening. Compressing before uploading has gone from an occasional nuisance to something most people have to do.

What to do about it

In the moment, compress the photograph to the limit the form gave you — that is what this site is for, and giving up some resolution is nearly always a better trade than crushing the quality.

In general, if you hit this constantly, check your camera settings. Reducing the capture resolution one step and, on an iPhone, considering whether HEIC or JPEG suits you better, will remove most of the friction before it starts.