Use case

How to Make a Changelog Video

A changelog video turns a month of release notes into a short, watchable recap. Done regularly, it shows customers and prospects that the product is moving — and it gets small improvements the attention they deserve.

Updated 19 October 2026
Quick answerA changelog video is a 30–60 second recap of recent updates: a title card with the month or version, three to five short updates each shown on screen, and an end card linking to the full release notes. Keep the same style every time so it reads as a series. In Spotlight, reuse a saved Product Profile and style preset, upload short clips of each change and generate the recap.

Why most changelogs undersell the work

Product teams ship constantly, but changelogs are mostly text: a list of bullets nobody reads beyond the first two. Customers don’t notice the improvements they asked for, prospects can’t tell whether the product is actively developed, and the team’s work goes unseen.

A short changelog video fixes that without turning every update into a campaign. It’s quick to watch, easy to post on LinkedIn and X, and easy to embed at the top of your release notes or in a monthly email.

What a great changelog video looks like

  • Length: 30–60 seconds for three to five updates.
  • Same format every time. The same intro, style, music and end card make it recognisable as a series.
  • One beat per update. Six to ten seconds each: name it, show it, move on.
  • Biggest update first. People drop off; lead with the change most users will care about.
  • Formats: 16:9 for release notes and email; 1:1 or 4:5 for LinkedIn and X.
  • Link to details. The end card points to the full release notes.
  • Regular cadence. Monthly or per release — consistency matters more than polish.

Scene-by-scene recipe (45 seconds)

  1. Title (0–4s) — title card. “What’s new — October 2026” or the version number.
  2. Update 1 (4–14s) — UI demo. The headline change, with a cursor path and a “New” badge.
  3. Update 2 (14–22s) — video clip. A second notable change.
  4. Update 3 (22–30s) — screenshot with highlight. A smaller improvement, ringed or underlined.
  5. Quick wins (30–39s) — feature grid. Three or four small fixes and improvements, one line each.
  6. End card (39–45s). “Full release notes at [URL]” — same end card every month.

This follows our feature release template. For a single big feature, make a dedicated feature announcement video instead.

How to make it in Spotlight

  1. Pick your saved Product Profile from the selector.
  2. Record a short clip of each update and upload them, along with any screenshots.
  3. Apply your saved style preset so this month matches last month.
  4. Generate the first cut, then instruct: “title it October 2026; lead with the new reporting; keep each update under 10 seconds”.
  5. Check narration and captions, then export 16:9 and a 1:1 cut for social.

Version history lets you look back at previous months’ projects, and only changed scenes re-render, so re-exports are fast. The Creator plan’s 3 HD videos a month suit a monthly changelog plus a couple of feature announcements; Studio includes 12. See pricing.

A repeatable monthly workflow

The hard part of a changelog video is not making it — it’s making it every month. Build the habit into how you ship:

  1. Record as you ship. When a change goes live, the person who built it records a 10–20 second clip and drops it in a shared folder. No editing needed.
  2. Keep a running list of user-facing changes with one plain-language line each.
  3. Pick a fixed day — say, the last Thursday of the month — to assemble the video.
  4. Choose the top three to five changes, upload their clips to Spotlight and generate the recap from your template.
  5. Publish everywhere at once: release notes, email, in-app and social.

With the clips ready, assembling and exporting a monthly recap becomes a short task rather than a project.

Writing updates users care about

Describe each change by what users can now do, not by what the team did. “Search now finds results inside attachments” beats “Improved search indexing”. Where you can, credit the users who asked for it — “You asked, we built it” makes customers feel heard and encourages more feedback. Keep the narration for each update to one or two sentences, and let the on-screen demo do the rest.

Mistakes to avoid

  • Too many updates. Five is plenty; link to the rest.
  • Changing style every month. Save a preset and reuse it.
  • Internal language. “Refactored the sync worker” means nothing to users; “Sync is now faster on large workspaces” does.
  • Skipping months. An irregular series signals the opposite of momentum.
  • Text-only beats. Each update should show something on screen.

Scene-by-scene plan

16:9 · about 45s · Brand style

  1. Title — “What’s new — October 2026”
    Same intro every month.
  2. UI demo — “New: custom dashboards”
    Headline update with a “New” badge.
  3. Video clip — “Faster search”
    Second notable change.
  4. Screenshot — “Bulk edit for tags”
    Smaller improvement, highlighted.
  5. Feature grid — “Plus: dark mode fixes, CSV export, new shortcuts”
    Quick wins, one line each.
  6. End card — “Full release notes at [URL]”
    Same end card every month.

Make this video free

Put your product centre stage

Your launch deserves better than a screen recording.

Paste your website. See your first cut in minutes. Free to try — no card.

Questions, answered

What is a changelog video?

A short video recap of recent product updates, usually monthly or per release, that shows each change on screen.

How long should a changelog video be?

30–60 seconds for three to five updates.

How often should I make a changelog video?

Monthly or per major release works for most teams. A regular cadence matters more than length.

How do I keep changelog videos consistent?

Reuse the same Product Profile, style preset, template and end card each time.

Where should I post a changelog video?

At the top of your release notes, in your product update email, in-app, and on LinkedIn and X.

Keep reading