Why are my photos so large? Megapixels and file size explained

Your phone takes one photo and it lands at five, eight, sometimes twelve megabytes. You try to email it and the attachment bounces back. You upload a batch and the bar crawls. The photo is not broken. Your camera is just handing you far more data than the moment needs, and once you have seen the actual numbers, the fix is obvious.

TL;DR: A pixel needs three bytes to store its colour, so a 48 MP photo is about 144 MB of raw data before anything compresses it. Megapixels set that floor, the format and the amount of fine detail decide how far JPEG can bring it down, and you almost never need full resolution for a screen. The fix is two steps in the right order: resize to the size you actually need, then compress.

Start with the raw byte count, because it is a bit shocking

Most explanations of this jump straight to “more megapixels means bigger files” and leave it there. Here is the number they skip. A single pixel stores three bytes of colour, one each for red, green and blue. A 48-megapixel photo is 48 million pixels, so before any clever storage, that is roughly 144 megabytes of raw colour. A 12-megapixel phone shot is about 36 megabytes raw.

You never see a 144 MB file, because the phone compresses it to a JPEG the instant you press the shutter. But that raw figure is the thing you are actually fighting. Everything from here on is about throwing away the parts of those 144 megabytes you were never going to notice.

Megapixels set the floor

A megapixel is one million pixels, and the count is just width times height. A 48 MP photo is roughly 8000 by 6000 pixels. Double the pixels and you roughly double the raw data underneath, no matter what the picture is of.

The image looks a normal size on your phone because the screen scales it down to fit. That is the trap: nothing about how a photo looks on your screen tells you how heavy the file really is. A big sensor quietly writes a big file every time.

Why your phone captures more than you need

Camera makers add megapixels because detail sells, and detail is real. A high pixel count lets you crop in hard and still keep a usable shot, print large without it going soft, and hold fine texture in a landscape. If you need that headroom, a big sensor is the whole point.

The catch is that you almost never need all of it at once. A photo bound for a text, a website or a social post gets viewed on a screen that shows a fraction of those pixels. Your camera captures for the most demanding case, a large print, and then hands you that same heavy file when you are just sending a snapshot to a friend. That mismatch is where the bloat comes from.

Two levers, and people reach for the wrong one first

Here is the mistake we see most often. Someone takes a full-resolution photo, compresses it hard to make it smaller, and is disappointed it is still over a megabyte and starting to look rough. They pulled the small lever.

There are two separate levers, and the order matters:

• Resize changes the number of pixels. A 48 MP photo taken down to 2 MP literally has fewer pixels, so there is far less to store.
• Compress keeps the pixel count but encodes those pixels more efficiently, usually by dropping subtle detail.

Resize is almost always the bigger win, and it should come first. Take a typical 12 MP phone JPEG at around 3.5 MB. Compress it hard on its own and you might reach 1.5 MB, and the edges start to smear. Now do it the other way: resize the long edge to 2000 pixels first, which is about 2.6 MP, and it drops to roughly 1 MB before you have compressed anything at all. Compress that, and you land at a few hundred kilobytes, looking identical on any screen. Same photo, close to a tenth of the size, because you pulled the big lever first.

One caution worth repeating: resizing down is permanent. The pixels you remove are gone, and enlarging the photo later will not bring them back. Keep the full-resolution original somewhere if you might ever print or crop hard, and resize a copy for sharing.

Try this: the sky-versus-gravel test

Ever notice two photos at the same resolution weigh completely different amounts? Test it. Save one photo of a clear sky and one of a gravel path or a leafy tree at the same size, and compare the files. The gravel photo can be several times bigger.

That is JPEG showing its hand. It stores smooth areas like an open sky almost for free, because there is little to describe, and it charges you for fine detail and noise. Foliage, fabric, hair, gravel and low-light grain all give it more to encode. So the size of a photo is not just its dimensions; it is how busy the picture is.

How small do your photos really need to be?

Smaller than your instinct says. A full HD screen is about 2 megapixels and a 4K screen about 8. A 48 MP photo holds six times more detail than even a 4K display can render, so every pixel past that is invisible weight when the photo only ever lives online.

Match the size to where it is going. For a web page or a social post, around 1600 to 2000 pixels on the long edge is plenty, and that step alone strips off most of the bulk. For email you can go smaller still. Only printing and heavy cropping really need full resolution, and those are exactly the cases where you keep the original untouched.

So the workflow is two steps in order: resize to what the destination needs, then compress what is left. We built the image compressor at image.hivly.net to do both, in that order, because the ordering is the thing people get wrong. It runs in your browser, so the photo never leaves your device, which matters when the picture is personal and you would rather not hand it to an upload server just to make it smaller.

Done together, those two steps turn a multi-megabyte phone photo into a light file that loads fast and sends cleanly, with no difference you can see on a screen. The detail you dropped was detail you were never going to look at.