The iPhone Camera Problem

Apple’s recent Pro iPhones are excellent small cameras. The iPhone 17 Pro, for example, has a 48 MP Pro Fusion camera system, ProRAW support, Photonic Engine, Deep Fusion, Smart HDR 5, and HEIF, JPEG, and DNG capture formats. The hidden problem is the default file most people keep: a finished, processed rendering rather than a preservation-grade original.

ProRAW combines standard RAW-format information with iPhone image processing, giving more editing control over exposure, color, and white balance. It is still Apple’s computational photography pipeline, but it keeps much more useful scene data than a normal HEIF or JPEG. Standard HEIF offers up to 24 MP, RAW 12 offers up to 12 MP, and RAW Max or HEIF Max can reach up to 48 MP on supported Pro models.

For memories you want to keep for decades, a 12 MP RAW master will age better than a sharper-looking 24 MP processed photo. The processed file may look cleaner on small screens, but the RAW file gives future software something real to work with. It gets even better: New storage formats now enable to preserve the raw and keep a manageable file size so there’s no real tradeoff.

The default iPhone photo is a rendered opinion

A typical iPhone capture path involves some mix of:

• exposure selection
• burst capture
• frame alignment
• multi-frame merge
• demosaicing
• denoising
• lens shading correction
• lens distortion correction
• local tone mapping
• face and sky handling
• semantic masks
• edge-aware sharpening
• texture enhancement
• white balance
• color rendering
• HDR mapping
• compression into HEIF or JPEG

Apple names parts of this system Deep Fusion, Smart HDR, Night mode, Photonic Engine, Photographic Styles, and related camera features. This pipeline can produce attractive images… on small screens. It can also make irreversible decisions before the photo reaches your library:

• Fine hair becomes a smooth edge.
• Grass becomes a painted texture.
• Skin becomes waxy.
• Logos and text can look reinforced but wrong.
• A boundary between a jacket and the background can shift by a few pixels.
• A window frame can get a halo.
• A face can be tone-mapped into a flatter, brighter version of itself.
• A dark area can lose its original noise pattern, which is often the only evidence future software has for reconstructing real detail.

Still a photo, but in archival terms it is closer to a final render.

Why 24 MP can be worse than 12 MP

A 24 MP HEIF image has “more” pixels than a 12 MP RAW image, but those pixels have already been interpreted. The iPhone has decided which texture is detail, which texture is noise, which edge deserves sharpening, which shadow deserves lifting, which sky needs smoothing, and which face should be protected from contrast. These decisions were made with algorithms from 2026, and they’re far from perfect.

A 12 MP RAW file stores a more useful working description of the scene. It gives a future editor or AI model access to richer tonal relationships, cleaner metadata, and less baked-in aesthetic judgment.

This is why “only 12 MP” can be misleading. A 12 MP RAW master is not the same kind of object as a 12 MP or 24 MP processed HEIF. The raw material is what you want, the other is a recipe already cooked.

The damage is permanent

A future photo model can improve a RAW file. It will demosaic better. It will denoise better. It will recover highlights with better tone curves. It will apply better lens profiles. It will use smarter deblurring, dehazing, color reconstruction, and super-resolution.

A future model may also improve on a processed HEIF, but that becomes guesswork much sooner. Once the original microcontrast is smeared, the noise pattern is removed, and local tone mapping has flattened the scene, exact recovery becomes impossible. The new model can invent plausible leaves, pores, fabric, or lettering. It cannot know the original leaves, pores, fabric, or lettering.

That is the core archival argument: keep the source, not the output.

Apple’s defaults make sense for sharing, not archiving

The default iPhone camera is designed for convenience:

• low storage use
• fast capture
• reliable sharing
• pleasing phone-screen previews
• fewer confusing choices
• good results for most casual snapshots

Those goals are rational. They are also different from preserving family photos, travel photos, childhood photos, documents, artwork, architecture, or once-in-a-lifetime scenes. When you’re taking pictures, you don’t know which ones will be the best: So you should capture the raw truth for all of them, just browse through and delete the bad ones.

Apple even exposes the tradeoff in settings. On supported models, the main or Fusion camera default can be changed between 24 MP and 12 MP, and “Prioritize Faster Shooting” modifies how images are processed so the phone can capture more photos when the shutter is tapped rapidly. That setting is on by default.

The practical answer: RAW 12 MP

For preservation-first shooting, the best default is:

ProRAW, 12 MP, JPEG-XL Lossy if available, with RAW settings preserved.

On iPhone 17 Pro, iPhone 17 Pro Max, iPhone 16 Pro, iPhone 16 Pro Max, iPhone 15 Pro, iPhone 15 Pro Max, iPhone 14 Pro, and iPhone 14 Pro Max, you can set the ProRAW default resolution and format from Camera settings. Apple also says you can preserve the ProRAW setting through Settings, Camera, Preserve Settings.

Use this setup:

1. Open Settings
2. Go to Camera
3. Open Formats
4. Turn on ProRAW & Resolution Control
5. Set the ProRAW format to JPEG-XL Lossy, if your model and iOS version offer it
6. Set the RAW default to RAW 12 or ProRAW 12 MP
7. Open Settings, Camera, Preserve Settings
8. Turn on ProRAW & Resolution Control or Apple ProRAW
9. In the Camera app, make sure RAW is actually active before important shots

The last step is critical. Enabling RAW support in Settings is not enough. If the Camera app is currently set to HEIC or JPEG, you are back to saving the processed file.

Why JPEG-XL Lossy is acceptable here

