Choppy timelapse? It's almost never the frame rate. Six things that actually cause it, how to tell them apart, and what to change next time.
You exported the timelapse, watched it back, and it stutters. Things jump instead of flowing.
The usual first instinct is to raise the frame rate, and that almost never works — I'll explain why below. There are about six things that cause this and they have different fixes, so it's worth spending two minutes working out which one you've got.
1. Your capture interval is too long
This is the cause maybe 70% of the time.
If you captured one frame every 10 seconds and the thing you're filming moves meaningfully within 10 seconds, every frame is a big jump from the last. Played back, that reads as stutter — because it genuinely is stutter. There's no motion between those moments, because you never recorded any.
How to tell: step through the video frame by frame. If each individual frame is sharp but the content leaps between them, this is your problem.
Fix: shorter interval next time. For screen work — code, design, writing — I'd stay at 2 seconds or below. For something slow like a sunset or a 3D render, 10 or 15 is fine because very little changes in that window.
You can't fix this one in post. The moments in between were never captured.
2. You're confusing it with frame rate
Raising playback from 30fps to 60fps does not add information. You have the same number of distinct frames; each one is now on screen for half as long. The video gets shorter and the jumps come at you faster.
If anything, this makes choppiness more noticeable, which is why the instinctive fix so often backfires.
Frame rate smooths playback only when you have enough frames to fill it. The interval decides whether you do. There's a fuller explanation of how the two interact in what frame rate should you use for a timelapse.
3. The player is dropping frames, not the file
Sometimes the export is fine and the playback isn't.
How to tell: try the same file in a different player — VLC, a browser, your phone. If it's smooth in one and choppy in another, the file is fine.
This happens most with very high resolution exports on machines that are busy doing something else, and with GIFs, which browsers throttle. It also happens a lot in the preview scrubbers inside editors, which are not a reliable way to judge a final export.
4. Variable frame rate in the source
If you recorded with a tool that writes variable frame rate (VFR) — most phone cameras and a lot of general screen recorders do this by default — and then sped it up in an editor, the timing goes strange. Frames are unevenly spaced in time and the speed-up amplifies the unevenness.
How to tell: the stutter is irregular. Smooth for a moment, jump, smooth again, with no pattern to it.
Fix: convert to constant frame rate before editing. With ffmpeg:
ffmpeg -i input.mp4 -vsync cfr -r 30 output.mp4
Recording at a fixed interval sidesteps this entirely, because every frame is deliberately spaced.
5. Something on screen moved too fast to capture
A specific screen-recording version of problem 1.
If you're recording a coding session at a 2 second interval and you scroll a long file, the scroll happens between frames. You get "top of file" then "bottom of file" with nothing in between, and it reads as a glitch rather than motion.
There's no interval that fixes fast scrolling short of recording at full frame rate. What helps in practice is being slightly aware of it while working — big instant jumps look bad in a timelapse regardless of settings. Not worth obsessing over, but worth knowing why it happens.
6. The export re-encoded badly
Less common, but it happens: the source is smooth and the export isn't. Usually a low bitrate on a high-motion export, which produces compression artefacts that read as judder.
Fix: export at a higher quality setting, or a lower resolution at the same quality. If the platform is going to re-encode anyway, giving it a cleaner source produces a better result at the other end.
Working out which one you have
Quickest path:
- Play the file in a different player. Still choppy? It's the file, keep going. Smooth? It was playback.
- Step through frame by frame. Sharp frames with big content jumps means the interval was too long.
- Irregular, unpredictable stutter usually means variable frame rate. Convert to CFR.
- Smearing or blockiness rather than jumping is a bitrate problem, not a timing one. Re-export at a higher quality.
The honest summary
Most choppy timelapses are a capture decision, not an export setting — which is frustrating, because it means the fix is "record it again with a shorter interval" rather than something you can apply to the file you already have.
The upside is that it's very learnable. Once you've matched an interval to a type of work a couple of times you stop getting it wrong. My defaults: 1–2 seconds for coding and design, 5 for long writing sessions, 10 or more for anything physical and slow. If you'd rather work it out from your own session length than borrow mine, the frame interval calculator does the arithmetic.