How to Reduce Photo File Size on iPhone
Shrink iPhone photos without wrecking detail. Start with Preview, then resize, compress, or convert only when the upload target needs it.
Contents
To reduce photo file size on iPhone, start in Preview: share the photo from Photos, adjust the size, export a copy, and check the new file in Files. If the site needs a hard limit like 500 KB or 2 MB, resize pixels first, then compress. One step rarely does both well.
Everyone’s been here: a clean iPhone shot, a form that rejects it, and a file name that says 3.9 MB when the upload box wants less than 1 MB. Preview can handle the first pass. If you need tighter control after that, RoundCut Compress is the browser route I use when the native path starts guessing.
Use Preview on iPhone before installing anything
Apple’s current iPhone guide lists Preview as able to crop, remove backgrounds, and adjust image size. That matters because you can shrink one photo without handing it to a random App Store compressor, watching an ad, or wondering where the original went. Start native. It’s cleaner.
Open Photos, pick the image, tap Share, and send it to Preview. In Preview, tap the more button, choose Adjust Size, keep proportions locked, and enter the width you actually need. For a website hero shot, 1600 px wide is often enough. For a profile upload, 800 px is usually plenty.
The drawback: Preview is a little hidden on iPhone, especially if you haven’t pinned it in the Share sheet. It also doesn’t think in “make this 500 KB” terms. It thinks in dimensions and export settings, which is correct design-wise but annoying when a school portal, Shopify form, or insurance upload just spits back a file-size limit.
Pick the right target before you compress
File size follows the job. A product image for a Shopify grid needs enough edge detail for zoom; a Gmail attachment only needs to arrive; a LinkedIn profile crop needs the face to stay sharp inside a small circle. Same phone photo, different answer.
I use this quick split:
- Under 300 KB: small web thumbnails, email signatures, lightweight blog images.
- 300 KB to 1 MB: product cards, form uploads, social posts where detail still matters.
- 1 MB to 2 MB: larger page images, portfolio uploads, photos that may be opened full screen.
- Original size: keep it when the photo is a master file or might go to print.
Don’t chase the smallest number blindly. A 90 KB image can look fine in a list view and fall apart on a retina screen when someone taps to zoom. The real win is matching the file to its display size (which is where most rushed exports go wrong).
If the destination says 2 MB exactly, use the more specific RoundCut 2MB guide workflow. If the problem is email, the RoundCut email guide is a better fit because mail apps have their own quirks.
Resize pixels first when the photo is huge
If an iPhone photo is 4032 x 3024, compression alone is the blunt tool. Resize it first, then compress the smaller copy. You keep the crop, the grid, and the visual hierarchy, but you stop asking the upload form to carry pixels nobody will see.
I ran a local test for this article with a 4032 x 3024 JPG that weighed 3.93 MB. Resizing it to 1600 x 1200, saving at JPEG quality 82, and stripping metadata produced a 360,988-byte file. That’s about 361 KB. Big drop. Still readable.
Close. The real story is that the resize did most of the work, not magic compression. If you leave a 12-megapixel photo at full dimensions and only lower JPEG quality, hair, fabric texture, and tiny text can get crunchy before the file gets small enough.
For repeat jobs, use an image resizer after Preview gives you the original. RoundCut’s upside is speed and repeatability in the browser. Its downside is the same as every browser tool: it won’t know whether your product needs more whitespace or whether your headshot crop is too tight. You still have to look.
Compress or convert when dimensions are already right
Once width and height are sane, compression handles the final weight. For photos, JPEG at a medium-high quality setting is still the safe compatibility pick. For web pages, WebP usually gets smaller while keeping the same visible detail. For iPhone storage, Apple’s High Efficiency setting keeps new captures in a space-saving format.
That last bit trips people up. HEIF is good for storage on iPhone, but some upload forms still expect JPEG because their backend is old, lazy, or both. If a site rejects an HEIC file, export a JPEG copy instead of changing your whole camera setup for one form.
Use compress in browser when the dimensions are already right and the only problem is weight. Use JPG to WebP when the image is going on your own site and you care about load speed more than old-app compatibility.
PNG is the exception. If your iPhone image is a screenshot, logo, or cutout with transparency, do not flatten it to JPEG unless you want a background baked in. Use the PNG size guide for that path.
Check the result at 100% before uploading
The final check is boring and saves more trouble than any slider: open the smaller file at 100%, look at faces, edges, type, and product texture, then upload that copy. If it looks bad at 100%, it’ll look worse after Instagram, X, or a marketplace compresses it again.
I check three spots: the face or hero subject, any small text, and the edge where foreground meets background. No kidding. Those are the places compression fumbles first, and they’re the places a buyer or recruiter notices without being able to name the problem.
For a store, tie this to page speed too. The RoundCut speed guide goes deeper on WebP, AVIF, and display pixels (the part most uploaders hide). For one iPhone photo, keep it simpler: duplicate the original, resize the copy, compress only if needed, and keep the master untouched.
Next time an iPhone photo gets rejected, do not install the first compressor you see. Open Preview, make a smaller copy, check it in Files, then use RoundCut only when you need a tighter target. Thirty seconds is enough. If it takes longer, the file probably needed a crop before it needed compression.
