How to film a running vlog with both iPhone cameras
A running vlog works on the same idea as any other dual-camera reaction shot: the road or trail ahead and your face experiencing it, landing in the same frame at the same second. What sets it apart from filming a walk through a city block is that a run rarely leaves a free hand for very long, and the motion of running itself does things to a camera that walking mostly does not.
The two decisions that actually matter for a running vlog are not about layout. They are how you hold the phone, and how much heat and battery a route you cannot pause for lets you spend. Get those right and the rest — which corner the small window sits in, which filter you pick — is the same choice it would be for any other dual-camera shot.
Holding it is what makes the front camera worth having
DualCam’s reaction premise depends on the front camera actually being pointed at your face. Hold the phone the way you would for any other dual-camera shot — chest-high, screen facing you — and picture-in-picture does exactly what it does everywhere else: the back camera fills the vertical canvas with the road or the trail, your face sits in a small corner window, and either feed can be made the main view or swapped to the inset while you are still recording, the same as moving that window to a different corner or resizing it.
A running armband or a waist pack solves a real problem — nobody wants to carry a phone in a fist for an hour — but it solves it by pointing the front camera at your forearm or the inside of a pocket instead of your face. What comes out the other end is two feeds of not much, not a face-and-road pairing. If the reaction is the point of the video, the phone needs to be held or mounted facing you — a chest harness built for running works, an arm or wrist band generally does not — and that trade-off is worth making before you start rather than discovering it in the file afterwards.
Running shakes the frame in a way walking does not
Every phone camera sensor reads a frame line by line rather than all at once, which is why fast enough motion during that read can make part of the image lean or wobble — the same rolling-shutter skew that shows up on a whip pan or a spinning fan blade. Walking introduces a mild, fairly steady version of this. Running introduces a much bigger one: a stride bounces the whole upper body on every step, and a hand swinging with your arm adds a second motion on top of it, so the sensor is reading each frame while genuinely moving fast, not just drifting.
It shows up worse in a picture-in-picture inset than it does full-frame, because the inset is already a small, cropped window and the same wobble now covers a larger share of it. A low, two-handed grip held close to the chest cuts a lot of this out simply by removing the arm swing; a small handheld gimbal or a running-specific chest mount absorbs the vertical bounce a hand alone cannot. None of this is a resolution setting — 720p and 1080p read a line at exactly the same speed, so switching between them does nothing for the wobble.
Heat and battery, with nowhere to cool off
Two live camera feeds, a GPU compositing pass on every frame and a hardware encode already make dual recording one of the more demanding things a phone does, and a run works against cooling in a way a mounted, stationary shot does not — the phone is either gripped in a warm hand or strapped against skin, with none of the airflow a dashboard or tripod mount gets for free. DualCam watches the phone’s thermal state and responds in steps: at the “serious” level it drops an unstarted 1080p recording to 720p before you begin, and if the phone keeps heating up during a take, it ends the recording and saves the file rather than pushing through.
For anything close to race distance, treat 720p as the default rather than something you switch to after the phone warns you — it roughly halves the pixel throughput each camera has to push, which is a real cut to how hard the phone works for the whole run, not just a smaller file. Start fully charged, since there is no outlet on a course, and skip a thick or insulating case for the same reason you would on any long take: it traps exactly the heat a run is already generating.
The file grows faster than the distance does
A dual-camera recording runs as one continuous file from the moment you press record to the moment you stop — there is no pause button to freeze it at a water stop and resume later in the same take. At DualCam’s recording bitrate of roughly 10 Mbps, that file grows at about 75 MB per minute, so a 5K run at a 30-minute pace comes to a little over 2 GB recorded straight through, and a two-hour half marathon comes to close to 9 GB if you tried to capture the whole thing in one file.
Few running vlogs actually need the whole distance. The start line, a specific mile marker, a hard hill, the finish are usually the parts worth having, and everything between them is exactly the kind of stretch a long hike treats as fine to stop and start a new take through. Deciding which stretches matter before you start, and stopping cleanly between them, costs far less battery, heat and storage than one long file trimmed down afterwards, and DualCam keeps every take as its own file in the app’s library, so picking the good parts later does not get any harder for having shot it that way.
One microphone for your breathing, the wind and the crowd
A dual-camera recording carries a single audio track from a single microphone, not one per camera, and on a run that one track picks up your breathing, your footfall, wind moving past the phone and, on race day, whatever a course full of people happens to be doing, all mixed into the same signal. There is no separate channel to turn any one of those down afterwards.
What that means in practice depends on what you are actually running. A solo training run into the wind is a case where muting and adding music or narration afterwards is often the better call, the same as it would be for any exposed outdoor shot — and mute has to be set before you press record, because the track either exists from the first frame or does not exist at all. Race day is usually the opposite: the crowd is part of what makes the footage worth having, imperfect as the mix might be, and it is not something a quieter training run would ever give back.
Common follow-up questions
Can I record a whole marathon in one dual-camera file?
Technically yes, but it costs more than the distance is usually worth. A continuous file at DualCam’s recording bitrate runs to roughly 75 MB a minute, so several hours comes to tens of gigabytes, and a phone strapped to your body that long with no airflow is exactly the situation the app’s thermal safeguards exist for. Recording a handful of takes at the moments that matter — the start, a landmark, the finish — uses a fraction of the battery and storage and gives you the footage you would actually use.
Does wearing the phone in an armband ruin the reaction shot?
It removes it rather than ruining it. An armband points the front camera at your arm, not your face, so you get two feeds of not much instead of a face-and-road pairing. If the reaction is the point, hold the phone or use a chest mount built for running that keeps it facing you — an arm or wrist band is the better choice only once the face shot has stopped mattering to you.
Should I shoot at 720p or 1080p for a run?
720p, for anything past a short training loop. It roughly halves the pixel throughput each camera has to push, which is a real reduction in how hard the phone works and how much heat it builds over a run with no airflow, and DualCam will drop an unstarted 1080p recording to 720p on its own if the phone is already running hot before you start.
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.