“Lossy RAW” sounds strange. For a pure archive, lossless is cleaner. For real phone use, JPEG-XL Lossy ProRAW is a strong compromise.

JPEG XL is a modern image coding system that supports lossy encoding, lossless encoding, and metadata through an extensible file format. In Apple’s newer ProRAW workflow, JPEG XL is wrapped inside a DNG container, so the file still behaves like a ProRAW file rather than a normal web JPEG XL image. Apple described this as a way to retain ProRAW flexibility with much smaller files.

The storage math is the reason this matters. Apple’s older ProRAW guidance says a 12 MP ProRAW file is about 25 MB and a 48 MP ProRAW file is about 75 MB. Apple estimated JPEG-XL ProRAW sizes of about 11 MB for 12 MP JPEG-XL Lossy, 18 MB for 12 MP JPEG-XL Lossless, 20 MB for 48 MP JPEG-XL Lossy, and 46 MB for 48 MP JPEG-XL Lossless on iPhone 16 Pro.

In practice, I often get 7 to 8 MB per photo.

That changes the storage argument: A 12 MP JPEG-XL Lossy ProRAW file can be small enough for real libraries while preserving far more useful material than a fully processed default capture.

For irreplaceable work, use JPEG-XL Lossless or the most compatible lossless ProRAW format. For everyday memories, JPEG-XL Lossy ProRAW is often the practical sweet spot.

The artifacts to look for

Open a default iPhone photo at 100 percent and look at difficult areas:

Hair and fur: strands merge into clumps, then sharpening draws artificial borders.

Leaves and grass: detail becomes a watercolor texture, especially in medium light.

Text and logos: letters look bolder, but corners and strokes drift from the real shape.

Faces: skin texture gets smoothed, then pores or wrinkles are reintroduced unevenly.

Edges: buildings, branches, glasses, jewelry, and clothing seams can show halos.

HDR scenes: shadows and highlights look impressive on the phone, but the tonal structure becomes harder to reinterpret later.

Motion: multi-frame fusion can create ghost detail around hands, pets, children, cars, and fabric.

Boundaries: semantic masks can separate subject and background imperfectly, especially around hair, transparent objects, reflective surfaces, and fine geometry.

These artifacts are easy to ignore on a phone screen. They become obvious when you crop, print, edit, or revisit the image years later on a better display.

ProRAW is not pure sensor RAW, and that is fine

A technical correction matters here: Apple ProRAW is not untouched sensor data. Apple describes it as standard RAW information combined with iPhone image processing, including compatibility with Smart HDR, Deep Fusion, and Night mode.

That makes ProRAW a hybrid. It is less pure than a classic single-frame Bayer RAW from a dedicated camera. It is also much more editable than a normal HEIF or JPEG.

For people who want even less processing, third-party camera apps can expose alternative RAW workflows. Halide, for example, describes its Process Zero mode as bypassing the standard iPhone image processing system and producing raw, sensor-level photos with more detail and more manual control. That route has tradeoffs though: less computational dynamic range, more visible noise, and more manual work.

RAW 12, RAW Max, or HEIF Max?

For most iPhone users, Apple ProRAW 12 MP is the simpler preservation default.

RAW 12 MP should be Apple default on Pro phones, period. For memories, people, travel, pets, family, street photos, and anything you want to keep. It balances editability, storage, and reliability.

RAW Max or 48 MP ProRAW: best for landscapes, architecture, artwork, documents, product shots, and scenes with excellent light where cropping matters.

HEIF Max: useful when you want high resolution with smaller files and limited editing plans.

Default 24 MP HEIF: fine for throwaway photos, quick sharing, receipts, parking spots, screenshots of reality, and anything with low archival value.

JPEG: best for compatibility with older systems, weaker as a master file.

The mistake is using default HEIF or JPEG as the only copy of a memory.

Preserve the original, share the render

A clean workflow is simple:

• Capture in RAW.
• Keep the DNG or ProRAW file.
• Edit from the RAW file.
• Export HEIF or JPEG copies for sharing. That’s the part Apple should make much easier.

Apple’s sharing behavior makes this worth checking. ProRAW files use the DNG format, and that sharing or emailing can produce smaller JPG versions depending on the path. Apple recommends methods such as iCloud Photos, AirDrop, Image Capture, or exporting the unmodified original when you want to keep the real ProRAW file.

That means your archive should contain originals, not only edited exports. A shared JPG is a delivery file. The DNG is the memory.

Compatibility caveat

The best archive format is the JPEG-XL. Apple supports JPEG XL across its ecosystem and wraps iPhone JPEG-XL ProRAW files in DNG. However, JPEG XL is still not universally adopted that why the iPhone 16 Pro options include other formats like JPEG Lossless, JPEG-XL Lossless, and JPEG-XL Lossy under ProRAW Format.

Test your workflow. If your editor, backup tool, NAS, Windows setup, or cloud library mishandles JPEG-XL ProRAW, choose the more compatible lossless ProRAW option. But as software moves quickly in the age of AI, you might find a solution sooner rather than later.

Apple should keep the raw material by default

Apple reports an installed base of more than 2.5 billion active devices, and iPhone had its best-ever quarter in Apple’s fiscal Q1 2026. So the default quality problem is affecting at least hundreds of millions of people: Most are unknowingly saving degraded photos.

Maybe the processed 24 MP photo looks better on a small screen, but it will age poorly. A 12 MP RAW master looks flatter at first, but it carries more of the original scene into the future: In five years, better demosaicing, denoising, HDR rendering, super-resolution, and AI restoration will exist. Those tools will perform best on files that still contain real signal.

The iPhone is a good camera. Treat it like one.