SaaS video is the set of short videos a software company makes as it ships: a clip for each release, a video for each new feature, and videos for help-centre articles, onboarding steps and webinar recaps. Each one can start from something your team has already written. Videngine turns release notes, changelog entries and help articles, with your current screenshots, into narrated, captioned MP4s in landscape and vertical cuts, ready for the feature owner to review.
The SaaS video map: which moments get a video
A SaaS video programme maps each product moment to a source you already write, the video made from it and where it lives.
Product marketing, developer relations, support and documentation each own some of these moments, and the writing usually exists already.
| Moment | Source you already have | Video | Where it goes |
|---|---|---|---|
| Feature launch | The feature page or launch post | A feature announcement video of 60–90 seconds, plus a vertical cut | The launch post, YouTube, social feeds |
| Release notes or changelog | The release's markdown entry | A clip of roughly 30 seconds per release | The changelog entry, the in-app “what's new” panel, YouTube Shorts |
| Help-centre article | The article and its screenshots | One task per video, 45–90 seconds | Embedded in the article; unlisted on YouTube |
| Onboarding step | The onboarding checklist or email copy | A short series, one step per video | In-app, linked from onboarding emails |
| Comparison or use-case page | The page itself | A 60–90 second summary of the page's argument | On the page, YouTube |
| Webinar recap | The written summary or slide notes | The three or four points worth keeping | The recording page, YouTube, social feeds |
Videngine typically gives each source a landscape (16:9) and a vertical (9:16) cut, delivered as files or uploaded to YouTube; placing the MP4 in the changelog, app or help centre is your team's step.
This page covers the whole programme. For the craft of one explainer, see the explainer video maker guide; for cutting a webinar summary down to a script, see turning an article into a video. Other business types are in the industries overview.
Release notes video: one short clip per release
A release notes video keeps pace with shipping only if it is small enough to make every time: markdown in, a clip of roughly 30 seconds out.
Paste a release's markdown into Videngine, or give it the published entry's URL, and it drafts a script and timed scene plan.
Keep a Changelog groups changes under Added, Changed, Deprecated, Removed, Fixed and Security, and says changelogs are for humans, not machines. Those headings map onto scenes:
- Added: a screenshot of the new feature, zooming slowly to the control that matters.
- Changed: a side-by-side scene, old behaviour beside new.
- Fixed: a card per fix worth saying aloud.
- Deprecated and Removed: a card with the date and what to use instead.
- Security: usually best left to the written notes.
Choose two or three changes per clip and let the end card point to the full notes; a product update video that reads out every line is a changelog with a voice.
Start from customer-facing notes, not the developer list. GitHub's automatically generated release notes list merged pull requests, contributors and a link to the full changelog, and GitHub advises checking they include all, and only, the information you want. Rewrite that list for customers before it becomes a changelog video. A bigger launch earns its own feature announcement video, built from the feature page.
Screenshots, product UI and versions
Videngine makes software product video from the screenshots and footage you supply, composing them into scenes with zoom and cards; it does not record your live app.
Help articles bring their own screenshots. Release notes rarely carry images, so supply them alongside the markdown, or in a CSV or JSON payload for a batch, with any brand footage you own.
Each screenshot becomes a moving scene: a slow zoom to the setting, a card with the exact menu path, or old screen beside new. A screenshot that does not fit the frame sits over a blurred fill of itself rather than being cropped; for vertical cuts, a cropped detail or mobile screenshot reads better than a wide desktop one.
Nothing is generated, so the interface on screen is your real one; our guide to text-to-video AI explains the difference between generating footage and assembling a narrated script.
- Keep screenshots current: capture from the build that is shipping, after the final copy change.
- Name them by feature: recurring-tasks-panel.png, not Screenshot 14.png, so the right file turns up at re-render time.
- Keep them clean and consistent: demo data, one window size, theme and zoom level.
When the UI changes, update the help article and its screenshots first, then re-render the video from them, so doc and video never drift apart. Videngine saves the rebuild as a new version, such as _v2, beside the original. The video ledger records who built and reviewed each version, and re-rendering the same video in the same month is free.
A pronunciation lexicon for product names, acronyms and API terms
Decide once how every product name, feature name, acronym and API term is said, and put it in the brand's pronunciation lexicon so the hundredth video says it like the first.
The terms below are examples; your lexicon should follow how your team says them on customer calls.
| Kind of term | Written | Said | Rule of thumb |
|---|---|---|---|
| Product and feature names | Invented names, dropped vowels, odd capitals | However the founders say them | Write each one out in the lexicon. |
| Acronyms said as letters | SSO, API, CLI | “S S O”, “A P I” | Spell them out; give the full term on first use if customers need it. |
| Acronyms said as words | OAuth, JSON | “oh-auth”, “jay-son” | Write the sound out in the lexicon, once. |
| Contested terms | SQL | “sequel” or “S Q L” | Pick the house form; developer relations will know what the audience expects. |
| Versions and API paths | v4.2, GET /v2/tasks | “version four point two”, “the tasks endpoint” | Say it naturally; show the exact string on a card. |
The same voice rules hold banned phrases, positive-only wording and a target length. Narration is in English.
Example: a 30-second release-note clip
A 30-second clip has room for one headline change, one or two smaller ones and a pointer to the full notes.
This plan is illustrative, for a hypothetical task-management product, not a customer video. The source is three lines of markdown:
## 4.2
### Added
- Recurring tasks: repeat any task daily, weekly or monthly.
### Changed
- Search now covers comments as well as task titles.
### Fixed
- Due dates now display in each user's own time zone.
| Time | Scene | On screen | Narration (gist) |
|---|---|---|---|
| 0–3 seconds | Chapter title card | “What's new in 4.2” | “Here's what's new in version four point two.” |
| 3–14 seconds | Screenshot with a slow zoom | The task panel, closing in on the new Repeat field | “Any task can now repeat, daily, weekly or monthly, so routine work sets itself up.” |
| 14–21 seconds | Side-by-side comparison | Search results before and after, now listing matching comments | “Search now covers comments as well as task titles.” |
| 21–26 seconds | Information card | “Fixed: due dates in your own time zone” | “And due dates now show in your own time zone.” |
| 26–30 seconds | End card | The changelog address and version number | “The full notes are in the changelog.” |
About 55 words of narration leaves the screenshots time on screen.
From docs and sitemap to published video
Seven steps take a release note or help article to a published video, and the feature owner's review is the one that cannot be skipped.
- Set up the workspace once. Choose the software and apps workspace, set brand tokens (typefaces, colours, logo, motion) and add the lexicon and target lengths.
- Pick the sources. Paste a release's markdown, or let Videngine read your sitemap and list help articles, feature pages and comparison pages to pick from, in batches. Attach current screenshots named by feature.
- Draft the script. Videngine reads each page in a headless browser and writes a script, a timed scene plan and YouTube metadata.
- The feature owner checks the facts. Whoever shipped the feature reads the script against the product: names, plan tiers, menu path, current screen. Accept it, edit a line or supply your own.
- Render. Narration uses a synthetic voice or your uploaded audio; captions are transcribed from the finished audio. Output is MP4 (H.264) or WebM, up to 1080p.
- Sign off. Every video is reviewed in the studio. A workspace can require that the approver did not build it, and a rejection carries a defect code, such as pronunciation, or photo for a stale screenshot.
- Deliver and publish. Download the MP4s, deliver them to a Google Drive folder you own, or queue approved videos to YouTube with privacy and synthetic-content disclosure set.
WCAG 2.2 success criterion 1.2.2, at Level A, asks for captions on prerecorded audio in synchronised media, except where the media is an alternative to text and clearly labelled as such. Burn captions in for social feeds; use the .srt sidecar where your help-centre player supports closed captions.
YouTube's privacy settings help says unlisted videos can be seen by anyone with the link but stay out of YouTube search unless added to a public playlist, which suits help-centre embeds. See the YouTube video maker guide for channel setup and short-form video at scale for vertical cuts.
Review time, not rendering, sets the pace: a one-minute 1080p video typically renders in a few minutes. See launch pricing for plans.
When Videngine is the wrong tool
Videngine is the wrong tool when the video needs a live screen, a person on camera, bespoke craft or interaction.
| Job | Why Videngine is a poor fit | What fits better |
|---|---|---|
| A screen-recorded click-through demo | It narrates over screenshots; it does not record your screen or follow a cursor | A screen recorder with basic editing |
| A talking-head founder video | No on-camera presenters and no avatars | A camera, a good microphone and an editor |
| A launch film with bespoke animation | Made once; custom illustration and art direction are the point | A motion designer or animation studio |
| An interactive product tour | It produces video files, not clickable walkthroughs | An interactive demo or in-app guidance tool |
Videngine fits the steady run of short videos, each tied to a document that changes.
SaaS video questions
What is SaaS video?
SaaS video is the short video a software company makes around its product: release clips, feature announcements, help-centre and onboarding videos, and webinar recaps. Most of it can start from writing the company already has, such as release notes and help articles.
How do I turn release notes into a changelog video?
Pick two or three changes from the customer-facing notes, pair each with a current screenshot, and point the end card at the full changelog. In Videngine you paste the release's markdown, attach the screenshots, approve or edit the script, and review a clip of roughly 30 seconds before it goes out.
Can Videngine record our app for a software product video?
No. Videngine composes the screenshots and footage you supply into scenes with zoom, cards and comparisons; it does not record your screen or click through a live app. For a click-by-click demo, use a screen recorder.
How do we keep help centre videos up to date when the UI changes?
Update the help article and its screenshots first, then re-render the video from them. Videngine saves the rebuild as a new version beside the original, and the video ledger records who built and reviewed each version.
How much does a release notes video cost?
On Videngine's launch pricing, Starter is $79 a month for 50 videos, Growth $249 for 250 and Scale $599 for 750; a video is one finished render up to two minutes. Re-rendering the same video in the same month is free. Videngine is coming soon, and choosing a plan joins the launch list with no charge today.
Choose your next step
See how other industries use Videngine, or go deeper on building a single explainer before you plan the whole programme.
Bring your last three releases.
Bring the release notes from your last three releases and the screenshots that go with them. Agree the lexicon and who signs off, then let each release make its own clip. Choosing a plan joins the launch list; there is no charge today.
Join the waitlist ↗Published by Videngine, a video rendering product built and run by Wall & Fifth. External links refer to the original documentation or product descriptions; examples are illustrative unless stated otherwise.