How to Shoot a Timelapse on iPhone in Both Portrait and Landscape
A timelapse is the highest-effort-per-second content you can make: you commit twenty real minutes to get eight usable seconds. Which makes the usual outcome doubly painful: you shot it vertical for Reels, and now the YouTube edit needs a horizontal version that doesn't exist.
This guide covers the craft basics that make timelapses look deliberate, and how to walk away from one session with both orientations.
The maths: how long to shoot
Decide the output length first, then work backwards. A timelapse that speeds reality up 20× turns 20 minutes of the world into 60 seconds of footage. Rough guide by subject:
| Subject | Speed | Real time for 15s of output |
|---|---|---|
| Street traffic, people walking | 10–15× | 3–4 minutes |
| Sunset / sunrise | 20–30× | 6–8 minutes |
| Clouds on a windy day | 20–40× | 5–10 minutes |
| Slow clouds, shadows moving | 60×+ | 15+ minutes |
When in doubt, shoot longer than you think. You can always cut an over-long timelapse; you cannot extend one that ended before the sun finished setting.
The three things that ruin timelapses
1. The phone moved
At 20× speed, a one-millimetre wobble becomes a visible jolt. Tripod if you have one; if not, lean the phone against something solid and don't touch it after framing. Start recording with the timer or a gentle tap, then step away. Wind is a real enemy on lightweight phone tripods: shelter the setup or weigh it down.
2. Exposure pumping
Auto exposure re-meters constantly. Compressed 20×, those little corrections become distracting flicker, most visible in skies. Lock exposure before you start. In ContentCam, set EV or full manual ISO/shutter, and it stays put for the whole session. For sunsets, expose for the sky about a third of the way into the expected run, so the start isn't blown out and the end isn't black.
3. White balance drift
Same problem, colour version: as light warms toward sunset, auto WB keeps "correcting" the very colour change you're there to film. Lock white balance (around 5600K for a sunset) and let the light do its thing on camera.
Getting both orientations from one session
Here's the part that used to require two phones. ContentCam's timelapse is dual-format like every other recording mode: the session captures the sensor's full 4:3 frame and produces a 9:16 timelapse and a 16:9 timelapse from the same minutes. The full-FOV crop approach means the landscape version genuinely shows the wide scene, not a strip of the vertical.
Frame for both before you start: skyline in the horizontal band for the landscape file, foreground interest in the vertical column for the portrait. The preview shows both crops, so you're not guessing.
Practical notes from how it's built: timelapse runs single-lens at 30fps output, audio is skipped (nobody wants 20 minutes of wind noise sped up), 4K is available on supported iPhones, and if something interrupts the session (a call, a low battery warning), the recording is recovered rather than lost. Timelapse is a premium feature.
Quick pre-flight list
- Battery above 40%, or plugged in for long sessions
- Storage: a few GB free for long 4K sessions
- Do Not Disturb on (notifications won't kill the recording, but the banner in your eyeline is annoying)
- Phone braced or tripod-mounted, wind considered
- Exposure locked, white balance locked
- Both crops checked in preview
- Walk away. Watching it doesn't make it go faster.
Related: Manual controls explained · How dual-format recording works
