ConvertPix
Modern iPhone photos are gorgeous — and enormous. A single shot from a recent iPhone can weigh several megabytes, a ProRAW frame far more. That's fine until you hit the real world: an email server that bounces attachments over 20 MB, a visa application portal that caps uploads at 1 MB, a messaging app that mangles your picture with its own brutal compression, or simply a storage bar creeping toward full. The good news: you can usually shrink a photo's file size by 70–90% with no visible difference at normal viewing sizes — if you understand which two levers you're pulling.
Why iPhone photos are so big in the first place
File size is driven by three things: pixel count, compression level, and content complexity. Recent iPhones capture 12, 24, or 48-megapixel images. Every one of those millions of pixels stores color information, and even efficient formats like HEIC can only compress so far. Complexity matters too: a photo of foliage, gravel, or a crowd contains far more fine detail than a photo of a clear sky, so it compresses less. That's why two photos from the same camera can differ in size by 3× or more.
The two levers: resizing and compressing
Every method of shrinking a photo comes down to two independent operations. Knowing which one your situation calls for is most of the battle.
Lever 1: Resize (fewer pixels)
Resizing reduces the image's dimensions — say, from 4032×3024 down to 1920×1080 (Full HD). This is the single most effective way to cut file size, because size scales roughly with pixel count: halving both dimensions cuts pixels (and, roughly, file size) to a quarter. And here's the part people miss: if the photo will be viewed on a screen, extra pixels beyond that screen's resolution are invisible. A 48 MP image shown on a 1080p laptop display is being downscaled anyway; you're paying megabytes for detail nobody can see.
Resize when the destination is a screen, a website, a chat thread, or a document. Don't resize the only copy of a photo you may want to print large or crop into later — resizing throws pixels away permanently, so work on copies.
Lever 2: Compress (fewer bytes per pixel)
Compression keeps the dimensions but stores the pixels less precisely. JPEG-style quality settings run from 100 (nearly lossless, huge) down to 0 (tiny, blocky). The relationship is dramatically non-linear:
- 100–90%: visually lossless for almost all purposes; big size savings already happen just below 100.
- 90–75%: the sweet spot for sharing — files shrink several-fold, artifacts remain invisible at normal viewing distance.
- 75–60%: still respectable for casual sharing and messaging; close inspection may reveal softness around sharp edges.
- Below 60%: visible blockiness in gradients and fine texture — worth it only when a hard upload cap forces your hand.
One warning: recompressing an already-compressed JPG over and over degrades it cumulatively, like photocopying a photocopy. Compress once, from the best source you have, at the quality you need — don't run a photo through five apps in a row.
Match the method to the destination
| Destination | Sensible dimensions | Quality range |
|---|---|---|
| Email attachment | 1920px on the long edge (Full HD) | 75–85% |
| Web form / portal with 1–2 MB cap | 1280–1920px long edge | 60–80%, adjust to fit the cap |
| Messaging apps | 1280–2048px long edge | 80% — the app may recompress anyway |
| Website / blog images | 1200–2000px wide | 70–85%, consider WebP |
| Archiving keepers | Original dimensions | Keep originals; compress copies only |
Why not just let the web do it?
Plenty of websites offer free image compression, and for a non-sensitive photo they work. But consider what's actually happening: your photo is uploaded to a stranger's server, processed there, and downloaded back. That costs time and mobile data, fails without a connection, and — for photos of your family, your documents, your home — hands a copy to infrastructure with a privacy policy you almost certainly haven't read. On-device processing does the same math locally in a fraction of the time, with nothing transmitted at all.
Rule of thumb: resize for the destination first, then compress to taste. A 1920px, 80%-quality JPG is typically 85–95% smaller than a full-resolution original and looks identical on any screen it's shared to.
A quick word on formats
Format choice is the third, smaller lever. HEIC is efficient but incompatible outside Apple's world (see our HEIC vs JPG guide); JPG is the universal choice for shared photos; WebP often beats JPG on size for web use; PNG is the wrong tool for photographs entirely — it's lossless and produces huge files for camera images. If your goal is a smaller file that anyone can open, converting to JPG while you compress solves both problems in one pass.
How ConvertPix helps
ConvertPix puts both levers in one offline app. Its image resizer offers preset sizes — including HD, Full HD, and 4K — plus picture resizing for social media, and its compressor lets you set quality anywhere from 60% to 100%, reducing photo size by up to 90% while maintaining quality. You can batch process up to 10 images at once, and convert between HEIC, JPG, PNG, and WebP in the same step. Because ConvertPix works 100% offline, your photos never leave your device — no uploads, no waiting, no privacy concerns. It's free on the App Store for iPhone and iPad (iOS 15.1+).