What happens if your iPhone runs out of storage while recording dual camera video?
Nothing dramatic. DualCam checks for at least 200 MB of free space before it will let a recording start at all, and once a take is running, it stops itself the moment free space drops under 100 MB — well before the phone genuinely has nowhere left to write a frame. Whatever was captured up to that point is finalized as one complete, playable file, the same as any other interruption a dual-camera recording can hit.
The more useful question is not whether the footage survives — it does — but how much recording time a given amount of free space actually buys you, and why the app leaves that 100 MB on the table instead of using every last byte.
Why it stops itself with storage still technically left
Finishing a video file cleanly is not the same as writing its last captured frame. Closing a recording out — so the file has a valid ending and opens normally instead of failing to play at all — takes a small amount of writing on top of the frames already on disk. A recording that kept accepting new frames right up to the very last free byte on the phone would have nowhere to put that closing step, and the take could be left in a state where the frames exist but the file itself is not usable.
The 100 MB threshold exists to keep that from happening: DualCam ends the take itself, with enough headroom left to finish the file properly, rather than waiting for the operating system to refuse a write it has no room for. The 200 MB check before a recording is even allowed to start follows the same logic one step earlier — there is no point beginning a take that would not have room to close out cleanly even a few seconds in.
How much free space a given shoot actually needs
DualCam encodes the finished, composited video at roughly 10 Mbps, which works out to about 75 MB for every minute recorded — a little over 4 GB for a full hour. That is the size of the one file that gets written; recording two cameras at once does not double it, because the output is a single composited clip rather than two separate camera files.
Add the 100 MB the app keeps in reserve to close the file, and it is straightforward to work out roughly how much free space a planned shoot needs before you start, rather than finding out mid-take:
Rough targets, at a glance
On a phone with plenty of room, storage is rarely the limit that actually ends a long take first — heat usually gets there before the disk does. It is still the one ceiling worth checking on purpose, because it is the only one of the two you can move in advance simply by deleting something.
- A 5-minute take needs roughly 475 MB free.
- A 15-minute take needs roughly 1.2 GB free.
- A 30-minute take needs roughly 2.3 GB free.
- A full hour needs roughly 4.6 GB free.
What happens to the footage that was already recorded
DualCam does not record the front and back cameras as two separate files that would need to be reconciled afterward. It draws both live images into one frame on the GPU as they arrive and writes that single composited frame to disk, so there is only ever one file for the whole take, from the first frame to whichever frame turned out to be the last. Running out of room simply stops new frames from being added to it — it does not leave two mismatched clips behind, and there is no separate audio track that can fall out of sync with anything.
Because the take is closed out with that 100 MB of headroom still in hand, the file this produces is not a broken or partial write either. It opens and plays normally, just as a shorter recording than the one you intended — the same way a dual-camera recording ended early by heat or a phone call is handled, closed out as a complete file rather than left corrupted mid-write.
Where a take like that ends up
A recording that gets cut short by storage still lands in DualCam’s own library the same way a full-length one would, with a thumbnail you can scrub through before deciding whether it is worth keeping. It has not touched iCloud at any point — the app’s library is local storage on the phone, and nothing in it uploads anywhere until you deliberately save a specific clip to Photos.
That review step is also the direct fix if storage keeps running tight: clips sitting in the app’s own library that you have already saved to Photos, or simply do not need, are the actual weight on your free space. Lowering DualCam’s resolution setting will not free much of it — the app encodes at close to the same bitrate at 720p and 1080p, so the two take up a similar amount of storage per minute. What buys you room is deleting something, not shooting smaller.
Checking before you shoot instead of after
- Open Settings → General → iPhone Storage before a take that matters, rather than trusting a vague sense of how much room is left.
- Use the rough numbers above for the length you are actually planning, not just enough to clear the 200 MB minimum to start — that check only promises the first few seconds, not the whole take.
- Offload or delete recordings already saved to Photos, or clips in DualCam’s own library you know you will not keep, rather than lowering resolution to try to buy more room.
- If a take genuinely cannot be reshot, treat the free-space check as part of getting ready the same way you would check heat or battery, not an afterthought.
Common follow-up questions
Will DualCam warn me before storage runs out mid-recording?
There is no separate countdown to watch. The app checks free space before it lets a recording start at all, requiring at least 200 MB, and if space runs low during a take it stops itself once free space drops under 100 MB, closing the file out cleanly rather than waiting for the phone to run out of room entirely.
Will I lose the video if storage runs out while I am recording?
No. Whatever was captured up to the moment storage forced the take to stop is finalized as a complete, playable file — shorter than you planned, but not corrupted or missing, the same way DualCam handles any other interruption mid-recording.
Does recording at 720p instead of 1080p let me fit more storage-wise?
Only marginally. DualCam encodes at close to the same bitrate regardless of resolution, so 720p and 1080p land in a similar range for storage per minute. A lower resolution mainly buys headroom against heat on a long take, not against free space — freeing real storage is what actually moves that ceiling.
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.