Turn shipped changes into a useful product update instead of another entry customers skip. Show what changed, why it matters, and how it works, then reuse the project for launch and sales channels.
Video generation uses credits. Review your estimate in ngram. MP4 downloads require Basic or higher.
How credits workTrusted by teams at
How it works
Paste the changelog, accept the plan containing the script, ship the video. No editor handoff, no deck.
Drop Keep-a-Changelog markdown, paste a plain version list, or give us your /changelog URL. ngram reads the version headings, the change-type sections (Added / Changed / Fixed / Deprecated), and any linked PR numbers or screenshots.
The agent promotes the headline change to the cold open, merges related commits into one feature segment, and rolls every bug fix into a single closing card so the recap tells the story of the version instead of reading the diff out loud.
Reorder entries, demote a minor change to a footnote, swap in the screenshot you linked from the PR, or split a 90-second cut into a 30-second social version. Plain-language edits in chat, no timeline scrubbing.
Review the changelog 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
Decide whether the recap opens with the top new feature, a breaking change, or a migration callout. The Added / Changed / Fixed structure of your changelog drives the scene order by default.
A 14-line Fixed section collapses into one 4-second card so the version recap stays focused on what shipped, not on every typo and dependency bump.
Pin one entry to the cold open with a larger scene, a custom motion graphic, and the screenshot or clip you linked from its pull request.
Auto-rendered version chips track v4.1.0 to v4.2.0, and breaking-change badges flag the entries developers need to read before they upgrade.
Set the intended channel and aspect ratio for the changelog video, then review the crop, caption placement, and CTA before exporting one MP4. Prepare another channel version as a separate edit.
Logo, fonts, motion style, and change-type color codes apply automatically, so v4.1.0 and v4.2.0 stay visually consistent without an editor in the loop.
Feature names, version numbers, and migration warnings stay readable in muted feeds and in-app modals. Caption styling follows the brand kit.
Re-render the same changelog recap with translated voiceover and captions for non-English customer segments. Useful for EMEA and APAC rollouts.
The rest of ngram
Reads the version headings, change-type tags, and commit copy in your changelog and writes a voiceover script that names the feature, the value, and the upgrade step, not the raw diff.
Learn moreAuto-animated lower-thirds for entry names, version chips that step from v4.1.0 to v4.2.0, and change-type badges (Added / Changed / Fixed) pulled straight from the changelog structure.
Learn morePins logo, font, color, intro card, and outro CTA so every version recap looks like it came from the same product team, even when a different engineer cuts the release.
Learn moreA house narrator for the changelog. Read v4.2.0 in 30 seconds and queue v4.3.0 next sprint without re-recording, using ElevenLabs and MiniMax voices.
Learn moreBurned-in captions on the social cut and the in-app announcement modal, the two places a changelog recap plays muted by default.
Learn moreThe changelog video leaves Studio as a single MP4. Use Video Converter afterward to make one MOV, WebM, or MKV file; it is a separate one-file, one-output step.
Learn moreUse cases
The same version entries that live on /changelog, narrated, captioned, and embedded above the list. Customers see the headline feature before they scroll the diff.
See use caseA 60-second cut a PM drops in the team channel so engineering, support, and CS know what shipped in v4.2.0 without reading every line of the changelog.
See use casePull the headline entry out of the changelog and turn it into a 9:16 feature announcement, with the screenshot and value claim landing in the first three seconds.
See use caseDevelopers skim changelogs. A 90-second recap that walks through SDK changes, breaking changes, and migration steps gets opened, watched, and shared.
See use caseA 1:1 cut that plays inside the in-app 'What's new' modal. Same changelog entry, video format, lower scroll-past rate than a static screenshot.
See use caseThe version entry behind a major.0 release, paired with the brand kit and a hero screenshot, becomes the launch-day hero video PMM ships to the campaign calendar.
See use caseCS attaches the version recap to QBRs and renewal emails so enterprise accounts learn about features they pay for but never enabled after the last release.
See use caseWhen a version changes how a feature works, support pins a short recap at the top of the help center so tickets about the new behavior drop after the release.
See use caseOther converters
A changelog is one of many text inputs. The same script-and-storyboard engine behind this page also reads release notes, markdown docs, and wiki pages.
When the source reads like a customer-facing release post rather than a developer changelog. ngram groups the features and drops the bug-fix noise the same way, with announcement framing instead of semver chips.
Open converterFor any markdown file beyond CHANGELOG.md. The agent reads the headings, code blocks, and lists and turns the structure into scene-grouped video.
Open converterWhen the version is documented in a longer doc rather than a structured changelog. ngram extracts the headings, the key claims, and the linked screenshots.
Open converterTools that pair with this converter
Editing the recap further
Once the first cut is back from the storyboard
Open the changelog recap in the timeline editor to nudge a scene, swap a placeholder for an in-product capture of the new feature, or trim the closing CTA.
Open toolLock in burned-in captions for the social cut of the recap, where most viewers watch a changelog clip muted in the feed.
Open toolTrim a 90-second public version recap into a 20-second internal clip by keeping only the headline feature and the breaking-change warning.
Open toolPrepare separate edits for the two placements: keep the background track on the public-page version, then mute it for the in-app modal and render that version separately.
Open toolGenerating recap assets from scratch
When the changelog is thin or still in draft
When the changelog is still a draft PR description, paste the text and get a rough version recap back before the entry is even merged.
Open toolGenerate B-roll for an entry whose screenshot is not captured yet, so the recap has visuals before the feature ships to staging.
Open toolDraft the voiceover script from the changelog first, hand it to the PM for sign-off, then render the recap from the approved script.
Open toolPut a consistent on-brand presenter in front of every version recap, sprint after sprint, without booking a studio.
Open toolPolishing the changelog source
Sharpen the source before you convert it
If an engineer recorded a voice memo summarizing the version, transcribe it into changelog bullets the converter can read.
Open toolRe-render the same changelog recap in German, Japanese, or Portuguese for EMEA and APAC customers, translating both caption and voiceover.
Open toolGenerate the recap's title and description from the same changelog so the upload metadata matches the version it covers.
Open toolBuilt for teams
Drop the changelog into ngram, ship a 60-second version recap, post it where the team lives. Adoption climbs because users see the feature instead of scrolling the diff.
See workflowsCompanion recap videos for SDK changes, breaking-API entries, and library migrations. Developers watch them; they only skim the written changelog.
See workflowsTurn the headline entry of each version into a social announcement video and a public changelog clip, without re-briefing an agency every sprint.
See workflowsAttach the version recap to QBR decks and renewal emails so enterprise accounts learn about features they are paying for but never enabled.
See workflowsWeekly build-in-public recaps straight from the team's own changelog. No editor, no agency, no calendar negotiation.
See workflowsPin a 30-second recap of the entries that changed behavior at the top of the help center so inbound tickets drop after every version ships.
See workflowsConvert the changelog into re-engagement creative, so every version becomes a reason to win back cooled-down users.
See workflowsIntegrations
Cutting a version already fires a Slack message and a docs deploy. Drop the recap render into the same chain so the video ships when the changelog does.
whenA new version entry lands in your CHANGELOG.md or a git tag is pushed
thenUse Zapier's documented Create Video or Get Status action for this Changelog to Video job with its supported input, then pass the result to the next step.
whenYour coding agent reads the merged changelog entries at the end of a release cycle
thenUse MCP's documented create and status tools for this Changelog to Video job with its supported input, then return the status or result to the agent.
whenYour workflow has an approved changelog ready for Studio
thenUpload the file in Studio; use n8n's documented Create From Text, Create From URL, or Get Status node for this Changelog to Video job, then pass the result onward.
whenYou hit 'Convert to recap video' while viewing your hosted changelog page
thenGet a branded version recap back in a new tab, ready to drop into the release announcement
How it compares
Most teams that make a changelog video today fall into one of three workflows: record a Loom over the release page, render a talking head in Synthesia, or build 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 a raw changelog | Paste markdown, fetch a URL, or upload a PDF | Manual narration over the release page | Manual script writing | Manual script writing |
| Separates features from patch notes | Auto-groups by change type and severity | None | None | Slide-per-line only |
| Version chips and semver labels | Auto-rendered from version headings | Manual edit | Manual edit | Manual edit |
| Brand intro and outro per version | 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 plus 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 version recaps | Translated voiceover and captions | None | Voiceover only | Caption-only |
| Time from changelog to posted video | Under 5 minutes | 20-40 minutes of recording | 30-60 minutes of script plus render | 30-60 minutes of slide build |
| API and 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 |
Changelog → Video
Paste the changelog, accept the plan containing the script, post the cut. Create your next version recap with ngram.
Follow a workflow from source material to a video you can review, share and make again.
Each product release
Give Claude the shipped changes. Use ngram to create a narrated update, review its plan and bring the finished video back to the conversation.
Release notes and real product screenshotsA narrated customer update
Ways to run: Claude
Every release
Give customers a short explanation of what shipped, who it helps and where to find it. Use your release notes to make a repeatable video update, then check the result against the shipped product.
Published release notesRelease roundup video
Ways to run: In ngram
