# Changelog video
URL: https://remocn.dev/docs/guides/changelog-video

A ~25-second release update for the weeks that ship several small things — same open, same pace, every release

Not every release deserves a launch. Most weeks ship three or four small improvements — a fix, a speedup, a new option — and that's exactly what this video carries. About twenty-five seconds, no big reveal, posted on a rhythm: weekly, monthly, every release. It's the lightweight sibling of the [Feature announcement](/docs/guides/feature-announcement) — when one change deserves the spotlight, use that recipe; when the week shipped several small things, use this one.

## The storyboard

1. **The stamp** — Your product name and the date or version land together, like a postmark. This is the recurring open viewers learn to recognize.
2. **Item one** — The change's name and one line on what it does.
3. **Item two** — Same shape, next change.
4. **Item three** — Same shape again. If a change is visual, show it instead of describing it.
5. **The nudge** — One line pointing to the full changelog.
6. **The lockup** — Your logo, one short closing line.

The value of this video isn't any single edition — it's the rhythm. Same open, same pace, every release. By the third one, viewers recognize your update in the feed before they read a word. So resist redesigning it each time; change the items, keep the frame.

## Your words

- **Product name**
- **Version or date** — Whatever you stamp releases with
- **Three or four changes** — Each a name plus a one-line payoff, six words or fewer
- **Changelog URL**
- **Closing line** — e.g. "Shipping weekly"

Struggling with the payoff lines? [Words on screen](/docs/guides/words-on-screen) is the cheat sheet.

## The prompt

Paste it into your agent with your words in place of the highlighted blanks.

```text
I'm making a changelog video with remocn (remocn.dev).

Build a ~25-second, 1920×1080, 30fps release update for <PRODUCT NAME> in
this Remotion project, using remocn components — install anything you need
with `npx shadcn add @remocn/<name>`:

1. Stamp — "<PRODUCT NAME>" with "<VERSION OR DATE>" beneath it, landing
   together like a postmark. Short and confident — this open repeats every
   release, so keep it simple enough to reuse.
2. Items — one beat per change, every beat built the same way: the change
   name lands first, its payoff line follows beneath it:
   - "<CHANGE 1>" — "<PAYOFF 1>"
   - "<CHANGE 2>" — "<PAYOFF 2>"
   - "<CHANGE 3>" — "<PAYOFF 3>"
   If a change is visual, replace its text beat with a small fake app
   screen showing it happen.
3. Nudge — one calm line: "Full changelog at <CHANGELOG URL>".
4. Lockup — my logo (<LOGO FILE, or: use the product name as a wordmark>)
   with a closing line: "<CLOSING LINE>".

Style: warm dark background (#141318), off-white text, one accent color
<ACCENT COLOR>, Manrope. One quiet shader-simplex-noise field behind the
whole video. Keep motion restrained and identical across the item beats —
this is a stamp, not a show. Use my copy exactly as written.
```

## Directing the result

- "Item two runs long — tighten it."
- "Hold the stamp a beat longer."
- "Change three is visual — show the screen instead of the words."
- "The items feel different from each other — make the motion identical."

More directing vocabulary: [Directing your agent](/docs/guides/directing-your-agent).

Next release, don't start over — ask your agent to reuse this video and swap the version and the items.

## Get the file

You'll get an `.mp4` in the project folder, ready to post.