How to record a software release walkthrough video

Release walkthrough script: 2.5 minutes, with timings

Record on the release build, in an account with the same plan and role as the viewer. Decide the audience before you start; the script below is for end users.

1. 0:00–0:15 · What changed. “In version 3.8, workspace admins can set how long deleted files are kept. Before, it was fixed at 30 days.”
2. 0:15–0:30 · Who gets it and when. “It is on for all Business workspaces from October 6. On other plans you will not see the setting.”
3. 0:30–0:45 · Before. Show the old place or the old limit for a few seconds, only so the change makes sense.
4. 0:45–1:50 · The new path. Perform it once at normal speed: name the menu, click, pause on the result. End on the saved state.
5. 1:50–2:10 · What did not change. “Existing files keep their current 30-day rule until you change it. Nothing is deleted earlier.”
6. 2:10–2:30 · Next step. Point to the release notes and the help article, and say where to send questions.

What to show in a release video, by audience

One recording rarely serves everyone. Users want the new path. Support wants the edge cases. Sales wants the one-line benefit. Record the user version first, then a shorter cut or a second take for internal teams.

Worked example: a retention setting in version 3.8

The release: a file-sharing product ships configurable retention for deleted files. The user video is 2:24 long. It opens on Settings → Data, shows the old fixed “30 days” label for five seconds, then sets retention to 90 days, saves, and ends on the confirmation banner.

The line that prevents the most tickets is at 1:52: “Existing files keep their 30-day rule until you change it.” Without it, admins assume the new default applies retroactively and write in to ask.

The support cut reuses the same footage and adds 90 seconds at the end: what a non-Business workspace sees (no setting), the error when retention is set below 7 days, and the escalation channel. The post that goes with both versions: “3.8: Configurable retention for deleted files. Business plan, rolling out October 6. Video (2:24). Release notes: link. Help article: link.”

Pre-publish checklist for a release video

Run this the day before the release goes out. A release video with one wrong label generates more tickets than no video.

• Recorded on the release build, not a development branch.
• Every label spoken in the narration matches the label on screen.
• Plan, role, and rollout date are said aloud and match the release notes.
• The final saved state is on screen for at least three seconds.
• “What did not change” is stated.
• No test data with real names, no internal tabs, no staging URLs in the frame.
• The video links to the release notes, and the release notes link to the video.
• Someone outside the feature team watched it once and could repeat the steps.
• The project file is saved until rollout is complete.

Fixing a release video the night before launch with Qreata

Release videos get recorded before the release is final, and something small always moves. The evening before launch, the setting is renamed from “Retention” to “Data retention.” Your 2:24 video shows and says the old name at 1:12. In Qreata you open the project on the final build, pick Replace Take (the Rerecord tool in the editor), Shift-drag across 1:08–1:20, re-record those 12 seconds, and export. The range has to sit inside one segment and can’t cross a cut, and the retake has to fill the 12 seconds: a shorter one is rejected, a longer one is trimmed. The intro, the before-and-after, and the closing stay as approved.

For the support cut, you do not start over either. Qreata projects hold multiple clips, so you use Add clip to record the edge cases into the same project and export a second version.

Small settings are hard to read in an embedded player. With Auto-zoom on clicks turned on, Qreata adds zooms on your real clicks; keep the one on the retention field and delete the rest, or add a zoom by hand on the confirmation banner, which has no click. If saving takes 20 seconds, set that segment to 4× speed. Export is MP4 (H.264) up to 4K. Pre-release footage stays on your Mac, because recording and editing are local, need no account, and upload nothing unless you press the button.

Captions in video burns word-highlighted captions into the MP4, which covers users who watch the release video muted. One limit to plan for: Qreata does not export SRT or VTT files, so if your host needs a caption file, create it there. To check the workflow before your next release, spend ten minutes of the 7-day trial recording the script above on a feature you shipped last month, then replace one 10-second section and watch both joins.

Common mistakes in release walkthrough videos

These are the ones that cost support time after launch.

• Turning it into a product tour. The viewer already uses the product; show the change.
• Not saying who gets it. Users on other plans look for a setting they do not have.
• Recording on staging with different labels or a visible feature flag.
• Skipping “what did not change,” which is where most worried questions come from.
• One video for users, support, and sales together.
• Publishing the video without a link to the written notes, or the notes without the video.
• Leaving the old video up when the feature changes in the next version.