Make a World Cup Group-Stage Recap Video in 30 Minutes

Why Recap a Group-Stage Matchday?

The World Cup 2026 group stage is the biggest ever staged: 48 teams in twelve groups, A through L, playing across the USA, Canada and Mexico from June 11, 2026. The tournament packs in 104 matches before the final on July 19 at MetLife Stadium in New Jersey, and on busy days the fixtures stack on top of each other — Mexico vs South Korea in Group A, Canada vs Switzerland in Group B, Brazil vs Morocco in Group C, USA vs Türkiye in Group D. Nobody sees everything live.

That is exactly the gap a recap video fills. A 60–90 second cut of the day's goals, saves and turning points is the clip your group chat actually watches, the post that travels on Reels and TikTok, and the fastest way to catch a friend up before the next kickoff. And because group matchdays come thick and fast, speed matters more than polish: a recap published three hours after the final whistle beats a perfect one published two days later.

This guide is a 30-minute, time-boxed workflow — five blocks, each with a clear job and a free browser tool. Nothing uploads, nothing gets watermarked, and there is no account to create; everything runs locally on your own device. The full toolkit lives on the World Cup tools hub if you want one tab with everything.

What You'll Need

• Recordings of the matches you want to cover — screen recordings of broadcasts you have the right to use, or your own footage.
• A rough list of the day's key moments and scorelines (the final score alone tells you most of what to hunt for).
• A timer. The 30 minutes only works if you actually box the time.

Pro tip: Decide the shape before you start the clock: how many matches, which moments, vertical or horizontal first. A recap of two matches with four moments each is far better than a recap of five matches you never finish.

The 30-Minute Plan

Print it, screenshot it, or keep it in a corner of the screen. Each block below explains how to stay inside its box.

Minutes 0–5: Collect and Shortlist

Move every recording into one folder, then write the shortlist: for each match, pick 3–5 moments. The reliable formula is every goal, the best save, and one turning point (a red card, a missed penalty, a post). For a two-match day — say Spain vs Uruguay in Group H and Argentina vs Austria in Group J — that is 6–10 moments total, which is exactly the budget a 90-second recap can afford.

Write a rough timestamp next to each moment ("goal ~ 23:40"). Those five minutes of notes are what make the next ten minutes fast.

Minutes 5–15: Trim the Key Moments

Open the first recording in the Video Trimmer and cut each shortlisted moment to its own clip:

1. Start each clip about 1 second before the action — the cross, the through ball, the wind-up.
2. End it 1–2 seconds after the payoff, just as the celebration peaks.
3. Keep clips between 4 and 8 seconds. Goals earn 6–8; saves and near-misses work at 4–5.
4. Name files so they sort: h-esp-uru-goal1, h-esp-uru-save, j-arg-aut-goal1, and so on.

Budget roughly 45–60 seconds of work per clip. Ten clips fits the ten-minute box with room to spare — but if you fall behind, cut moments, not corners. Eight tight clips beat twelve sloppy ones.

Minutes 15–20: Merge Into One Timeline

Load all the clips into the Video Merger in your chosen order. Two orders work:

• Chronological — the day as it happened. Best when matches overlapped in drama.
• Match by match — all of Group H, then all of Group J. Best for clarity, and the structure the scoreboard step needs anyway.

Check the preview top to tail once — five seconds of checking saves a re-export — then merge to a single file. Since all the clips come from broadcast recordings at the same resolution and frame rate, the merge is instant and clean; if one clip came from your phone, resize it to match before merging.

Minutes 20–25: Scoreboard and Captions

Two overlays turn raw clips into something that reads like a broadcast package:

1. Scoreboard: run the merged file through the Video Scoreboard and set the team abbreviations and score for each segment — ESP–URU while Group H plays, ARG–AUT after the switch. A score on screen means a viewer who joins mid-clip still knows the stakes.
2. Captions: most feeds play muted, so burn the context in with the Subtitle Burner. One short line per moment is enough: "Group H — opening goal, 23'" or "Group J — the equalizer." Keep lines under 42 characters and inside the central safe area.

Burned-in captions cannot be turned off by the platform, which is the point: your recap stays understandable with the sound off, where most of its views will happen.

Minutes 25–30: Go Vertical and Compress

Broadcast footage is 16:9; the platforms that reward recaps are 9:16. Two ways to convert:

• Crop: the Video Crop tool cuts a 1080×1920 window out of the frame. Keep the ball and the goal inside the crop — that usually means following the center of the action, not the center of the frame.
• Resize with padding: if cropping loses too much context (long balls, counter-attacks), the Video Resizer fits the full 16:9 image into a vertical canvas with bars, keeping every player visible.

Then compress. The Video Compressor at CRF 23 typically cuts the file to half or a third with no visible loss — a 90-second 1080p recap lands well under 50 MB, small enough to post anywhere and send in any chat.

Bonus: Tease the Next Matchday

End the recap with a hook. The Score Predictor generates win probabilities and most-likely scorelines for any World Cup 2026 fixture — pick the next big group game, say Netherlands vs Japan in Group F or England vs Croatia in Group L, and hold the prediction card on screen for the final 2–3 seconds with a caption like "The model says 2–1. Agree?" It turns a recap into a conversation starter and gives the next video a ready-made opening.

Export Specs by Platform

Export the vertical version first — it is the one with a deadline. The horizontal YouTube cut can wait until the evening.

Putting It Together

Shortlist in five minutes, trim ten clips in ten, merge in five, overlay scoreboard and captions in five, crop and compress in the last five. For a matchday with Brazil vs Morocco and USA vs Türkiye, that is a 75–90 second vertical recap — every goal, the best save, one turning point per match, scores always on screen — published while the post-match interviews are still running.

The entire pipeline is free and local: no upload, no watermark, no signup, from the first trim to the final compress. Run it once at half speed to learn the boxes; by the second or third matchday of this 104-match group stage, 30 minutes will feel generous.

FAQ

Q: Can a beginner really finish a recap in 30 minutes? A: Yes, if you respect the boxes. The first run usually takes 40–45 minutes because trimming is new; by the second matchday you will beat the clock. The two biggest time-savers are shortlisting moments before touching an editor and capping yourself at 3–5 moments per match.

Q: How many moments per match should I include? A: Three to five: every goal, the best save, and one turning point. At 4–8 seconds per clip, two matches fill 60–90 seconds perfectly. If the day had three or four matches, drop to 2–3 moments each or split the recap into two videos rather than rushing past 90 seconds.

Q: Should I edit horizontal or vertical first? A: Edit in the original 16:9 — trimming, merging and overlays are all easier with the full frame — then convert at the end with Video Crop for a tight 9:16 or the Video Resizer if you need the whole pitch visible. Converting last means one decision instead of ten.

Q: Do these tools upload my footage or add a watermark? A: No. The trimmer, merger, scoreboard, subtitle and compression tools all run locally in your browser via WebAssembly. Your recordings never leave your device, no account is required, and exports are watermark-free.

Q: What if I missed one of the day's matches entirely? A: Cover what you have and bridge the gap with a scoreline caption ("Group A: Mexico vs South Korea — see thread"). Then lean on the Score Predictor tease for the next fixture so the recap still ends forward-looking instead of incomplete.