Frame rate and capture interval are two different settings, and mixing them up is why your timelapse came out the wrong length. Here's how to pick both.
Almost every question I get about timelapse settings is actually two questions wearing a trenchcoat. People ask "what fps should I use" when what they mean is "why is my timelapse 4 seconds long."
So before the numbers, the distinction that fixes most of it.
Frame rate and interval are different settings
Capture interval is how often a frame is taken while you're recording. One frame every 2 seconds, one every 10, whatever you set.
Frame rate is how fast those frames play back afterwards. 24fps, 30fps, 60fps.
The interval decides how much real time gets compressed. The frame rate decides how smooth the result looks. They multiply together to give you the final length:
video length (seconds) = frames captured ÷ frame rate
frames captured = session length ÷ interval
A one hour session at a 2 second interval gives you 1,800 frames. At 30fps that's a 60 second video. Change the frame rate to 60fps and the same frames become a 30 second video — smoother, but half as long. Change the interval to 4 seconds instead and you get 900 frames, which at 30fps is also 30 seconds — same length, but choppier, because you're showing fewer moments.
That's the whole relationship. Once it clicks, the settings stop being guesswork.
Just tell me the frame rate
30fps. If you don't want to think about it, use 30 and move on. It's the safe default on every platform, it looks smooth enough for screen content, and every device plays it back correctly.
Here's when I'd pick something else:
24fps — if the timelapse is going into something else that's already 24fps, like a video project or a film-style edit. Mixing frame rates in one timeline causes judder. Match what you're cutting into. On its own, 24 also gives you a slightly longer video from the same frames, which is occasionally useful when you're just short of a target length.
60fps — if there's fast motion in the frame, or you're recording a camera pointed at something physical rather than a screen. 60 costs you roughly double the file size for a difference most viewers won't consciously notice on screen recordings, but on camera footage with movement it's visible.
I'd avoid going above 60. The file grows, the export takes longer, and platforms will often transcode it back down anyway.
Picking the interval
This is the setting that actually matters, and it depends entirely on how long you're recording and how long you want the result to be.
Rough starting points for a video in the 30–60 second range:
| Session length | Interval | Frames at 30fps | Result |
|---|---|---|---|
| 30 minutes | 1 second | 1,800 | 60s |
| 1 hour | 2 seconds | 1,800 | 60s |
| 2 hours | 4 seconds | 1,800 | 60s |
| 4 hours | 8 seconds | 1,800 | 60s |
| 8 hours | 15 seconds | 1,920 | 64s |
The pattern: roughly 1,800 frames gets you a minute at 30fps, so divide your session length in seconds by 1,800 and you have your interval.
Rather than doing that in your head every time, I put it in a time lapse calculator that works it out in any direction.
Err on the side of a finer interval
If you're unsure, capture more often than you think you need.
You can always drop frames afterwards — thinning a 2 second interval to an effective 4 seconds is trivial, and every editor will do it. You cannot invent frames that were never captured. If you set 10 seconds and the result turns out too choppy, the session is gone.
The cost of a finer interval is disk space and a slightly bigger export, which are cheap. The cost of too coarse an interval is re-recording something you can't re-record.
What actually makes it look choppy
Frame rate gets blamed for this and it's usually not the culprit.
If your timelapse looks jumpy, it's almost always the interval being too long relative to how fast things are moving on screen. Bumping playback from 30fps to 60fps won't help — you'll have the same number of distinct moments, just displayed for less time each. It may even look worse.
The fix is a shorter capture interval next time. There's more on diagnosing this in why is my timelapse choppy.
Where the settings differ by platform
Worth knowing before you export:
- YouTube handles 24, 30 and 60 natively. No reason to avoid 60 here.
- Instagram and TikTok will re-encode whatever you give them. 30fps is the safe choice; 60 often gets transcoded down anyway, so you paid for file size you didn't keep.
- X compresses aggressively. Keep it at 30 and keep the video short.
- Embedding on your own site — 30fps, and consider WebM alongside MP4 for the file size.
The short version
Set the frame rate to 30 unless you have a specific reason not to. Spend your attention on the interval instead, because that's the one that decides whether you end up with a 4 second clip or a 4 minute one. And when in doubt, capture more often — you can throw frames away later, but you can't get them back.