# Turn a screen recording into a demo video.

> Turn your screen recording into a demo video: cut the dead time, speed up the waits, add titles and captions. A coding agent writes the edit.

Canonical: https://vawe.dev/screen-recording-to-demo-video
Last updated: 2026-11-09

A screen recording is footage. In vawe a coding agent trims the dead time, speeds up the waits, adds a title card and captions, and renders the result as an MP4. Your recording is shown as you made it: vawe does not redraw your app.

## How the edit runs.

1. **Hand over the recording. **`bin/vawe new demo --footage ~/Movies/demo.mov` copies it into the film’s folder.
2. **Log it. **`footage.md` lists the length, the shot changes, the loudness, a contact sheet of 8 frames and, if you talk over it, a transcript, with every word timed in a words file beside it.
3. **Plan the cut. **The agent fills a Cut list: one row per part with the in and out seconds, the speed and the reason.
4. **Write the page and render. **`bin/vawe dev` renders a half-size draft with sound. The final render waits for your OK.

A silent screen recording has no words to cut on, so the agent reads the contact sheet and asks you for the seconds it cannot see. vawe has no detector for an idle screen.

Ask in plain words:

```
Edit the screen recording in ~/Movies/demo.mov
into a 30-second demo.
Cut the dead time, speed up the waits,
add a title card and captions.
```

Source: prompts/edit-from-clips.md · harness/media/footage.mjs

## Cut the dead time, speed up the waits.

Each part of the recording is a `<video>` in its own beat. `data-trim` and `data-trim-end` keep one stretch, and `data-rate` sets its speed. The example plays source seconds 12 to 32 at 4 times speed, so a 20-second upload takes 5 seconds of film.

The engine seeks the clip to an exact second on every frame. It never plays it live, so the same page gives the same frames on every render.

A wait, sped up 4 times:

```
<section data-world="upload">
  <video src="footage/demo.mp4" data-at="0"
         data-trim="12" data-trim-end="32"
         data-rate="4" muted></video>
</section>
```

Source: skills/vawe-page/SKILL.md, Video clips

## Titles, captions and a push.

1. **Titles. **A title card at the start and lower thirds that name a step.
2. **Captions. **Word-timed captions from your narration, for a viewer who watches muted.
3. **A push. **The camera-moves component pushes the whole clip toward a point the agent chooses. vawe does not follow your cursor and does not find the part of the screen that matters.

Music only comes from a file you give. Without one, the clip keeps its own sound.

Source: prompts/moves/README.md, Scope

## How this differs from a launch or showcase video.

A [launch video](https://vawe.dev/launch-video) and a [product showcase video](https://vawe.dev/product-showcase-video) are built from captured UI that vawe animates. Here your recording is the picture. The agent trims it, times it and frames it, and it stays your pixels.

## The video components this edit uses.

A name on screen, captions for a muted viewer, a push on the whole clip and a soft change between parts.

- [lower-third](https://vawe.dev/video-components/lower-third)
- [caption-karaoke](https://vawe.dev/video-components/caption-karaoke)
- [camera-moves](https://vawe.dev/video-components/camera-moves)
- [luma-matte-dissolve](https://vawe.dev/video-components/luma-matte-dissolve)

## More on editing with an agent.

1. [Edit video with Claude Code](https://vawe.dev/edit-video-with-claude-code): the steps in Claude Code, Codex or Cursor, and the questions the agent asks first.
2. [Agentic video editing](https://vawe.dev/agentic-video-editing): how an agent reads footage it cannot watch, and what an edit can and cannot do.
3. [Edit video with code](https://vawe.dev/programmatic-video-editing): ffmpeg, MoviePy, Editly, Remotion and vawe compared, with sources.
4. [vawe vs video-use](https://vawe.dev/vs/video-use): another open-source way to edit clips with a coding agent, and when it is the better choice.
5. [vawe vs OpenEdit](https://vawe.dev/vs/openedit): an open-source pipeline from VEED that also lets an agent edit clips, and how it differs.
6. [How an agent reads footage it cannot watch](https://vawe.dev/blog/how-an-agent-reads-footage): what footage.md holds and why the agent cuts on a word end.
7. [Cut the silences with an agent](https://vawe.dev/blog/cut-silences-with-an-agent): trim the pauses and keep every word whole.
8. [Captions on a video, in HTML](https://vawe.dev/blog/animated-captions-html): word-timed captions, the part of an edit a muted viewer reads.
9. [Aspect ratios without cropping](https://vawe.dev/blog/html-video-aspect-ratios): one edit at 16:9, 9:16, 1:1 or 4:5.

## Start from your recording.

`bin/vawe new <name> --footage <file>` logs it and starts the page.

## Related

- [Get vawe on GitHub](https://github.com/vawe-hq/vawe)
- [Edit video with Claude Code](https://vawe.dev/edit-video-with-claude-code)
- [Product showcase videos](https://vawe.dev/product-showcase-video)
- [Launch videos](https://vawe.dev/launch-video)
- [Every video component, with its clip](https://vawe.dev/video-components)
