2026-10-21
A photo from a mid-range Android phone lands around 3 to 6 MB at default settings, and the high resolution modes go past 10 MB. Emails, application forms and corporate upload portals reject those regularly. There are four ways to compress photos on Android, and none of them need an extra app: export a resized copy from the gallery app, use the Google Photos storage saver, pick a size when sharing, or open a browser-local compressor in Chrome and set a target size. The first three have no learning curve but cannot hit a specific number. The fourth can.
Two reasons, the pixel count and the encoding. A high resolution mode captures what it captures, and while most of the Android side stores JPEG by default, with some models on HEIC or HEIF, those save 40 to 50 percent over JPEG at the same quality. Cheaper per photo, and it still buckles under sending twenty at once.
What actually drives file size is pixel count and compression quality, which has less to do with the phone than people assume, broken down in /blog/image-resolution-vs-file-size. So the first step is not finding a tool but working out how large the photo needs to end up, since a feed post and a 6 inch print are two different targets.
One misconception worth clearing up: an optimised or backed up badge in the gallery app does not mean the local file shrank. The cloud holds a separate copy and the full original stays on the phone.
The win here is that it ships with the phone and adds no install. The limit is just as clear: the tiers are fixed, you find out the resulting size afterwards, and every manufacturer puts the entry point somewhere else, so switching phones means hunting for it again.
The storage saver swaps already backed up photos for slightly lower quality versions in the cloud, and leaves the copy on your device alone. It frees cloud space, not phone space.
So if the goal is making one photo smaller in order to send it, this route does nothing for you.
Cheapest option by a distance, with a matching limit: it only works inside that one app, you never get a reusable small file out of it, and the tiers are fixed. What size an attachment should be is covered in /blog/compress-image-for-email-attachments and /blog/compress-photo-to-1mb-email.
Against a specific cap, say a form that demands under 200 KB, none of the first three can promise anything. Use a browser-local tool instead:
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.
Some Android phones save HEIC or HEIF by default, which is smaller than JPEG at the same quality. The trouble is at the receiving end: a fair number of corporate systems, older Windows builds and online forms do not read 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. The same judgement on the iPhone side, and the conversion steps, are in /blog/heic-vs-jpg-iphone-photos and /blog/convert-heic-to-jpg-free.
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. Some forms also cap dimensions and pixel count separately, so check which limit is written down.
No, the option exists to keep the original. Wording varies by manufacturer, so when the menu only offers Save with no Save as copy, confirm once before tapping.
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.
The logic is the same and the entry points differ. iPhone batch work runs through Shortcuts, Android mostly through the editing export in the gallery app, and both can set a target size in a browser-local compressor. The three iPhone methods are in /blog/compress-photos-iphone-3-ways.