Does dual camera video support HDR on iPhone?

HDR is bundled into presets a multi-camera session cannot reach

On a single camera, iPhone's higher capture presets bundle several things together: higher resolution, richer stabilization, and a wider dynamic range captured directly by the sensor. A simultaneous session cannot reach for any of those presets at all — every camera in it has to run a format explicitly marked as capable of multi-cam capture, chosen one setting at a time instead of picked from a convenience preset, and the combined cost of both streams has to fit inside a single hardware budget alongside the real-time compositing and the encode. The formats that clear that bar are the plainer ones. Resolution tops out at 1080p for the same reason stabilization tops out at a basic mode: the richer options were never on the table to begin with, because they belong to a preset the session cannot select.

So the honest way to describe DualCam's lack of an HDR toggle is not "a feature not yet added." It is a consequence of what a device will let two cameras ask for at once, in the same category as the resolution ceiling and the plainer stabilization.

Compositing gives it a second, independent reason

Even setting the multi-camera format limit aside, DualCam's own design would still get in the way. The front and back camera images are drawn into one canvas on the GPU as you record, and that composited frame is the exact frame written to the file — nothing is re-rendered afterwards. HDR video is not just "more range captured"; it is range that has to be carried all the way through capture, processing and encoding as one connected pipeline, usually inside a 10-bit container built for that purpose.

A dual recording never has one dynamic range to carry through that pipeline — it has two, one per camera, already merged into a single frame the moment they are drawn. There is no point in that pipeline where two independently exposed live images could be handed off with two different tonal ranges intact and still come out as one coherent picture a moment later. Composite first, decide the range once for both halves at once — which is exactly what an 8-bit H.264 file does.

What shooting in standard range means in practice

Standard dynamic range has less room at the extremes than HDR does. Point the back camera at a bright window or a sky and it can clip to a flat, detail-less white; leave a corner of the frame in real shadow and it can crush to solid black. HDR video, where it exists, buys some insurance against exactly that — the sensor captures a bit more at both ends, and the file has somewhere to keep it. DualCam does not have that insurance on either camera feed, so the exposure the camera lands on when you press record is close to the exposure you are stuck with.

This sits on top of a fact that already causes brightness mismatches in dual video: the two cameras set exposure completely independently, each one reading only the frame it sees. A bright window behind your head is already a well-known cause of a dark face in a dual recording — standard-range capture just removes the small margin HDR might otherwise have clawed back at either end.

There is no fixing it after the fact

Once recording stops, a dual-camera file is an ordinary finished MP4, not a project with two separate exposures still sitting behind it. Trimming, adding music or captions, exporting for a platform — all of that works normally, but nothing pulls back a highlight that clipped to white or a shadow that crushed to black while you were shooting, because there was never extra range recorded to reveal. Getting the light right before you press record is the entire lever here, more so than it would be with a single HDR-capable camera that leaves a little room to fix things in an edit afterward.