Every photo you take on a modern iPhone carries a quiet engineering decision buried in the Camera settings. If you set up your phone a while ago and never revisited the format options, there’s a reasonable chance it’s still shooting JPEG — a format whose compression design dates to 1992, running on hardware that ships with a capable 48-megapixel sensor and a dedicated neural engine. That mismatch matters more in 2026 than it ever did before.
This is not an argument that JPEG is broken. It has served photographers, web publishers, and archivists well for decades. The case here is narrower and more specific: for iPhone users who actually care about what their images contain, JPEG increasingly throws away data that the phone’s hardware went to real trouble to collect.
What JPEG Actually Does to Your File
JPEG compression works in a well-documented sequence. The encoder converts the image from RGB into a luminance-plus-chrominance color model (YCbCr), then applies chroma subsampling — typically discarding half the color resolution horizontally, since human vision resolves luminance detail more sharply than color. The image is then divided into 8×8 pixel blocks, each run through a Discrete Cosine Transform, and the resulting frequency coefficients are quantized — meaning higher-frequency detail is rounded to coarser values and then entropy-coded. That quantization step is where data is permanently discarded. There is no lossless JPEG option that preserves what the sensor captured; the format’s defining mechanism is lossy, every time.
Re-saving a JPEG makes this worse in a specific way. Each successive encode runs a fresh quantization pass over already-quantized data, so artifacts compound rather than simply holding steady. A photo you open in an editor, adjust brightness slightly, and save again has now been through two rounds of block-artifact accumulation.
What HEIF Actually Stores Instead
Apple’s default capture format since iOS 11, HEIF (High Efficiency Image File Format) uses HEVC-based compression with fundamentally different block prediction — it references neighboring blocks to encode content rather than treating each block independently. The visual result at equivalent file sizes is meaningfully fewer hard-edged artifacts, particularly in smooth gradients like sky tones or skin.
Beyond compression efficiency, the container itself handles things JPEG cannot. HEIF supports 10-bit color depth natively, which matters directly to iPhone users because recent iPhones capture in 10-bit HDR by default in certain shooting modes. A JPEG can only encode 8 bits per channel. When the phone downconverts that HDR capture to JPEG, it maps 10-bit tonal values into an 8-bit space, collapsing the subtlety in highlight and shadow transitions that the sensor actually recorded. You lose that before the compression even begins.
HEIF also handles multi-image sequences in a single file — the structure Apple uses for Live Photos, burst captures, and depth maps. JPEG handles one primary image per file and bolts auxiliary data on loosely through sidecar mechanisms.
For a closer look at how these two formats compare across a wider set of shooting scenarios, our article on HEIF vs. JPEG camera format choices covers the tradeoffs in more depth.
The Compatibility Argument Is Weaker Than It Was
The most common reason iPhone users stay on JPEG is compatibility. Older software, certain email clients, and some web upload forms still trip over HEIC files. This was a legitimate concern in 2017 and 2018, when HEIF was new and support was patchy.
A few things have shifted since then. Windows 10 and 11 added HEIC support through the HEVC Video Extensions codec (though users may need to install it separately — check current support documentation for your Windows version, since this is one of those areas where the experience varies by build and device). macOS has opened HEIC natively since High Sierra. Current versions of major browsers have progressively added support for HEIF images, though this is worth verifying against current release notes rather than taking as a permanent given.
When you genuinely need a JPEG — uploading to a service that rejects HEIC, or sending a file to a client whose software predates the format — iPhone’s built-in compatibility features handle the conversion on transfer. Under Settings → Camera → Formats, setting “Transfer to Mac or PC” to Automatic causes the phone to silently convert HEIC to JPEG when you cable-connect to a desktop, without touching the original stored on the device. If you want to convert files manually without installing anything, we’ve documented how to do that on-device without third-party apps.
Apple ProRAW: A Step Further
If you’re shooting on a recent iPhone Pro model, there’s a third option worth considering: Apple ProRAW. This format stores a DNG-wrapped file that includes the computational photography processing — the multi-frame noise reduction, Smart HDR compositing, and deep fusion passes — as a 12-bit linear DNG, rather than flattening all of that work into a final render. You get a file you can still push in post with real tonal latitude, rather than an already-baked result.
ProRAW files are larger, and the workflow requires an app that actually reads DNG with full fidelity. The format draws on the same DNG standard that has been developing for years — for context on that standard’s trajectory, our coverage of DNG becoming the official RAW standard explains what that designation means in practice. For most users, ProRAW is overkill for casual shooting but genuinely worthwhile for anything you intend to edit seriously.
Making the Switch Without Disrupting Your Workflow
The settings path is short: Settings → Camera → Formats, then select “High Efficiency.” That’s the change. The phone keeps shooting everything normally; the only difference is what the encoder writes to storage.
Before switching, think through two specific scenarios:
- Shared photo libraries. If family members access your iCloud library from older devices or Windows PCs, verify their software handles HEIC before you flip the setting. The easiest test is to airdrop one HEIC file to each device they use.
- Third-party camera apps. Apps like Halide and Moment have their own format settings independent of Apple’s Camera app. Changing the system setting won’t automatically change what those apps write.
If either scenario creates friction, the “Transfer to Mac or PC → Automatic” setting mentioned above handles the practical problem without forcing you back to JPEG as your capture format.
The actual next step: open Settings on your iPhone now, navigate to Camera → Formats, and check what it says. If it says “Most Compatible,” your phone is shooting JPEG. Switch it to “High Efficiency,” then compare a few shots at 100% zoom against older JPEG captures from the same scenes — particularly anything with clear sky, smooth fabric texture, or gradients. The difference in block artifacts and color banding at pixel level is not subtle.