Every photo you take on a modern smartphone is being encoded by a format the camera selected before you ever opened the app. Most people have never changed that setting. Many don’t know it exists. And while format choice won’t affect whether a photo looks good on a 6-inch screen, it has an outsized effect on how many photos fit in your pocket before the “storage almost full” warning interrupts a shoot.
This isn’t about upgrading to RAW or chasing maximum quality. It’s about understanding what happens at the encoding stage — and why two photos that look identical can occupy very different amounts of space depending on how they were written to storage.
Why File Size Isn’t Just About Megapixels
The pixel count of your camera’s sensor sets a ceiling on file size, but format and compression determine how much of that ceiling you actually hit. A 48-megapixel sensor doesn’t necessarily produce 48-megapixel-equivalent files — most smartphones apply aggressive processing before the image is even saved.
JPEG, which remains the default on many Android devices and in Apple’s “Most Compatible” mode, uses Discrete Cosine Transform compression. The encoder breaks the image into 8×8 pixel blocks, applies a quantization step that discards detail the human visual system is less sensitive to, and writes the result. The quantization table determines how aggressively data is thrown away. A JPEG shot at quality 95 versus quality 75 can differ substantially in file size while looking nearly identical at normal viewing distances — the difference shows most clearly in fine textures, gradients, and anything containing repeating patterns.
HEIF (the container format that wraps HEVC-compressed images, commonly saved as .heic on Apple devices) uses a different compression method: block-based coding with more sophisticated prediction algorithms that generally encode more image information at a smaller file size than equivalent-quality JPEG. The efficiency gain comes from how HEVC handles motion-prediction and intra-frame coding, which was designed for video but translates well to still images. The practical result is that an HEIC file from the same shot as a JPEG will typically be meaningfully smaller — some device manufacturers cite roughly half the storage for comparable perceived quality, though actual ratios vary with image content, exposure, and the specific encoder implementation.
What Each Format Actually Preserves (and Discards)
The compression method is only part of the equation. Format choice also determines what the file is capable of storing.
JPEG:
- 8 bits per channel (24-bit total for RGB), meaning 256 possible values per channel
- No native transparency support
- Lossy compression applied at every save — re-saving a JPEG discards additional data at each quantization step, not just the first
- Broad universal compatibility across every browser, operating system, and image editor
HEIF (.heic):
- Supports 10-bit color depth per channel, which matters if your phone’s camera captures HDR content — that extended range has somewhere to live in the file
- Container format that can store bursts, HDR gain maps, depth maps, and image sequences alongside the primary image
- Efficient chroma subsampling (4:2:0 or 4:2:2 depending on encoder settings) similar to JPEG, but the prediction step preserves more edge detail at the same bit budget
- Still not fully interoperable — certain older software and non-Apple web platforms may require conversion before the file is usable (check current compatibility before relying on HEIF for any archive or handoff workflow)
Apple ProRAW / RAW-adjacent formats:
- Unprocessed or minimally processed sensor data, typically with a linear response curve rather than the camera’s baked-in tone mapping
- Much larger files — often an order of magnitude bigger than an HEIC of the same scene
- Preserves the full bit depth and dynamic range available from the sensor, but requires a RAW-capable editor to interpret the file usefully
For the vast majority of smartphone users, the meaningful choice is between JPEG and HEIF. RAW formats are a deliberate workflow decision, not a storage optimization.
The Settings That Actually Control This
On iOS, the camera format preference lives under Settings → Camera → Formats. “High Efficiency” writes HEIC; “Most Compatible” writes JPEG. The choice applies to video as well — HEVC versus H.264 — so switching affects how much storage your video clips consume too.
On Android, the path varies by manufacturer, but most camera apps expose a “picture format” or “file format” toggle somewhere in the camera settings menu. Some Samsung devices list this under Advanced Picture Options; Pixel cameras have historically defaulted to JPEG with HEIF available as a toggle, though implementation details vary by Android version and device — verify in your current camera app before assuming either way.
A few practical considerations before switching:
- Where are the files going? If you routinely share photos to services or devices that struggle with HEIC, a conversion step gets added to every handoff. The file you convert from HEIF to JPEG on iPhone loses the 10-bit color data in the process — that information doesn’t survive a round-trip through an 8-bit format.
- Are you shooting HDR content? Modern phones increasingly capture HDR (High Dynamic Range) images using gain maps or dual-exposure techniques. HEIC is the only widely available smartphone format that can store this extended dynamic range information intact. JPEG truncates it.
- Do you back up to a cloud service? Some services transcode on ingest. Know what your backup provider actually stores before treating cloud storage as an archival format — the risks of format-level data loss are worth understanding separately.
- Are you sharing directly to social media? Most platforms re-compress on upload regardless of what you send them. See our coverage of what compression tradeoffs happen when you export for social media — the format you shoot in matters less than you might expect once a platform’s encoder gets involved.
The Size Difference in Real Terms
Concrete numbers are difficult to pin down without specifying a phone model, scene complexity, and encoder version — claims like “HEIC is always half the size of JPEG” flatten variables that matter. What’s reliably true: HEIC files from the same sensor and scene will typically be smaller than JPEG files at comparable visual quality, because HEVC’s intra-coding is more efficient than JPEG’s DCT quantization for most photographic content. Complex scenes with lots of fine detail (grass, foliage, fabric) will show a larger proportional difference than flat scenes with smooth gradients.
The most honest test is your own library. Check the file info on a recent JPEG from your phone, then switch formats, shoot the same subject, and compare. The difference may be striking enough to decide the question on its own — or the compatibility friction may tip you back. That tradeoff is real and format-specific, not something a general recommendation can resolve for you.
What to Do Next
Open your camera app’s settings right now and find the format option. If you’re on JPEG and your phone supports HEIF, try switching for a week. Pay attention not to visual quality — they’ll look identical on the phone display — but to how your files behave when you share them, how they open in whatever editor you use, and how much storage you recover. If the workflow is frictionless, you’ve made a practical gain at no visible cost. If every third share triggers a “can’t open this file” response, you’ll know what HEIC compatibility friction actually looks like in your specific situation.