Why is my phone photo so big?

A photograph has no inherent size. The same scene shot on the same phone can be 800KB or 8MB, and four changes to phone cameras over the last decade account for almost all of the growth.

Knowing which one is responsible for your file matters, because only two of them are worth doing anything about.

1. Resolution went up by a factor of four

A 2016 flagship shot 12 megapixels. A 2026 flagship shoots 48 or 50 by default on the main sensor, and some shoot 200.

File size scales roughly with pixel count, so this alone is a 4x increase. And it is almost entirely wasted for any normal use:

Use	Pixels actually needed	Megapixels
Instagram, WhatsApp	1080 across	1.2 MP
Full-screen on a 4K TV	3840 across	8 MP
A 6x4 inch print at 300dpi	1800 across	3.2 MP
An A4 print at 300dpi	2480 across	7.3 MP
A 48MP phone photo	8000 across	48 MP

An A4 print — larger than most people ever make — needs 7 megapixels. The remaining 41 are stored, backed up, and then discarded by whatever displays them.

This is the one worth fixing, and it is free. Resizing from 8000 pixels wide to 2560 is invisible on anything that was going to show it at 2560 or less, and removes about 90% of the file.

2. HDR means more than one exposure

Modern phones do not take one photograph. They capture a burst at different exposures and merge them, which is why you can now see detail in both a bright sky and a shadowed face in the same frame.

The merged result has more real tonal information than a single exposure, and genuinely needs more bytes to store. Some phones also save a gain map alongside the image — a second, smaller layer describing how to brighten the highlights on an HDR display — which adds 10–20%.

This one is mostly not waste. It is detail you can see.

3. HEIC, and why it sometimes makes things worse

iPhones have defaulted to HEIC since iOS 11, and HEIC is about half the size of JPEG at the same quality. So it should have made files smaller, and for storage it did.

The problem is what happens when something does not accept it, which is often. Upload forms, older Windows software, many web applications and a good share of email clients still cannot read HEIC. The usual rescue is to convert to JPEG — and that conversion doubles the file, because you are moving from an efficient modern codec to a 1992 one.

So the 2MB HEIC on your phone becomes a 4MB JPEG the moment you need to upload it. The file did not get better; it got portable.

4. Computational photography adds layers

Portrait mode stores a depth map. Live Photos store a short video alongside the still. Some phones keep the unprocessed frames for a while so you can re-edit. Burst mode keeps everything.

These are often invisible in the photo library — it looks like one image — but the file carries the extra payload. A Live Photo is a JPEG plus a three-second video, and sharing it as a photo usually drops the video, which is why the file your friend receives is dramatically smaller than the one on your phone.

So what do you actually do

In order of how much they save per unit of effort:

Resize. The single biggest lever and the only free one. Target the largest size anything will display. 2560 pixels on the long edge is generous for virtually everything short of large-format printing.

Encode at quality 0.80–0.85. Removes 60–70% of what is left with no visible change, because most of what goes is sensor noise rather than detail. More on where that threshold comes from.

Change the camera setting, if you keep hitting this. Most phones can be set to shoot 12MP instead of 48, and to shoot JPEG instead of HEIC. If you are compressing photos weekly, shooting a sensible size in the first place is less work than fixing each one.

Stop emailing originals. This is the biggest practical win for most people. A 5MB photo against Gmail's effective 18MB ceiling means four photos per message, and the recipient did not need 48 megapixels.

The arithmetic, worked

A 48MP HEIC at 3.5MB, needed under 500KB for a form:

Original                  8000 x 6000, HEIC      3.5MB
Converted to JPEG q0.92   8000 x 6000            7.1MB   worse
Resized to 1600 x 1200    quality 0.92           780KB
Resized to 1600 x 1200    quality 0.82           430KB   fits

Note the second line. Converting format without resizing made it twice as large — which is exactly the trap, because "convert HEIC to JPG" is the advice most people find first.

The last line is 8% of the original and will look identical on the form that displays it at 400 pixels wide.

Why measuring beats guessing here

The problem with the table above is that it is specific to one photograph. A picture of a brick wall and a picture of a blank sky at the same dimensions and quality differ by a factor of four in size, because one is full of high-frequency detail and the other is nearly flat.

So no fixed quality setting lands reliably on a byte target. What works is encoding, weighing the actual output, and adjusting — about eight passes of fifteen milliseconds each, converging to within a percent of the limit.

Compress an image to 500KB, to 1MB or to 200KB does that in your browser. The photo is never uploaded, which for anything with a face or a location in it is the other thing worth caring about.

FAQ

Why are iPhone photos so large?

Mostly resolution: recent iPhones shoot 48 megapixels by default on the main camera, four times the 12MP of a few years ago. HDR capture and Live Photos add more. Ironically HEIC — the format Apple uses — is the efficient part, at roughly half the size of JPEG; the file balloons when you convert it to JPEG for something that cannot read HEIC.

Does resizing a photo reduce its file size?

Yes, and it is usually the biggest single saving available. File size scales roughly with pixel count, so halving both dimensions removes about three quarters of the file. It is also the only lossless-in-practice option as long as the result is still larger than whatever will display it — a browser showing a photo at 1200 pixels wide discards everything above that anyway.

Should I turn off HEIC on my iPhone?

Only if you regularly upload to things that reject it. HEIC is genuinely better for storage, at about half the size of JPEG for the same quality. But if every upload means a conversion that doubles the file, switching the camera to "Most Compatible" saves you the round trip. The setting is under Settings, Camera, Formats.

How do I email photos without them being rejected?

Resize to around 1600 pixels on the long edge and encode at quality 0.82, which puts a typical photo between 300 and 600KB. Against Gmail's real ceiling of about 18MB that is thirty photographs per message. Note that Gmail advertises 25MB but measures the base64-encoded message, which is about 33% larger than the files themselves.