What is a What's New / Changelog video?
A What's New or changelog video recaps selected product updates. It helps existing users understand recent changes without reading a long release list.
When to use a What's New / Changelog video
Use this format when the audience needs to understand the selected release period, the most useful updates, and their practical impact on users. It works best when the viewer has one clear reason to watch and the source material supports a useful answer, demonstration or explanation. Before drafting, write down what the viewer already knows and what they should be able to do or explain afterward. That decision helps set the right amount of context and keeps the video from turning into a tour of unrelated material.
- When viewers need a focused explanation of the selected release period, the most useful updates, and their practical impact on users.
- When a team needs a reusable explanation for what's new / changelog videos.
- When the source material can support a clear, accurate video brief.
A story arc for this format
Use this outline to plan the selected release period, the most useful updates, and their practical impact on users. Treat the timing and order as editorial choices; adapt them to the source material and the viewer's level of context. Keep each beat focused on one idea, and let the visual prove or clarify what the narration says.
| Beat | What to cover | Review check |
|---|---|---|
| 1. User goal | Name the task behind the selected release period, the most useful updates, and their practical impact on users. | Show the starting screen and any prerequisite. |
| 2. Product path | Follow the real labels and actions in order. | Keep one meaningful action in each scene. |
| 3. Result | Show the completed state or next useful action. | Verify it against the current product before export. |
Worked example: what's new / changelog
Illustrative scenario: A fictional release includes a new report filter, an updated invitation flow, and a corrected export label. Group the changes by the task they affect instead of reading a changelog aloud.
Possible opening line: “Here are three changes in this release that affect daily reporting.” Use it only as a writing prompt; replace the wording with your product's verified voice, terminology and details. For this format, build the middle around the selected release period, the most useful updates, and their practical impact on users.
Before publishing, check that the scene supports the spoken claim. Set a date range, verify every item shipped, and distinguish staged availability from general release.
| Scene | Draft direction | Review question |
|---|---|---|
| Opening | Here are three changes in this release that affect daily reporting. | Does the intended viewer understand why to keep watching? |
| Context | A fictional release includes a new report filter, an updated invitation flow, and a corrected export label | Choose a clear time period. |
| Main beat | Show the selected release period, the most useful updates, and their practical impact on users. | Group related changes. |
| Close | Show the outcome or one appropriate next action. | Set a date range, verify every item shipped, and distinguish staged availability from general release. |
How DemoVexa makes it
In New video, choose Product & Software > What's New / Changelog. This type gives Claude its own instructions for the brief, script, scene plan, and build. The idea field asks for the details this format needs; answer from your source material, and review the brief and script before building. Correct terminology, sequence, availability details and unsupported claims, then inspect the preview at the intended aspect ratio.
What to prepare
Provide confirmed release notes or a product workspace, the date range to cover, and any updates that should be left out.
Name the viewer, the point the video should communicate, and any boundaries the script must respect. Gather current interface labels and approved examples; leave unknown facts out or mark them for confirmation.
Production checklist for a clear what's new / changelog video
Use the checklist during script and preview review. It is especially useful when the first draft contains more detail than the viewer needs.
- Choose a clear time period.
- Group related changes.
- Explain the user impact, not just the change name.
- Label availability and dates accurately.
- Check the sample scenario against the real product, source or approved material: Set a date range, verify every item shipped, and distinguish staged availability from general release.
- Check captions, pronunciation and screen legibility in every format you plan to publish.
Explore related pages
Choose a related format or browse the full directory of video types.
Frequently asked questions
How long should a what's new / changelog video be?
Keep it long enough to explain the selected release period, the most useful updates, and their practical impact on users, and remove context the audience does not need. Start with the point, then give each necessary step or piece of evidence room to be understood.
Can I make a what's new / changelog video without recording?
Yes. DemoVexa builds animated scenes from your workspace and brief, so a camera or screen recording is not required. Narration is optional; you can use an AI voiceover or make a video with captions.
Which formats and languages can a what's new / changelog video use?
Videos can be made in 16:9, 9:16, and 1:1. Voiceover language depends on the provider you use; ElevenLabs supports up to 85 languages, while narration is optional.
What is a useful example of a what's new / changelog video?
A fictional release includes a new report filter, an updated invitation flow, and a corrected export label. Group the changes by the task they affect instead of reading a changelog aloud. This is an illustrative outline, not a customer result or proof that a product has a particular capability. Replace the scenario with a verified workflow and approved data.
What should I check before publishing a what's new / changelog video?
Start with the source material: Provide confirmed release notes or a product workspace, the date range to cover, and any updates that should be left out. Then review the exact screen labels, any claim about availability or outcomes, captions, permissions and the rendered preview. Set a date range, verify every item shipped, and distinguish staged availability from general release.
Make your next product video with DemoVexa
Download the app to make a video from your code, or start a free trial with 15 renders.