Why can’t the iPhone Camera app record both cameras at once?
It is a reasonable thing to go looking for: open Camera, look for a toggle or a mode that lets the front and back cameras run together, and find nothing. That absence is not an oversight or a feature Apple is holding back for a future update. Recording two cameras at the same time uses a different capture session than the one Camera is built on, and that different session comes with rules a single-camera app never has to think about.
Understanding what those rules actually are explains both why Camera app does not do this, and why an app that does do it looks and behaves the way it does — fewer resolution choices than a single camera gets, a resolution that locks the moment you press record, and a preview that is not a preview at all but the actual frame being written to the file.
Camera app runs one capture session; dual recording runs two feeding one
Underneath any iPhone camera app is an AVFoundation capture session, and the ordinary version of it — the one Camera app is built on — is designed around a single active input. You can switch which camera is active, from front to back and between lenses, but only one stream is ever flowing at a time. That is not a limitation someone chose; it is the entire shape of the API a normal camera app is written against.
Recording both cameras at once needs a different session type, one built specifically to run more than one input simultaneously and route each through its own connection to its own output. It is a separate API, with a separate set of rules, not an extra option bolted onto the session Camera app already has. An app either is written against this multi-camera session from the start, or it is not — there is no toggle that upgrades one into the other.
A multi-camera session cannot use the presets a single camera relies on
Point Camera app at "4K" or "high quality" and it picks a sensible format for you — a convenience preset that quietly handles resolution, frame rate and codec details on your behalf. Those presets exist because a single input only ever has to satisfy itself; the system can pick freely from whatever that one camera supports.
A session running two cameras at once cannot lean on that shortcut. Every input in it has to run a format that is explicitly flagged as multi-cam-capable, which is a narrower list than the formats that camera offers on its own, and the choice has to be made deliberately rather than handed to a preset. That is also why a dual-camera app’s resolution list looks shorter than a single-camera one’s — it is not being stingy, it is showing you only the formats that were actually eligible to begin with.
Two live pipelines share one hardware ceiling, not two separate ones
Running one camera costs a certain amount of processing. Running two at once, plus compositing them into a single frame in real time, costs more than double that — and the system enforces a ceiling on the combined cost, not a separate allowance per camera. Two cameras at a resolution that would be trivial individually can still add up to more than the hardware budget allows together.
That shared ceiling is the actual reason a dual-camera recorder offers 720p or 1080p rather than reaching for 4K the way a single-camera shot might, and why 1080p on both cameras at once is the heavier of the two — some devices genuinely throttle under it during a sustained take. It is also why resolution locks the instant recording starts: changing it mid-take would mean renegotiating that shared budget while the session is already running, which is exactly the kind of risk a recording in progress cannot absorb.
The preview has to already be the finished frame
A single-camera app can afford a gap between what you see and what gets saved — crop, filter and export settings can all be applied after the fact, because there is one source stream to work from. A dual-camera recording does not have that luxury in the same way: two live streams are being merged into one frame, in real time, on the GPU, and that merged frame is what actually gets written to the video file.
That is a direct consequence of writing one finished file instead of two raw ones that would need lining up in an editor afterwards. It is also why layout, the picture-in-picture corner and the filter can change mid-recording with no penalty — they only affect how that same real-time merge is drawn, frame by frame — while the things that would require restructuring the file itself, like resolution, cannot.
Why Apple does not just add this to Camera app
Camera app has to work the same way on every iPhone still receiving updates, most of which do not have the chip generation that multi-camera capture requires in the first place. Building a single, universal interface around a capability that only a subset of that fleet has — and where even the supported subset has a hardware budget that varies by exact model, by which lenses are involved, and by how hot the phone already is — is a materially harder design problem than a purpose-built app that only exists on devices where the capability is already known to be present.
A single-purpose dual-camera app can also afford to make fixed, upfront choices — a small set of resolutions, locked once recording starts, no attempt to be all things to all devices — in a way a general-purpose app that has to feel simple and consistent for everyone is not really free to do. The absence in Camera app is a reasonable product boundary, not a technical impossibility Apple has not gotten around to.
Common follow-up questions
Is there a hidden setting in iPhone Settings that turns on dual-camera recording in Camera app?
No. This is not a setting waiting to be switched on — Camera app is built on a capture session that only ever runs one active input. Recording both cameras at once requires a different session type from the start, which Camera app is not written against.
Can a dual-camera app ever offer 4K the way Camera app does for a single camera?
Not with the same hardware behind it. Two cameras running at once share one combined hardware budget rather than each getting its own, which is why dual-camera recording tops out at 1080p with an honest warning that some devices will throttle, rather than reaching for the resolutions a single camera can hit alone.
If my iPhone supports dual-camera recording, why does the resolution list look shorter than in Camera app?
A multi-camera session cannot use the convenience presets a single-camera session relies on. Every input has to run a format explicitly flagged as multi-cam-capable, which is a narrower list than that camera’s full set of formats — the shorter list reflects what actually qualifies, not a setting being withheld.
Want to just do this?
DualCam records the iPhone front and back cameras at the same time and writes one finished MP4 while you shoot. Free, no account, no ads, nothing leaves the phone.