Slow-Motion Replays: Editing Dramatic World Cup Moments
Make smooth slow-motion replays of World Cup 2026 goals in your browser. Learn slow-mo factors, frame rate, fps conversion, and clean lead-ins.
Why Slow Motion Owns the Replay
The FIFA World Cup 2026 runs June 11 to July 19, with 104 matches spread across the USA, Canada and Mexico. Every tournament produces a handful of moments worth watching again: a curling free kick, a last-ditch tackle, a goalkeeper getting fingertips to the ball. Broadcasters reach for slow motion because it stretches a half-second of action into something you can actually feel β the spin on the ball, the defender's weight shift, the exact frame the ball crosses the line.
You do not need a TV studio to do this. If you have a clip of the moment β a screen recording, a phone video off the TV, or a downloaded highlight β you can build a clean slow-motion replay entirely in your browser. No software install, no upload, no watermark. Everything below runs on FFmpeg compiled to WebAssembly, which means your footage never leaves your device.
This guide walks through the full workflow: picking a slow-mo factor, understanding why source frame rate matters, when to convert fps for smoothness, isolating the replay clip, and pairing it with a normal-speed lead-in so the edit feels like a real broadcast.
What You'll Need
- A source clip of the moment you want to replay. Even 5β10 seconds is plenty.
- The clip's frame rate (fps). Most phone and broadcast footage is 25, 30, 50 or 60 fps. If you are not sure, you will see it once you load the file.
- A browser. That is it β the Video Speed Changer does the slowdown, and a couple of supporting tools handle trimming and frame rate.
A quick word on frame rate, because it is the single thing that makes or breaks a replay. When you slow a clip down, you are spreading the same number of frames over more time. A 30 fps clip slowed to 50% only shows 15 unique frames per second β and that is where stutter creeps in. The higher your source frame rate, the more real frames you have to work with, and the smoother the slow motion looks.
Step 1: Trim Down to the Moment
Start by isolating just the action. A replay should be tight β the run-up to the shot, the strike, and the ball settling in the net. Anything before or after dilutes the drama.
Open the Video Trimmer, drop in your clip, and set the in and out points around the moment. Aim for 3β6 seconds of source footage. Remember that slowing it down will multiply the runtime: a 4-second clip at 50% speed becomes 8 seconds on screen, which is already a long replay by broadcast standards.
Trim before you slow down, not after. Working with the shortest possible clip keeps every later step fast and keeps your final file small.
Pro tip: Leave about half a second of "air" before the key action β the moment a striker plants their foot, or the keeper begins to dive. That breath gives the viewer time to lock onto the subject before everything goes slow, which makes the payoff land harder.
Step 2: Choose Your Slow-Mo Factor
The slow-mo factor is just the playback speed. Lower percentage means slower motion. There is no single correct value β it depends on how fast the original action was and how much detail you want to reveal.
- 75% (1.33x slower) β A subtle slowdown. Good for showing a passing sequence or build-up play without it feeling artificial.
- 50% (2x slower) β The classic replay speed. Perfect for goals, saves, and tackles. Most broadcast replays live around here.
- 25% (4x slower) β Dramatic, almost frozen. Use this for the single most important frame: the ball kissing the post, the offside-line moment, the celebration roar.
Open the Video Speed Changer, load your trimmed clip, and try 50% first. Preview it. If the action still flies by, drop to 25%. If it drags, push back up toward 75%. The tool changes speed instantly so you can experiment without committing.
A useful rule: the faster the real-world action, the slower you can go without it feeling sluggish. A 100 km/h free kick can survive 25% playback. A slow midfield build-up will feel like it is wading through mud at the same setting.
Step 3: Convert Frame Rate for Smoothness (When Needed)
This is the step most people skip, and it is the difference between buttery slow motion and a stuttery slideshow.
If your source is 30 fps and you slow it to 25%, you end up showing only 7β8 unique frames per second. Your eye notices every one. The fix is to give the clip a higher frame rate before or after slowing, so playback has enough frames to feel continuous.
Open the Video FPS Converter and bump your clip up to 60 fps. Modern frame-rate conversion interpolates intermediate frames, generating new in-between images so the slow motion glides instead of jerking. The result will not match true 240 fps phone footage, but for a 50% or even 25% replay it is a dramatic improvement.
The order that works best:
- Trim the clip.
- Convert to 60 fps.
- Then apply the slowdown.
If your original footage was already shot at 50 or 60 fps β many modern phones and broadcast feeds are β you can often skip this step entirely. High source frame rate is the best smoothness insurance there is, which is why sports cameras shoot at 120 or 240 fps in the first place.
Step 4: Combine a Normal-Speed Lead-In
A replay that is slow from the very first frame feels disconnected. Real broadcasts show the moment at full speed first, then cut to the slow version β sometimes from a second angle. You can fake that rhythm with two clips.
- Keep one copy of your trimmed clip at normal (100%) speed β this is your lead-in.
- Make a second copy and run it through the Video Speed Changer at your chosen factor.
- Join them so the full-speed version plays first, immediately followed by the slow replay.
This full-speed-then-slow structure is exactly how you would see a goal presented on screen during the tournament: HOM 2 β 1 AWY at real speed, then the slow-motion breakdown of how it happened. The contrast between the two speeds is what makes the slow version feel cinematic rather than just sluggish.
For an even more broadcast feel, add a short freeze on the single decisive frame at the end β the instant the ball crosses the line. You can approximate this by setting a very low speed (10β15%) on just the last fraction of a second.
Step 5: Export and Check
Once your replay is built, export and watch it back at full size, not just in the preview window. Stutter is much easier to spot on a big screen.
Run through this checklist:
- Does the action read clearly, or did you slow it so far that motion blur smears it?
- Is the lead-in long enough to orient the viewer before the slowdown hits?
- Does the file size make sense for where you are sharing it? If it is heavy, a quick pass through a compressor can shrink it without a visible quality drop.
Because the whole pipeline runs in your browser, you can re-trim, re-slow, and re-export as many times as you like with no upload waits and nothing stored on a server.
FAQ
What's the best slow-motion speed for a goal replay?
Start at 50% (2x slower) β it is the broadcast standard and works for almost every goal, save, or tackle. Drop to 25% only for the single most dramatic instant, like the ball crossing the line. Going much slower than 25% on 30 fps footage usually looks choppy unless you first raise the frame rate.
Why does my slow motion look choppy or stuttery?
Because there are not enough real frames to fill the extra time. A 30 fps clip slowed to 25% shows only about 7 frames per second. Convert the clip to 60 fps with the Video FPS Converter before slowing it down, or start from higher-fps source footage (50/60 fps phones and broadcast feeds). More frames equals smoother motion.
Do I need to upload my World Cup clip to a website?
No. Every tool here β the Video Speed Changer, Video Trimmer, and Video FPS Converter β runs entirely in your browser using FFmpeg WebAssembly. Your footage stays on your own device, there is no signup, and the result has no watermark. It works the same on desktop and mobile.
Try it yourself β free in your browser
No upload, no signup, no watermark β these tools run on FFmpeg WebAssembly locally.