Do you need two iPhones to record dual camera video?
No. One iPhone that supports simultaneous capture, running an app built on a multi-camera session, records the front and back cameras at once into a single file. Two phones is the workaround people reach for anyway, because without knowing the hardware can already do this on its own, mounting one phone facing you and one facing the scene is the obvious way to get both views. It works, in the sense that you end up with footage of both — it just is not the same thing as what a single multi-camera session produces.
The two approaches are worth comparing honestly, because they are not the same tool solving the same problem in slightly different ways. One leaves you with two files you still have to reconcile. The other never produces a second file to begin with.
Why two phones feels like the obvious answer
The reasoning is intuitive and, on its own terms, not wrong: you want a camera pointed at yourself and a camera pointed at whatever you are reacting to or narrating, and a phone can only face one direction at a time, so two phones means two directions covered. It needs no special app either — any camera app on either device does its half of the job, which is part of why it is the first idea most people have.
What it actually gets you is two independent video files, shot on two independent devices, that someone still has to place together — either live, by physically arranging both phones so their frames read as one shot, or afterwards, in an editor. That reconciliation is real work, and it is the work a single-file recording skips entirely.
What a two-phone setup actually costs you
Two independent phones run on two independent clocks, and nothing keeps them aligned unless you deliberately add a sync signal — a clapperboard moment, a shared countdown — the way real multi-camera productions do. Skip that step, which almost everyone shooting casually does, and the two clips drift: a fraction of a frame of mismatch per minute that is invisible at first and obviously wrong by the ten-minute mark. This is a property of having two files with two clocks, not a flaw in how carefully you started them.
The logistics double along with everything else. Two mounts or two people holding phones steady, two batteries to watch, two amounts of storage to manage, and — the part that is easy to underestimate — no way to see the combined shot while you are filming it. Each phone only ever shows you its own frame, so whether the two views actually work together as one picture is something you find out later, in an editor, rather than something you can adjust in the moment.
What a single multi-camera session gets you instead
A multi-camera session is a documented capability of the capture hardware on iPhone XS, iPhone XR and newer — the same iPhones a simultaneous-recording app like DualCam requires — that lets the front and back cameras run concurrently inside one hardware session on one device. An app built on it draws both live images into a single frame on the GPU as they arrive and writes that exact frame to the file. There is nothing to reconcile afterwards, because the two views were already merged before anything reached storage: one shared timeline, one fixed frame rate, one file, running the whole take.
That structure is also why the sync problem does not carry over. A dropped frame under heat or heavy load takes the whole composited frame with it — both camera images together — rather than letting one camera fall behind the other the way two separate files can. And because everything lives inside one hardware session, it comes with a real ceiling that a two-phone setup does not have: the combined resolution and frame rate of both cameras has to fit inside one shared hardware budget, and convenience presets like "high" or "4K" are not available to a multi-camera session the way they are to a normal single-camera recording.
When two phones is still the right tool
None of this makes two phones the wrong answer in every case — it makes it the answer to a different set of constraints.
Your iPhone predates the hardware floor
Simultaneous capture needs the multi-camera session Apple has supported since the A12 Bionic generation. On an iPhone older than that, there is no software workaround — a single-phone dual recording is not available at all, and two phones running two separate camera apps is the only way to get both angles, synced or not.
You need landscape, or fully independent framing
A composited multi-camera recording commits to its layout — picture-in-picture or split screen, on a portrait canvas — at the moment you shoot. If what you actually need is landscape footage, or two clips you want full editing control over later rather than a layout decided during filming, two separate recordings genuinely serve that better than one file that has already merged them.
Common follow-up questions
Can DualCam record using two iPhones together?
No. DualCam runs one multi-camera session on a single iPhone that supports it — the front camera and one back lens, composited into one file. It is not built to pair with a second device.
Would a two-phone recording ever be higher resolution than a composited one?
Potentially, per camera, since each phone is not sharing a combined hardware budget the way both cameras inside one multi-camera session do. What you trade for that is two files instead of one, and the sync and logistics work that comes with them.
If I start two phones recording at the same moment, will they stay in sync?
Not reliably over a take of any real length. Two independent devices run on two independent clocks with nothing correcting for drift unless you add your own sync signal, which is exactly the category of problem a single composited file never has.
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.