2026-10-20
A photo from an iPhone 14 Pro lands around 2 to 3 MB at default settings, and ProRAW goes past 25 MB. Emails, online forms and corporate upload portals reject those regularly. There are three ways to compress photos on iPhone, and none of them need an extra app: batch resize through the built-in Shortcuts app, pick a size when attaching in Mail, or open a browser-local compressor in Safari and set a target size. The first two have no learning curve but come with limits. The third gets you to a specific KB figure.
Two reasons, the sensor and the format. A 48-megapixel sensor captures what it captures, and while HEIC stores the same quality in roughly half the space of JPEG, it still buckles under sending twenty at once. The practical difference between HEIC and JPEG is set out in /blog/heic-vs-jpg-iphone-photos, and converting when an older system needs it is in /blog/convert-heic-to-jpg-free.
What actually drives file size is pixel count and compression quality, which has less to do with the phone than people assume. That is broken down in /blog/image-resolution-vs-file-size.
Batch and automation are the win here. Precision is not: Resize Image takes a width, not a target file size, so you find out afterwards what you got. Fine for an archive pass, unreliable against a hard 100 KB cap.
Cheapest option by a distance, with a matching limit: it only works inside Mail, you never get a reusable small file out of it, and the four tiers are fixed. Sizes for attachments are covered in /blog/compress-image-for-email-attachments and /blog/compress-photo-to-1mb-email.
Three things hold at once here: no app to install, no upload to someone else's server, and a number you can actually hit. The file is processed on the phone the whole way through, which matters when the pictures contain faces or work material. Whether compression costs visible quality is dealt with in /blog/does-compressing-image-reduce-quality, and doing dozens at a time in /blog/batch-compress-images-multiple.
HEIC is smaller than JPEG at the same quality, which is why it is the default on iPhone. The trouble is at the receiving end: a fair number of corporate systems, older Windows builds and online forms do not recognise it and fail with an unhelpful error that reads like a size problem. Decide based on who is receiving rather than converting everything up front, because converting to JPEG before compressing throws away the size advantage.
It depends on dimensions. At 1920 px wide and around 200 KB, a 6 inch print is fine, while A4 and above shows the missing detail. For print, set dimensions first and compress quality second, and stop earlier than you would for screen.
Usually the format, not the size. Systems that do not read HEIC often throw a vague error that looks like a size problem. Convert to JPEG first; the steps are in /blog/convert-heic-to-jpg-free.
No. It writes to a new file and leaves the version in Photos alone. You can delete the originals afterwards to reclaim space, though check the compressed output first.
No. A batch is the same single operation run twenty times. What does hurt is compressing the same file repeatedly, where each pass removes another layer of fine detail, explained in /blog/does-compressing-image-reduce-quality.