Free tool · no signup
Release notes to video script
Paste your release notes, pick up to three changes, and get a short feature-video script with timings and word counts.
Your release notes
Pick up to three to feature
Customer-facing changes make the best scenes. Items marked "internal" sound like fixes behind the scenes.
Your draft
A feature release video shows one to three changes, each as a short scene, with a hook up front and one call to action at the end. Pick the changes customers will notice, and leave out internal ones.
Most teams already write release notes. Turning them into a short video usually stalls, because release notes are written for the team: they list everything, in the team's words, with ticket numbers. A viewer wants one to three changes, in their own words, shown on the real screen.
This tool takes your pasted release notes, tidies them (it removes issue and pull request numbers), and lets you choose up to three changes to feature. It then builds a script: a hook, one scene for each change, and a call to action, with timings and a word count for each. It rearranges your words only, adds nothing of its own, and runs in your browser, so nothing you paste is sent to us.
Which changes to feature
Pick the changes a customer would notice and care about. A good feature scene answers "what can I do now that I could not before?" Changes that fix a bug, speed something up a little, or tidy something internal rarely make a good scene. You can mention them in text or in the changelog instead.
- One change is enough. A 15 second film with one clear change beats a list of five.
- Two or three at most. Beyond that, each change gets too little time to be seen.
- Lead with the best one. The hook is built from the first change you pick, so choose the strongest first.
How the script is built
| Scene | What it does |
|---|---|
| Hook | "New in your product", and the benefit of the first change |
| One scene per change | The change in one sentence, shown on the real screen |
| Call to action | One next step and the address |
Time is shared between the scenes, and each scene gets a word budget at a calm pace of about 2.4 words a second. A count turns red when a line runs over. Edit every line in your own words.
Write for customers, not for the team
Release notes often say things like "refactor the settings module" or "bump a dependency". A customer cannot picture that. Rewrite each change as what they can now do: "save any report as a shareable link" is a scene, while "add a share endpoint" is not. The tool removes ticket numbers and marks lines that sound internal, but only you know which changes your customers will care about.
Keep it accurate
Show the real product doing the real thing. Screens that change often date a release video quickly, so use the screen planner to decide what to show. For more on the format, read how to announce a new feature with a short video and how long a product demo video should be.
If you ship every week or month, a short film for each release can keep up with the product. Our monthly plan is built for that: send us a brief. We send a one-page storyboard first, then a private preview, and you pay only once you are happy with it. For a one-off launch, the launch checklist puts every step on a timeline.
How to use it
- Paste your release notes. Add the product name and paste the notes, one change per line. Bullets and numbers are fine.
- Find the changes. The tool splits them into lines, removes issue and pull request numbers, and marks changes that sound internal.
- Pick up to three. Tick the changes a customer would notice. Put the strongest first, since it becomes the hook.
- Edit and keep it. Rewrite each line in your own words, watch the word counts, then copy it or send it to us as a brief.
Frequently asked questions
How do I turn release notes into a video?
Choose the one to three changes a customer would notice, write each as one sentence, and show each on the real screen. Add a short hook and one call to action. This tool builds that structure from your own release notes.
How many features should a release video show?
One to three. A 15 second video suits one change, and 30 to 45 seconds can carry two or three. Showing more gives each change too little time for a viewer to follow it.
What does the tool do with ticket numbers?
It removes issue and pull request references such as #482 or PR-12 from the lines, and marks lines that sound internal, like refactors and dependency bumps, so you can leave them out of the film.
Is the script written by AI?
No. It rearranges your own words into a hook, a scene for each change and a call to action. It adds no claims of its own, and nothing you paste is sent to us.
How long should a feature release video be?
Fifteen to forty-five seconds works for most releases. Choose the shortest length that shows each change clearly. The tool gives each scene a word budget so the voiceover fits the time.
Want it made for you? Every Release, $699 / month
For teams that ship every week or month: four videos a month, each with a 15 second cut and the post to go with it. You see a storyboard and a private preview first, and pay only once you are happy.
See what's in Every Release or get a free storyboard →