Release Notes to Video for showing customers what changed and why
Turn shipped changes into a clear product story that shows both the workflow and the value. Create the main release update, then adapt it for help content, campaigns, and sales follow-up.
Trusted by teams at
How it works
From changelog text to a finished release video in four steps.
No deck. No editor handoff. Paste the notes, accept the storyboard, ship the video.
Paste the release notes
Drop a markdown changelog, GitHub release URL, or the body of your release email. ngram parses the headings, the category tags (New / Improved / Fixed), and the linked screenshots.
ngram groups features and ranks them
The agent merges related changes into video segments, promotes the headline feature, and tucks bug fixes into a single closing card so the video tells the story of the release instead of reciting the bullet list.
Review and adjust the storyboard
Reorder features, demote a bullet to a footnote, swap the hero feature visual, or split a 90-second cut into a 30-second LinkedIn version. Plain-language edits in chat, no timeline.
Export and post
Review the release notes video for its intended channel, including the crop and caption placement, then export one MP4 from Studio. Prepare and review another aspect ratio as a separate edit.
Output controls
Controls tuned for product update videos, not generic edits.
Feature grouping rules
Decide whether the video opens with the top-rated new feature, the most-requested fix, or the migration callout. Bug fixes can be merged into a single rolling card.
Bug fix condensing
A 14-item fix list collapses into one 4-second card so the release video stays focused on what shipped, not what got patched.
Hero feature emphasis
Pin one feature to the cold open with a larger scene, custom motion graphic, and the screenshot or Loom you linked in the notes.
Prepare each channel edit separately
Set the intended channel and aspect ratio for the release notes video, then review the crop, caption placement, and CTA before exporting one MP4. Prepare another channel version as a separate edit.
Brand kit on every release
Logo, fonts, motion style, and category color codes apply automatically. Release v4.1 and v4.2 stay visually consistent without an editor in the loop.
Burned-in captions per release
Feature names, version numbers, and migration warnings stay readable in muted feeds. Caption styling follows the brand kit.
Localized release variants
Re-render the same release video with translated voiceover and captions for non-English customer segments. Useful for EMEA and APAC rollouts.
Pre-release file safety
Pre-launch changelogs stay private to your workspace, and you can delete your account to trigger a full data purge. Talk to sales about security, access controls, and data handling for your team.
The rest of ngram
The ngram stack behind every release video.
Script Generation
Turns headings, change-type tags, and bullet copy from your release notes into a voiceover script that names the feature, the value, and the next step.
Learn moreMotion Graphics
Auto-animated lower-thirds for feature names, version chips for v4.1 → v4.2, and category badges (New / Improved / Fixed) that match the notes.
Learn moreBrand Kit
Pins logo, font, color, intro card and outro CTA so every release video looks like it came from the same product team, even when a different PM publishes the notes.
Learn moreAI Voiceover
A house voice for the changelog. Read v4.2 in 30 seconds and queue v4.3 next week without re-recording a single narration.
Learn moreCaptions & Subtitles
Burned-in captions on the LinkedIn cut and the in-app announcement modal, the two places release videos play muted by default.
Learn moreConvert the finished release notes video
Finish the release notes video in Studio and download one MP4. When a site, player, or handoff requires MOV, WebM, or MKV, convert that file separately in Video Converter, one input and one output per job.
Learn moreUse cases
Eight release moments worth a 60-second video.
Changelog video for the public release page
The same release notes that live on /changelog, narrated, captioned, and embedded above the bullet list. Customers see the feature before they read about it.
See use caseFeature announcement on LinkedIn
A 9:16 cut of the release video that pulls the hero feature, the screenshot, and the value claim into the first three seconds of the LinkedIn feed.
See use caseInternal PM changelog for the team
A 60-second internal cut that PMs drop in #released so engineering, support, and CS know what shipped without scrolling Linear.
See use caseProduct launch video from release notes
The same notes paired with the brand kit and a hero screenshot become the LinkedIn launch post for a v1.0 or a major.0 release.
See use caseFeature announcement video for marketing
PMM takes the engineering changelog, removes the version numbers, and renders a customer-facing announcement video tuned for the campaign calendar.
See use caseDevRel update video for developers
Developers skim release notes. A 90-second video that walks through SDK changes, breaking changes, and migration steps gets opened, watched, and shared.
See use caseFeature education video for existing customers
CS attaches the release video to QBRs and renewal emails so enterprise accounts learn about features they paid for but never enabled.
See use casePM feature launch video for the in-app modal
A 1:1 cut that plays inside the in-app 'What's new' modal. Same release notes, video format, lower scroll-past rate than a static screenshot.
See use caseOther converters
Starting from a different source? There's a converter for that.
Release notes are one of seventeen inputs. The text-to-video pipeline behind this page also handles long-form docs, blog posts, product pages, and PDFs.
Paste any block of writing, like a launch post, a memo, or an email, and get the same scene-grouped video without the version-chip styling.
Open converterWhen the source is a longer doc rather than a structured changelog. The agent extracts the headings, the key claims, and the screenshots.
Open converterTurn the launch blog post that accompanies the release into a companion video for LinkedIn and YouTube. Same source, different channel.
Open converterTools that pair with this converter
After the release video lands.
Editing the release video further
Once the first cut is back from the storyboard
Video Editor
Open the release video in the timeline editor to nudge a scene, swap a screenshot for an in-product capture, or trim the closing CTA.
Open toolAdd Subtitles to Video
Lock in burned-in captions for the LinkedIn cut, where 85% of viewers watch the release video muted.
Open toolVideo Cutter
Trim a 90-second public release video into a 20-second internal Slack version by selecting only the hero feature and the migration warning.
Open toolAdd Music to Video
Prepare separate edits for the two placements: keep the background track on the YouTube version, then mute it for the in-app modal and render that version separately.
Open toolGenerating release assets from scratch
When the release notes are thin or still in draft
Text to Video
When the changelog is still a Linear comment, paste the comment and get a draft release video back before the notes are even published.
Open toolAI Video Generator
Generate B-roll for features the team is shipping next sprint so the release video has visuals before the screenshots are ready.
Open toolVideo Script Generator
Draft the voiceover script from the release notes first, hand it to the PM for review, then render the release video from the approved script.
Open toolAI Avatar Video Generator
Put a consistent on-brand presenter in front of every release video, sprint after sprint, without booking studio time.
Open toolPolishing the release notes input
Sharpen the source before you convert it
Audio to Text
If the engineer recorded a voice memo summary of the release, transcribe it into release-note bullets the converter can consume.
Open toolVideo Translator
Re-render the same release video in German, Japanese, or Portuguese for EMEA and APAC customers, with caption and voiceover translation.
Open toolYouTube Title Generator
Generate the release video's YouTube title and description from the same release notes, so the upload metadata matches the storyboard.
Open toolBuilt for teams
Who reaches for release videos in your company?
Product Marketing
Turn every release into a LinkedIn announcement video and a public changelog clip, without re-briefing an agency every sprint.
See workflowsProduct Managers
Drop the release notes into ngram, ship a 60-second changelog video, post it in #released. Adoption climbs because users see the feature.
See workflowsDeveloper Relations
Companion update videos for SDK changes, breaking-API releases, and library migrations. Developers actually watch them; they skim the written notes.
See workflowsCustomer Success
Attach the release video to QBR decks and renewal emails so enterprise accounts learn about features they're paying for.
See workflowsGrowth Marketing
Convert the changelog into paid social creative, so every release becomes a re-engagement campaign for cooled-down users.
See workflowsFounders
Weekly build-in-public videos from the team's own release notes. No editor, no agency, no calendar negotiation.
See workflowsSupport Teams
Pin a 30-second release video at the top of the help-center home page so inbound tickets about new behavior drop after every ship.
See workflowsSales Enablement
AEs get a release video they can forward to deals in flight, so the prospect sees what shipped without reading a paragraph of bullets.
See workflowsIntegrations
Wire the release video into your changelog workflow.
The release notes already trigger a Slack message, an email blast, and a Discourse post. Drop the video render into the same chain.
whenA release tag publishes in GitHub or Linear marks a cycle 'shipped'
thenUse Zapier's documented Create Video or Get Status action for this Release Notes to Video job with its supported input, then pass the result to the next step.
whenClaude reads your changelog markdown via MCP at the end of a sprint
thenUse MCP's documented create and status tools for this Release Notes to Video job with its supported input, then return the status or result to the agent.
whenThe video from your release notes is ready for LinkedIn Social Publishing Beta
thenAdd the approved release notes video to the LinkedIn calendar, then choose a recurring schedule.
whenYour workflow has an approved release notes ready for Studio
thenUpload the file in Studio; use n8n's documented Create From Text, Create From URL, or Get Status node for this Release Notes to Video job, then pass the result onward.
whenYou hit 'Convert to release video' on your GitHub releases tab
thenGet a branded release video back in a new tab, ready to paste in Slack
How it compares
If you've been making release videos a different way.
Most teams that ship a release video today fall into one of three workflows: record a Loom and call it done, render a talking-head with Synthesia, or assemble bullet slides in Pictory. ngram handles the writing and editing for one reviewed cut; prepare other channel versions separately.
| Feature | ngram | Loom | Synthesia | Pictory |
|---|---|---|---|---|
| Starts from raw release notes | Paste markdown, GitHub URL, or PDF | Manual narration over screen recording | Manual script writing | Manual script writing |
| Groups changes into video segments | Auto-groups by feature and severity | None | None | Slide-per-bullet only |
| Bug-fix condensing | Single rolling card for fixes | Manual edit | Manual edit | Manual edit |
| Brand intro / outro per release | Auto-applied from brand kit | Manual every time | Avatar branding only | Template selection |
| Channel-specific editing workflow | One reviewed MP4 per channel-specific edit | 16:9 only | 16:9 + 9:16 (extra render) | Re-edit per format |
| Burned-in captions for muted feeds | Default on every cut | Auto-caption (separate step) | Default | Default |
| Localized release variants | Translated voiceover and captions | None | Voiceover only | Caption-only |
| Time from notes to posted video | Under 5 minutes | 20-40 minutes of recording | 30-60 minutes of script + render | 30-60 minutes of slide build |
| API + webhook for release pipelines | REST API with self-service API keys; webhook subscriptions for video.completed or video.failed; MCP, Zapier, and n8n for documented workflows | None | API (enterprise tier) | None |
| Pre-release file safety | Workspace-private, account-level data purge | Workspace-bound | Workspace-bound | Workspace-bound |
FAQ
Questions about converting release notes to video
Still curious?
Release Notes → Video
Ship the next release with a video, not just bullets.
Paste the changelog, accept the storyboard, post the cut. The next release video is five minutes away.