Blog/Craft
Release and changelog videos people watch
Ninety seconds: what changed, who it affects and how to try it. Put the change first and link the notes.
Kevin Blanco··5 min read·Retention
The short answer
A release video tells existing users what changed, who it affects and how to try it, in about ninety seconds. Open with the change, show it working, say what to do next and link the full notes. Pair every significant release with one, and measure views from the release email and tickets on the topic.
01
Why a video for a release
Release notes get skimmed. A short video gets watched by the people who care about the change, because it shows what it does and how to use it.
The audience is existing users. They know the product, so the video can skip every introduction and go straight to the change.
02
Ninety seconds, in beats
The beat sheet
Plan the release video
Change the beats and the seconds for your release.
- 0:00s
- 0:15s
- 0:30s
- 1:05s
- 1:20s
1:30 of 2:00
The proof starts at 0:30
It fits. Check that every beat earns its seconds.
03
From changelog line to script
The changelog line
"Added support for batch endpoints. See the docs for details."
The release video's opening
"If you send events one at a time, you can now send up to a hundred in one call. Here's how it looks."
04
Breaking changes
When something will break, say so first. Say what, when, and the exact lines to change. Show the before and the after.
Put the same warning, with the date, in the release email and at the top of the notes.
05
What to measure
Views
From email
Existing users are the easiest audience to reach. Link the video in the release email.
Tickets
On the topic
Compare the weeks before and after on the topic the video covers.
Adoption
Of the feature
Whether the people who watched start using the new thing.
FAQ
Questions people ask
How long should a release video be?
About ninety seconds: what changed, who it affects, how to try it, and where to read more. Link the full notes for detail.
Which releases deserve a video?
Those that change how people use the product: new features, breaking changes and migrations. Small fixes can stay in the notes.
Who is a release video for?
Existing users. They know the product, so the video skips introductions and starts with the change.
How do I handle breaking changes in a release video?
Say what will break and when, show the before and after, and give the exact lines to change. Put it first.
How do I measure a release video?
Views from the release email, tickets on the topic in the weeks after, and adoption of the feature among those who watched.
DevReel
How we do it at DevReel
We make release videos short, put the change first and link the notes. For major releases we also add a migration video, so the people affected know exactly what to do.
Cloudinary's videos usually average around 400 views. Ours passed 9,000 in the first week. For ngrok, watch hours tripled and subscribers went from about 450 to over 800 in the first week.
Cloudinary views
9,000+
in the first week, against a usual ~400
ngrok watch hours
3×
subscribers from ~450 to 800+ in the first week
Now the hard part
Tell us about your next release and we'll plan the ninety seconds.

Kevin Blanco founded DevReel. He has made 500+ developer-tool videos and spoken at 80+ developer conferences.
Keep reading
Craft/Evaluation
A product demo developers watch to the end
Build it around one outcome, show the real product, keep one honest limit, and plan it in beats so the proof arrives early.
November 16, 2026·6 min read→Craft/Activation
Tutorial videos developers finish
Set the screen up for the viewer, keep the real error, and give every tutorial chapters and a link to the code.
November 16, 2026·6 min read→Craft/Activation
Docs videos: when video beats a page
Text wins for reference and commands. Video wins for setup flows, debugging and anything visual. How to tell, and how to embed it.
November 16, 2026·5 min read→