Guide
How to Make a Variable Speed Timelapse
Short answer
A variable speed timelapse is one whose playback speed changes as it goes: slow while something is happening, fast through the still stretches. There are three ways to make one — let the camera vary the speed while you shoot, ramp the speed by hand with keyframes in a video editor, or let software read the footage and set the speed for you.
One question narrows it fast: has the footage already been shot? If it has, the in-camera route is off the table.
A timelapse that runs at one speed spends the same slice of your video on the morning the crane showed up and the afternoon it rained and nobody came. Varying the speed fixes that: the work gets room to breathe, the quiet stretches go past quickly, and the shoot stays whole. This page walks all three ways to do it — including the two that have nothing to do with our software — and says what each one is bad at.
The short answer
Picture the speed of a timelapse as a dial. On a normal one it is glued in a single position for the whole clip. Making a variable speed timelapse means unsticking that dial and deciding — or letting something else decide — where it sits moment by moment. Done well the changes are gradual, so on screen it reads as the video breathing rather than as a cut.
So the real question is not how so much as who turns the dial: your camera while you shoot, you at a keyboard afterwards, or software reading the footage. Those are the three methods, and they are not interchangeable — the first one is only available before you press record.
The three ways to make one
Side by side, on the four things that decide which one you can actually use. The middle column settles most arguments on its own.
Scroll the table sideways to see every column
| Method | What sets the speed | Works on footage you already shot? | Effort | Best for |
|---|---|---|---|---|
| In camera, while you shoot | The camera, from a timer it stretches as the recording runs on | No — it is baked in at capture | Low: pick a mode before you start | Short clips you are shooting right now |
| By hand in a video editor | You, one keyframe at a time | Yes | High: you must watch the raw footage first, then place every ramp | Short hero clips you want to control second by second |
| Automatically, from the footage | The footage — how much moved between each pair of frames | Yes | Low: one switch, then a ceiling to taste | Long fixed-camera shoots where the work comes in bursts |
Speed through the shoot
- One speed, picked up front
- Speed set by the footage
The rest of the page takes each one in turn: how you actually do it, and the catch nobody mentions until you are halfway through.
Method 1: In camera, while you shoot
Some cameras vary the speed for you as they record. Phone time-lapse modes are the common version: an iPhone keeps stretching its own capture interval as a recording runs on, so a one-hour and a four-hour shoot both come out roughly the same length. That is the camera changing the speed — but it changes it for the whole clip, not for the interesting parts of it.
How to do it: on a phone, open the time-lapse mode and hit record. That is the entire procedure, and that is the appeal.
The catch: it is baked in at capture
The camera writes one finished video and only that video. The frames it skipped were never saved, so there is no going back afterwards to slow a moment down — you would be stretching frames that do not exist. And the rate it picks is a timer, not a judgment: it knows how long the recording has run, not what is happening in front of the lens, so the busy hour and the empty one come out compressed exactly alike.
Method 2: By hand in a video editor
This is the classic answer, and every editor has it: a speed ramp, also called time remapping. You put the clip on a timeline, drop keyframes onto its speed, tell the editor what the speed should be at each one, and then smooth each change so it eases in rather than jumping — a bare keyframe is an instant switch, not a blend. Premiere Pro, DaVinci Resolve, Final Cut Pro and CapCut all do it. The menus differ; the idea does not.
- Put the timelapse on the timeline and scrub it once, marking the moments worth slowing down.
- Open the clip’s speed curve — Time Remapping in Premiere Pro, the Retime Curve in DaVinci Resolve, Retime in Final Cut Pro.
- Add a keyframe just before and just after each of those moments.
- Set the speed low between the pair of keyframes, and high across the stretch between one moment and the next.
- Drag the handles on each keyframe apart so the change eases in over a second or so instead of snapping.
This is the method that gives you the most control. You are placing every change deliberately, so the video lands exactly where you want it to and nothing surprises you.
The catch: it does not scale
On a twenty-second clip this works well — every ramp is one you placed on purpose. The problem is finding the moments. To place a ramp you have to know where the interesting parts are, and the only way to know is to watch the raw footage — days of scrubbing on a four-month jobsite shoot before you touch a single keyframe, and most of the ramps move if you re-cut anything. This is the single most common reason long timelapse footage sits on a drive, unedited, forever.
Method 3: Automatically, from the footage
The third route removes the part that does not scale: instead of you finding the busy moments, software finds them. It compares each frame with the one before it and scores how much of the picture actually changed, smooths those scores so a passing truck or a cloud shadow does not throw it, then turns the result into a speed for every moment of the clip. Busy stretches settle back to the base speed. Quiet ones climb toward a ceiling you choose.
The technique has a name — this is what adaptive pacing is — and a video made this way is called an adaptively paced timelapse. What separates it from the other two methods in practice: hundreds of speed changes end up in the clip, you placed none of them, and you never had to watch the raw footage to find out where they belonged.
There is nothing cut out, either. The rained-out week is still in the video from first frame to last; it just goes by in a couple of seconds instead of a couple of minutes. Cutting those stretches away entirely is a different edit, usually called trimming.
Which method should you use?
Two questions get you there.
- Is the footage already shot? If it is, cross off method 1. Pacing is only available in camera before you press record.
- How long is the raw shoot? Short enough to watch straight through, doing it by hand is practical and puts every ramp under your control. Hours, weeks or months, do it automatically, because nobody watches four months of footage to find the good parts.
Let the footage set it
- A camera sat in one place for weeks or months — a build, a remodel, a barn raise.
- The interesting part is a small slice of the recording and the rest is nights, weekends and weather delays.
- The footage is already on a card and you are not going back to re-shoot it.
- You want it finished today, not over a weekend of scrubbing.
Set it yourself
- The clip is short enough to watch straight through, and you want a hand on every ramp.
- The moment you want to hold on is a quiet one that no movement score would notice.
- You are cutting to music and every speed change has to land on a beat.
Still planning the shoot rather than editing it? Start with the long-term timelapse guide. Interval, power and framing decide far more about the finished video than pacing ever will. Pacing is the last decision, not the first.
Making one in Tweedia Studio
MotionPace is Tweedia Studio's implementation of the third method. It runs on a shoot you have already filmed — a clip off a jobsite camera, or a folder of stills — and it is four steps end to end.
- Upload the shoot. A video file or a folder of stills, from any camera — a jobsite camera, a GoPro, a phone on a windowsill, a DSLR on an intervalometer.
- Switch MotionPace on for that video. There is nothing to mark up and no timeline to drag.
- Set the ceiling. Max speed is how fast the still stretches are allowed to get: anywhere from 1.5× to 15× the base speed. Near the bottom it reads as a gentle drift; near the top the quiet hours genuinely fly. A Smoothness setting decides how gradually each change arrives.
- Watch the preview, then render. The paced preview updates before you render, so you can try a setting without spending anything. Credits are charged on the finished video.
The ceiling is the only number you need an opinion about, and it only ever governs how fast the quiet gets: wherever you put it, the busy stretches settle back to the base speed.
See it on real footage
The MotionPace page charts an actual deck build — days of a fixed camera, paced automatically, with nothing cut out — against the same footage at a constant speed.
How MotionPace works →FAQ
What is a variable speed timelapse?
A variable speed timelapse is one whose playback speed changes as it goes: slow while something is happening, fast through the still stretches. There are three ways to make one — let the camera vary the speed while you shoot, ramp the speed by hand with keyframes in a video editor, or let software read the footage and set the speed for you.
Can I change the speed of a timelapse I already shot?
Yes, as long as the camera recorded at one steady rate — a normal timelapse clip or a folder of stills. You can ramp it by hand in any video editor, or have software do it from the footage. What you cannot undo is a camera that already varied the speed for you: that decision was written into the file at capture and the skipped frames were never saved.
How do I make a speed ramp in a video editor?
Open the clip’s speed curve — Time Remapping in Premiere Pro, the Retime Curve in DaVinci Resolve, Retime in Final Cut Pro — then add a keyframe either side of each moment you want slowed, set a low speed between that pair and a high speed across the stretches in between, and drag the keyframe handles apart so the change eases in instead of snapping.
Does varying the speed cut footage out?
No — nothing cut out. The whole shoot is still in the video from first frame to last; the still stretches simply go past faster. Cutting those stretches away entirely is a different edit, usually called trimming.
How much faster should the quiet parts play?
That is your call. In Tweedia Studio you set a ceiling anywhere from 1.5× to 15× the base speed, and the busy stretches settle back to the base speed no matter where the ceiling sits. Start low on a shoot where small changes matter, and push it up on a shoot with long quiet runs.
Do I need a special camera for it?
Only for the in-camera method. The other two happen in the edit, so any footage works — a jobsite camera, a GoPro, a phone on a windowsill, or a folder of stills from a DSLR.
What is a timelapse made this way called?
It depends which method made it. When the footage sets the speed, the technique is adaptive pacing and the result is an adaptively paced timelapse. When you place the changes yourself, the changes are called speed ramps. Either way the file is a normal MP4 you can post anywhere.
Try it on a shoot you have already filmed
Upload footage you filmed months ago, let the movement in it set the pace, and watch a draft before you spend a credit.
Tuning and previewing are always free. Credits are charged on a finished render.