Watch what AfterRushes made
Stock footage by Alexander Mass, used under the Pexels licence. The people in it are models, not AfterRushes customers, and they don’t endorse AfterRushes.
In short
What happened? Only 2.4 minutes of 4K stock footage, in 13 clips (0.3 GB), went into a 1:50 highlight film and a 0:30 vertical teaser. AfterRushes kept the film to the moments the footage holds rather than stretching it to the three minutes asked for, and said so. The build took 4 minutes 2 seconds on our office PC (Intel Core i7-7700, 16 GB of RAM) and the AI cost $0.39. Neither film has any sound.
The facts
| Clips | 13 video clips |
|---|---|
| Footage | 2.4 minutes · 0.3 GB |
| Source format | 3840×2160 (4K) · 30 fps |
| Highlight film | 1:50 · 1920×1080 |
| Vertical teaser | 0:30 · 1080×1920 |
| Chapters | 8 |
| Build time | 4 minutes 2 seconds · office PC, Intel Core i7-7700, 16 GB RAM |
| AI cost | $0.39 |
| Music | None recorded or supplied |
How we measured. Build time is AfterRushes’ own timer, from pressing Build (with the clips already added) to the films cut and ready to play. Adding the clips and exporting the files aren’t included. AI cost is the Claude API use AfterRushes counted for the project, at Anthropic’s list prices. Electricity, the computer and the licence aren’t in it. The films on this page are AfterRushes’ cuts as exported; any changes asked for are shown under “Changing it in plain English”.
Where each number comes from
- Clips
- AfterRushes' footage list for the project, made when the clips were added
- Footage
- AfterRushes' footage list for the project, made when the clips were added
- Source format
- The clips' own file metadata
- Highlight film
- The exported film file
- Vertical teaser
- The exported teaser file
- Chapters
- The film's edit in AfterRushes (its chapter list)
- Build time
- AfterRushes' build timer, in the screen recording of the build (8 October 2026)
- AI cost
- AfterRushes' AI cost counter, in the screen recording of the build (8 October 2026)
- Music
- The film's edit in AfterRushes (its music cues)
The brief
We asked for a three-minute landscape highlight film in the cinematic style and a 30-second vertical teaser, with the note "Short wedding film". The project was made on 8 October 2026. Music: use what was recorded on the day, if any.
What went in
The names on the film's opening title card are placeholders typed into the project.
All 13 clips were filmed in 4K (3840×2160) at 30 fps. None has sound, none was filmed upright, and the files don't record which camera filmed them. No photos went in.
Asked for vs delivered
| Item | Asked for | Delivered |
|---|---|---|
| Highlight film | 3:00 | 1:50 |
| Vertical teaser | 0:30 | 0:30 |
| Style | Cinematic | Cinematic |
| Music | From the day, if any | None recorded or supplied |
| Speeches edit | Off | Off |
How AfterRushes built the story
- 0:00Opening
Drone follows the car through open country, setting the scene
- 0:11Getting ready
Bride flings open the shutters, arms wide with joy
- 0:31First look
Bride approaches the groom under the white arch
- 0:39The bridesmaids
Genuine laughter with the bridesmaids
- 0:53The ceremony
Wide outdoor ceremony with mountains behind
- 1:14Portraits
Elegant bridal portrait through soft foreground branches
- 1:27The reception
The whole head table raises glasses together
- 1:35Together
Intimate embrace, framed by the car window
What happens when you didn’t film the whole wedding?
These 13 clips have no ring exchange and no first kiss on video, and no sound, so no vows either. AfterRushes didn't pretend otherwise: it built the day from what was there (the shutters, the first look under the arch, the bridesmaids, the ceremony, the head table, the car), kept the film at the 1:50 the footage supports, and asked for still photographs to cover the rings and the kiss. For photographers who film a few clips between photos, that's the usual case: AfterRushes makes the film from what you have and tells you what's missing.
What the AI noticed
- Story decision
Your footage holds about 1 minute 50 seconds of strong, distinct moments, so the highlight runs about 1:50 rather than the requested 3 minutes; stretching it further would mean repeating shots.
- Pacing suggestion
Set the highlight target to 2 minutes so it matches the footage available without repeating shots.
- Suggested addition
Add a few of your best still photographs to cover the ring exchange and first kiss, which have no video in the log.
- Suggested addition
Add any vows, toast or speech audio from the day so we can lay a spoken line over the opening or the kiss.
- Music suggestion
Choose a gentle, cinematic song for the highlight and a brighter, upbeat one for the teaser, since no music was recorded on the day.
The music
No music was recorded on the day and none was supplied, so the film has no soundtrack, and as the clips have no sound, it plays silent. Given a licensed track of your own, AfterRushes finds its beats and cuts the film to them.
Technical details
There is no soundtrack and no sound at all. None of the 13 clips had sound, no music was recorded on the day and none was supplied, so the highlight film and the teaser are silent as AfterRushes made them. The AI's note on music reads: "Choose a gentle, cinematic song for the highlight and a brighter, upbeat one for the teaser, since no music was recorded on the day."
When there is music to work with, AfterRushes uses the band or DJ recorded on the day if the recording is clean enough, or the photographer's own licensed track. Music for wedding films covers both.
Watch the build
Short videos from this film
Read the voiceover
“Stretching it further would mean repeating shots.” That's AfterRushes, refusing to pad a wedding film. You asked for three minutes. It found 1 minute 50 of strong moments and said so. It even noticed the ring exchange was never filmed. Try it free.
Read the voiceover
13 clips from one wedding. Four minutes later, a film. AfterRushes found the story. Getting ready, the first look, the bridesmaids, the ceremony, the dinner. Then it cut the highlight film and the vertical teaser. Camera cards in. Wedding film out.
Read the voiceover
39 cents. That's the AI bill for this wedding film. 13 clips in. The first look. The bridesmaids and the portraits out. In one minute fifty. Less than a coffee. Camera cards in. Wedding film out.
3 more short videos from this film
Read the voiceover
13 clips. Love filming weddings? Hate the timeline? AfterRushes was built for the second half. The getting ready. The ceremony. The dinner. The vintage car. A film and a vertical teaser. Without one drag handle. Shoot the wedding. Skip the timeline.
Read the voiceover
8 chapters from 13 clips. Opening. Getting ready. First look. The bridesmaids. The ceremony. Portraits. The reception. Together. AfterRushes wrote the story. Then cut the film. Camera cards in. Wedding film out.
Read the voiceover
30 seconds. That's the sneak peek. The cuffs, the first look, the bridesmaids laughing, the embrace through the car window. AfterRushes cut the vertical teaser in the same four minutes as the film. Post it tonight before the photos are even edited. Your next sneak peek? Try it free.
What it didn’t do
- It came in short, on purpose. The film runs 1:50 against the three minutes asked for. In the AI's words, "stretching it further would mean repeating shots".
- It has no sound. No clip had sound and no track was supplied, so there are no vows, speeches or music.
- Two moments are missing. The ring exchange and the first kiss were never filmed, so they aren't in the film; the AI asked for photographs to cover them.
- Its suggestions are still open. None has been applied, so the film on this page is the cut as AfterRushes made it.
- The AI makes the first cut, and the photographer reviews it and makes it theirs. Here that would mean watching it through, adding photographs of the rings and the kiss, and adding a licensed track. They can change shots on the timeline, apply a suggestion with one click or ask for changes in plain English in the Assistant, the app's chat panel. Making an AI first cut your own covers the changes worth making.
Questions about this film
How long did AfterRushes take to make this film?
The build took 4 minutes 2 seconds on our office PC (Intel Core i7-7700, 16 GB of RAM), on AfterRushes' own timer: from pressing Build, with the 13 clips already added, to both films cut and ready to play. Adding the clips and exporting the files aren't included. Build times for other footage vary with the footage and the computer.
What did the AI cost?
$0.39 for this build of 13 clips: the Claude API use AfterRushes counted, at Anthropic's list prices. The cost for other weddings varies with the footage. Your first film is free; after that, the AI is paid with credits, or with your own Claude key on the lifetime licence or Flex.
Why is the film shorter than three minutes?
Because the footage is. The 13 clips hold about 1 minute 50 seconds of strong, distinct moments, and AfterRushes doesn't repeat shots to reach a target. It said so in its notes and suggested setting the target to 2 minutes.
Was the footage uploaded anywhere?
The video files weren't. They stay on the computer AfterRushes runs on, with the edit and the finished films. Still frames from each clip go to the AI, Anthropic's Claude, to plan the film.
Can the edit be changed?
Yes. The AI makes the first cut, and the photographer reviews it on the timeline, applies suggestions with one click or asks for changes in plain English. Only the shots that changed re-render.
Is this a real couple's wedding?
No. It is stock footage filmed by Alexander Mass and published on Pexels, used to show what AfterRushes does. The couple are models who aren't AfterRushes customers and haven't endorsed it.