Why do two-camera videos go out of sync on iPhone?
They usually do not, but the worry is reasonable, because it comes from real experience: two-camera productions — two phones side by side, or an app that keeps the front and back streams as separate video tracks — really do drift apart on a long take. The reason a single composited dual-camera recording does not have this problem is not that it is better at preventing drift. It is that there is nothing to drift, because there was never a second file to begin with.
That distinction is worth understanding on its own terms, because it also points to the one place a dual-camera recording can still develop a genuine sync issue: audio, which is written from a separately selected input and can carry real latency of its own.
Where camera-to-camera drift actually comes from
Two independent cameras — whether that is two phones or an app design that records the front and back streams as two separate files — each run on their own clock. Even a tiny mismatch between two nominal frame rates compounds over a long take: a fraction of a frame of drift per minute is invisible at first and clearly visible by the ten-minute mark. This is exactly why real multi-camera productions use a clapperboard, a shared timecode feed or a sync tone — something that gives an editor one moment both clips can be trusted to agree on, because the files themselves cannot be.
A casual two-phone reaction video usually skips all of that, which is why the visual reaction so often looks like it lands slightly before or after whatever caused it once you watch the footage back. Nobody starts two phones at exactly the same instant, and nothing corrects for it afterwards.
Why a single composited recording cannot have this problem
A dual-camera app that composites in real time does not record the front camera and then, separately, the back camera. It draws both camera images into one frame on the GPU as they arrive, and writes that one frame to the file — the same frame you are looking at in the viewfinder. By the time anything reaches storage, the two images are already merged. There is no “camera A’s clip” and “camera B’s clip” sitting side by side that could later pull apart, because a composited recording only ever produces one clip, running on one shared timeline, at one fixed frame rate for the entire take.
This is a structural fact, not a performance claim. It is not that the drift is small or well controlled — it is that the category of problem does not apply to a single file the way it applies to two.
The one small gap that can genuinely exist
The front and back cameras still run as two separate capture pipelines up to the moment of compositing, and nothing coordinates them — in the same way nothing coordinates their exposure, where each camera meters and reads only its own scene. So at the pixel level, the two images inside a given composited frame can be a fraction of a frame apart in exactly when their sensors sampled the scene. This does not accumulate into visible drift, because every output frame is built fresh from whatever the two current buffers happen to be — there is no backlog that could grow across a long take, only a fixed, tiny offset that stays roughly the same from the first second to the last. It is real, but it is not something you would notice outside of a frame-by-frame comparison, and it is nothing like the seconds of drift a genuinely separate two-file setup can develop.
Where a real, noticeable sync problem can still happen: audio
A dual-camera recording still writes a single audio track from a separately selected input, alongside the composited video. If that input is the phone’s own microphone, it sits close to the encoder and this is not worth thinking about. If it is a Bluetooth microphone or a pair of AirPods, the audio takes a slower path onto the phone — compressed, sent over radio, decoded — and that adds a consistent delay that can be enough to notice lips moving slightly ahead of the words on a close talking shot. That is a genuine, separate mechanism from anything to do with the two cameras, and it is covered in more depth in the guides on dual-camera audio and on using AirPods for a dual recording.
What a dropped frame does instead
Under real load — heat, or hardware running out of budget — a dual-camera recording can drop frames rather than deliver them late, because a frame that misses its moment would only push the whole pipeline further behind. The point worth knowing is what a dropped frame drops: the entire composited frame, both camera images at once, not one camera’s half of it. So a heavy take gets shorter or visibly choppier under load, but the two views inside it never separate from each other — a stutter is not the start of a drift.
DualCam works this way: both camera images are composited into one frame on the GPU every time, one audio track is written from whichever input iOS has selected, and the file that results is the same recording from the first frame to the last — there is nothing left to synchronise after the fact.
Common follow-up questions
If I record with two separate phones instead, will they stay in sync?
Not reliably, and not for long. Two independent devices run on two independent clocks, and without a shared sync signal — a clapperboard moment, a shared timecode — the two files will drift apart over a take of any real length. This is exactly the problem a single composited recording avoids by only ever producing one file.
Can editing the file afterwards introduce a sync problem?
Only if you separate the video and audio and re-encode or trim them independently. Left alone, the file keeps the same relationship between picture and sound it was recorded with.
Does frame dropping under heat make one camera lag behind the other inside the file?
No. A dropped frame drops the entire composited frame — both camera images together — not one camera’s contribution to it. The two views stay paired through any amount of stutter; what changes is how smooth or how long the take is.
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.