What a velocity edit actually is
A velocity edit is not just “slow motion” or “fast motion.” It is a clip whose playback speed changes over time, in sync with music or movement — slow on a dramatic beat, fast through a transition, then back to normal speed. The speed changes are the edit. If the speed jumps suddenly from one fixed speed to another, the result looks choppy. If the speed ramps smoothly between values, it looks intentional and professional.
That is why this guide is built around speed keyframes and easing, not around fixed speed presets. A preset can give you a starting point, but a beat-sync edit needs control at specific moments in the clip.
Before you start: choose the right clip and song
Velocity edits work best on clips with visible movement — dance, sport, travel, or any action where slowing down reveals something and speeding up creates energy. A static talking-head clip will not benefit much from velocity work, however carefully you keyframe it.
Pick a song first, not last. Beat-sync editing means the speed changes land on musical events: a bass drop, a snare hit, a change in section. If you choose the song after the edit, you will be forcing cuts to fit music that was never part of the plan.
Practical setup, in general terms:
- Start a new project at the resolution and frame rate you intend to export at. Changing these later can change how smooth slow motion looks.
- Import your video clip and your audio track as separate layers so you can adjust each independently.
- If your clip was shot at a low frame rate, do not expect very slow motion to look smooth — slow motion needs frames to work with. This is a limitation of the source footage, not a setting you can fix in the app. High-frame-rate source footage gives smoother slow-motion results.
Step 1: Mark the beats
Play the audio and place markers where the speed should change. The most useful markers are:
- The downbeat where a section starts.
- A bass drop or accent where you want the clip to slow down and hold attention.
- The beat where a fast section should begin again.
Do not mark every beat in the song. Mark only the moments where speed changes. Too many markers make the edit busy and hard to control; three to five well-placed speed changes usually beat twenty small ones.
If you are editing to a specific trend or song, listen to the track a few times before marking. The pattern of drops and builds tells you where the slow and fast sections belong — the edit should follow the music, not fight it.
Step 2: Split the clip at the markers
Split the video layer at each marker so each section can have its own speed behaviour. Splitting does not delete anything; it gives you control points. Keep the audio layer intact — do not split the audio at the same points unless you have a reason to, because splitting audio can create clicks or gaps.
A common beginner mistake is to split too finely and then lose track of which section is which. Name or order your sections mentally by their musical moment (“intro,” “drop,” “build”) rather than by their position on the timeline.
Step 3: Set speed with keyframes, not fixed speeds
For each section, set the speed using keyframes on the speed control, rather than applying one fixed speed to the whole clip. The workflow, in general terms, is:
- Select the video layer and open its speed controls.
- Add a speed keyframe at the start of a section and another where the speed should reach its new value.
- Set the first keyframe to the starting speed and the second to the target speed — for example, normal speed into a slow section, then back to normal or fast speed for the next section.
- Repeat for each section, so the clip speeds up and slows down in sequence.
The key point is the transition between keyframes. If two keyframes have very different speeds and are close together, the change will feel abrupt. If they are spaced further apart, the change ramps gradually. Space your keyframes to match the music: a sudden drop can justify a faster ramp; a smooth build usually wants a slower ramp.
Step 4: Ease the speed changes
Easing is what separates a smooth velocity edit from a jerky one. Alight Motion’s keyframe system includes easing curves — the same concept covered in the Keyframes guide. For velocity work:
- Use an ease-in / ease-out curve on speed keyframes where you want a natural acceleration or deceleration, rather than a linear change.
- A linear speed change can feel mechanical. An eased change feels like a camera slowing down or speeding up.
- Preview the section after changing the curve. Small curve adjustments make a large visible difference, so change one thing at a time and preview.
If a speed change still looks choppy after easing, the problem is usually spacing (keyframes too close together) or source footage (too few frames for the slow section), not the curve itself. Fix spacing first.
Step 5: Keep audio in sync
Speed changes affect video, but your audio track should stay in time with the song. Two rules:
- Do not speed up or slow down the music track to match the video. The music is the reference; the video follows it.
- If a slow section makes a sound effect or dialogue sound wrong, check whether that sound belongs to the video layer or the audio layer, and adjust only the video layer’s timing.
If you add sound effects (a whoosh on a fast section, for example), place them on the musical beats you marked in Step 1, not at arbitrary timeline positions. Effects that land off-beat are the most common reason a velocity edit feels “off” even when the video speed is correct.
Step 6: Add motion blur and effects sparingly
Motion blur can make fast sections look smoother and slow sections look more cinematic, but it is not a fix for choppy speed changes. Add it after the speed work is done, preview it, and remove it if it makes the clip look muddy rather than smooth.
The same applies to shake, glow, and other effects. A velocity edit with one well-placed effect on a drop usually looks better than a velocity edit with an effect on every section. If you want a shake effect, follow the dedicated Shake Effect tutorial rather than improvising shake keyframes here, and keep the shake synced to the same beat markers.
Step 7: Export for the platform you are posting to
Export settings are covered in detail in the Export Settings guide; the velocity-specific points are:
- Export at the frame rate you edited at, or higher if the platform supports it. Dropping frame rate at export can undo smooth slow motion.
- For TikTok, Reels, and Shorts, use a vertical project and the platform’s recommended resolution and frame rate — check the Export Settings guide for the current platform guidance, separated from general recommendations.
- Preview the exported file, not just the in-app preview. Export can reveal stutter that the timeline preview hides, especially on slower devices.
- If export fails or stutters, do not immediately re-export at a lower quality. Check the Export Failed troubleshooting guide first — the cause is often storage, project complexity, or a problematic media file, not the export settings themselves.
A worked example (illustrative, not a preset)
Song structure: intro (4 beats) → drop → build → outro.
- Intro: normal speed, no speed keyframes. Let the viewer see the clip clearly.
- Drop: speed keyframes ramp down to slow motion over the first beat of the drop, hold slow through the dramatic moment, then ramp back up over the next beat.
- Build: speed keyframes ramp up to fast motion, with an eased curve so the acceleration feels continuous, not stepped.
- Outro: return to normal speed for the final beat, so the edit ends cleanly rather than mid-ramp.
This is a pattern, not a recipe. Different songs need different patterns, and the pattern should follow the song you chose, not the other way round.
Common mistakes and how to fix them
| Mistake | What it looks like | Fix |
|---|---|---|
| Speed jumps suddenly | Clip lurches between speeds | Space speed keyframes further apart; add easing |
| Too many speed changes | Edit feels busy, nothing stands out | Keep 3–5 speed changes; remove the weakest ones |
| Slow motion looks choppy | Stuttering in slow sections | Source footage frame rate is too low for that slowdown; use a smaller slowdown or different footage |
| Audio drifts out of sync | Music and video no longer line up | Check you did not change the audio layer’s speed; re-align video sections to the beat markers |
| Effects on every section | Edit looks cluttered | Keep effects to the drop and one other moment; remove the rest and preview |
| Export looks worse than preview | Stutter or quality drop after export | Preview the exported file; check the Export Failed guide; do not just lower quality and re-export |
What this guide does not do
- It does not recommend a specific preset pack, XML file, or third-party download. Preset files from unknown sources carry the risks described in the Safety guide, and a velocity edit built from your own keyframes does not need one.
- It does not promise that any edit will go viral, rank, or perform on any platform. Performance depends on the content, the song, and the platform, none of which this guide controls.
- It does not claim to have been tested on a specific device or app version. The workflow above is a general Alight Motion workflow.
Frequently asked questions
Do I need a paid subscription for velocity edits?
Speed keyframes and easing are core editing features. Whether a specific export option (resolution, watermark removal, frame rate) requires a subscription depends on the current official pricing — check the official store listing rather than relying on a guide’s pricing claim, because pricing changes. This guide does not state a price.
Can I do velocity edits on iOS?
Yes, the workflow is the same in principle on iOS and Android, because it uses the app’s own speed and keyframe controls. The iOS page explains the official App Store route for the app itself; this guide does not offer an iOS download.
Why does my slow motion look bad even though I followed the steps?
Usually the source footage. Slow motion needs frames. If the original clip is 30 fps and you slow it to a quarter speed, the app has to stretch 30 frames per second into a much longer duration, and the result will stutter. Use higher-frame-rate source footage for slow sections, or use a smaller slowdown.
Should I use a velocity preset instead of keyframes?
A preset can save time, but it replaces your control with someone else’s timing. If the preset’s beats do not match your song, the edit will feel off-beat. Learning keyframes first — as in this guide — means you can adjust any preset later, rather than depending on it.
Want more step-by-step editing lessons? Browse the Alight Motion Tutorials hub, or visit the Troubleshooting hub if something goes wrong.