← All articles
Guide4 min read

How to make an event recap video from a day of footage

Eighteen minutes of festival footage became a 20-second recap: twenty cuts, one look, cut to the drum build. How to get the same from your own event.

An event recap has one job: make the people who were there feel it again, and make the people who were not wish they had been. It has about twenty seconds to do it, and the footage it is cut from is usually an hour of phone video with no plan.

Below is a recap cut in Narrative from a festival vlog, and how to get the same from your own event, whether it is a festival, a conference, a launch or a wedding. You can open it on its timeline without an account.

Eighteen minutes to twenty seconds

The source is one file: an 18-minute, 1080p vlog of a day at a music festival, the kind of thing a phone produces when you point it at everything. The recap is 20 seconds. On the timeline it is twenty cuts, and their names are the shot list: night lights, crowd to camera, the blue payoff, the stage screen in daylight, then a strobe run of a friend, the dancing, the DJ, the fans, the tent, a totem, the sunset, the night. Every one of those was found in the 18 minutes and put in an order that builds.

It has one look, applied to everything: an analog lens with tape grain and a handycam on-screen display, so twenty phone shots from different hours of the day read as one piece. It has one track, and the cuts tighten with it into a black-shutter hit on the drum build. That is the whole recipe: one thread, one look, one track.

The recap. Twenty cuts in twenty seconds, one look, cut to the build. Sound on.

What to upload

  • Everything usable from the day. Recaps are built from moments, and the moment is often in the clip you would not have picked. The editor reads all of it; you do not have to.
  • Separately recorded audio, if any. A line from the stage, a toast, a cheer. It goes in the same project.
  • The music. The cuts are timed to the track, so the track has to be in the project before you ask. Make sure you have the right to use it where you are posting.

How to ask for it

Length, thread, look, rhythm. In that order if it helps.

Make a 20-second recap of the day. Open on the night lights, build to the main stage. One look across everything: analog, grainy, handycam. Cut to the beat, tighten on the build, black on the last hit.

Two things make the difference between a recap and a slideshow. The first is the thread: “the day, dawn to the headliner” or “the moment the doors opened” gives the cuts an order. The second is the look. Phone footage from one day varies wildly in colour and light; a single treatment across all of it is what makes it read as one film. Ask for it in words (“warm, grainy, a little soft”) or open the colour panel and set it by hand.

Reviewing a recap

Watch it once at full speed, then ask three questions. Does it build? A recap that peaks at 0:04 has nowhere to go. Is the best shot the payoff? If the biggest moment is buried at 0:09, say “make the confetti the last shot.” Is anyone in it who should not be? Twenty seconds of an event is twenty seconds of faces; check them.

Then revise by naming the moment. “Hold the crowd shot longer.” “Lose the tent, it’s the weakest.” “Start on the daylight and end on the night.” Each revision is a version, and if one goes wrong you step back to the one before.

The same recipe, other events

A conference recap is the same edit with a different look: cleaner, slower, the speakers’ faces held longer, captions for the one quotable line. A launch recap wants the product as the payoff. A wedding wants the ceremony audio under the cut. The structure does not change: one thread, one look, one track, the best shot last.

See it on a real timeline

Open the recap. Scrub the last five seconds and watch the blocks shorten into the drum build; that is the beat sync as blocks on a strip. Then ask for one change, “end on the sunset instead of the night” is a good first one, and see what moves. The first three prompts are free; the editor runs on desktop today.