Blog

How to make a feature announcement video for every release

An app window with a starburst badge, megaphone, envelope with a video and a bell
One feature, one short clip, next to the written note. Every release.

A feature announcement video is a 30 to 90 second screen recording of one new feature, posted next to the written release note. Not instead of it. The text is what people search for later; the video is what makes them notice the feature today. Here's how to make one quickly enough to do it every release, and where each version goes, including email, where video mostly doesn't play.

Video next to the changelog, not instead of it

Big product teams already do this. Windows, for one, publishes video release notes every month. You don't need their budget to copy the format.

The split that works: the written note is the reference. It's searchable, skimmable, and it lists the details and the edge cases. The video is for discovery: someone sees the feature working in 40 seconds and goes to try it. Drop either one and you lose half the job.

One change per video, 30 to 90 seconds

A release with six changes gets six short clips, not one six-minute tour. Short clips are easier to watch, easier to drop into a help article, and you can re-record one when the UI changes without redoing the rest.

The release note you already wrote is your script. Turn it into four beats:

  1. The old pain, in one sentence. "Exporting a report used to take four clicks and a download folder."
  2. The new way, shown, not described. The feature doing its thing on screen.
  3. Where to find it. The menu, the button, the shortcut. This is the part people rewatch.
  4. The nudge. "It's live for everyone now. Try it on your next report."

Where each version goes

ChannelFormatNote
Changelog page or in-app widgetEmbedded video, 16:9Right above the written note
EmailGIF or a still with a play button, linking to the videoMost inboxes won't play video
X and LinkedInSquare or 4:5, captions burned inPlays muted in the feed
Help centerThe same clip, or a longer walkthroughLives longest. Keep it current.
Customers who asked for itA direct link from sales or supportThe highest-converting send you'll make

That last row is easy to forget. If twelve customers asked for the feature, send each of them the clip with one line: "You asked, it's live." That message does more for retention than the public announcement.

Email: video mostly won't play

Gmail strips video tags out of emails, and support elsewhere is patchy (Email on Acid's guide covers the details). The standard fallback is a short GIF, or a still frame with a play button, that links to the full video on your changelog page.

Both are quick with ffmpeg (brew install ffmpeg). I tested these. A 4-second GIF at 600 pixels wide, the usual email width, came out at about 640 KB:

ffmpeg -i feature.mp4 -t 4 -vf "fps=12,scale=600:-1:flags=lanczos,split[a][b];[a]palettegen=max_colors=96[p];[b][p]paletteuse=dither=bayer" \
  -loop 0 feature-email.gif

Or grab a single frame, 3 seconds in, to use as a thumbnail:

ffmpeg -ss 3 -i feature.mp4 -frames:v 1 -update 1 feature-thumb.png

Recording it fast enough to do every release

The real risk with release videos isn't quality. It's the team quietly stopping after three releases because each one took an afternoon. Set it up so one clip takes about 15 minutes:

  • Keep a demo workspace with realistic data and every feature flag on. Never record in production with real customer names.
  • Use the same window size and zoom every time, so clips from different releases sit together on the changelog without jumping around.
  • Save your recording setup (background, frame, cursor, webcam position) instead of rebuilding it each release.
  • Record before release day. Get it done on staging while the feature is fresh, not in the scramble after launch.
  • Accept "good enough." A clear 45-second clip every release beats a polished one every quarter.

If several PMs make these, agree on one short checklist: window size, demo workspace, four beats, length limit. Consistency comes from the checklist, not from one person doing all of them.

The tools, honestly

Loom is the usual pick for this and fine for internal updates. For customer-facing release videos, you want the click to be visible and the result to look like it came from the same team every time.

I make CursorFlow, a Mac screen recorder. For release videos:

  • Automatic zoom on clicks puts the new button front and centre, and you can adjust it on the timeline.
  • Presets save the whole look, so every release clip matches without anyone remembering settings.
  • 16:9, square, 4:5 and 9:16 from the same recording: switch the canvas and export again.
  • On-device captions for the muted feed versions, and an .srt for your video host.
  • Local-first. Recordings of unreleased features stay on your Mac until you choose to publish. More on that in the case for local-first recording.

It's free to use, with a watermark on exports until you buy the one-time licence.

Frequently asked questions

How long should a feature announcement video be?
30 to 90 seconds, covering one change. A release with six changes gets six short clips rather than one long tour.
Can I embed a video in a product update email?
Not reliably. Gmail strips video from emails and support elsewhere is patchy. Use a short GIF or a still frame with a play button that links to the video.
Should a video replace written release notes?
No. The written note is the searchable reference; the video helps people notice the feature. Post them together.
What should a feature announcement video show?
The old pain in one sentence, the new feature working on screen, exactly where to find it, and a nudge to try it.
How do we keep release videos consistent across a team?
Agree on a short checklist: demo workspace, window size, four-beat script, length limit. Save the recorder's visual settings so every clip looks the same.