How long can you record dual camera video on iPhone?

Why there is no fixed maximum

A single-camera video has essentially one constraint: storage. A dual-camera recording runs two capture pipelines, composites them into one frame on the GPU every frame, and hardware-encodes the result, so it draws far more from the phone than a normal video does. That extra load is exactly what turns two more variables — heat and battery — into real limits instead of theoretical ones. None of the three has a fixed value; each one depends on your specific phone, its age, the weather, and the resolution you picked.

Storage: the one with a clean number attached

This is the only one of the three you can calculate in advance. DualCam encodes at roughly 10 Mbps, which works out to about 75 MB per minute of finished video — a little over 4 GB an hour. The app requires at least 200 MB free to start a recording at all, and stops an in-progress one once free space drops under 100 MB, so a take always gets closed cleanly instead of running the disk dry mid-write.

Rough capacity, at a glance

On a phone with plenty of free space, storage is rarely the limit that actually stops you — heat usually gets there first. It is still worth checking before a take you cannot reshoot, since it is the one ceiling you can move by simply deleting something.

• 1 GB free ≈ 13 minutes
• 5 GB free ≈ 66 minutes
• 10 GB free ≈ 2 hours 13 minutes

Heat: usually the one you hit first

Two live camera pipelines plus a GPU composite plus an encoder generate more heat than any single-camera recording does, and iOS tracks the phone’s thermal state and reacts to it in steps. On a hot day, in direct sun, or on an older supported iPhone, this is typically what ends a long dual-camera take, well before storage becomes a factor — a 45-minute interview is far more likely to end because the phone got hot than because the disk filled up.

A case that traps heat, a phone that was fast-charging right before you started, and a screen at full brightness the whole take all push you toward that ceiling faster. None of them change how much storage you have; they only change how soon heat becomes the actual constraint.

Battery: rarely the limit on its own, but it stacks

Running two camera pipelines and a GPU composite draws more power than single-camera recording, which is a real cost but not usually the one that ends a take by itself — most phones can sustain a long dual recording well past the point storage or heat intervene, as long as they started with a reasonable charge. The exception is charging while you shoot: it adds its own heat on top of what recording already generates, which is more likely to push you into the thermal ceiling than to spare the battery.

Planning a take that needs to run long

• Clear real storage space before you start, not just enough to pass the 200 MB minimum — you want headroom for the whole planned length, not just the first few minutes.
• Take the case off, especially anything thick or insulating, if the take matters and might run long.
• Shoot on battery rather than plugged in; charging adds heat on top of what recording already generates.
• Use 720p instead of 1080p for anything past a few minutes — it roughly halves the pixel throughput each camera has to push, which lowers both heat and battery cost, not just file size.
• If a single take genuinely needs to run past twenty or thirty minutes, plan for the possibility that heat ends it early, and treat what you get as a finished, if shorter, file rather than a failed one.