Auto-generate product demo videos from your changelog
Turn your changelog into product demo videos automatically, Remotion templates read your release data and render an MP4 per feature, on your Mac, for free.
You can turn a changelog into product demo videos automatically: a Remotion template reads your release data — version, feature names, descriptions, screenshots — and renders a polished MP4 for each entry. Because Remotion is programmatic video, the layout is code and the data is a variable, so one template produces a consistent video per feature with correct text and on-brand styling every time. ReDock runs Remotion as a one-click stack on the Bun runtime with live frame progress, so the whole pipeline runs on your Mac for free.
Why changelogs and code video fit together
A changelog is structured data: a list of releases, each with a title, a description, maybe a screenshot and a version number. A product demo video is a repeatable format: intro, feature highlight, a few bullet points, outro. When your video is a template and your changelog is data, generating videos is just mapping one onto the other.
This is exactly what programmatic video is good at and what a timeline editor is bad at. In an editor, fifty releases means fifty manual videos. In Remotion, fifty releases means feeding fifty data objects to one template and rendering. The scene is drawn exactly from the data — no misspelled feature names, no off-brand colors, because Remotion draws precisely what the code specifies. The distinction is spelled out in free AI video with Remotion, and the trade-offs against editors are in programmatic video vs. editors.
The pipeline shape
Here’s how a changelog-to-video pipeline is built:
- Structure the changelog. A JSON or markdown file with an entry per feature: title, description, image, version. Most teams already keep this.
- Build one demo template. A Remotion scene that takes those fields as props — a title card, the screenshot, animated bullet points, a closing frame.
- Map data to renders. For each changelog entry, pass its data to the template and render an MP4. The layout is identical; only the content differs.
- Collect the outputs. One video per feature, named by version, ready to attach to release notes or post.
The batch step — rendering many videos from a list — runs on the Bun runtime and is covered in detail in render farm of one.
Let an agent close the loop
ReDock exposes its whole app as MCP tools on localhost:47200, which makes the “read the changelog, render the videos” step something an agent can drive. You point Claude, Cursor, or ReDock’s built-in agent at your changelog and template, and it maps entries to renders. Because ReDock ships a local-LLM catalog, this works with no API keys — the model runs on your Mac. An agent can also help write the demo template itself, as in Claude-written Remotion scenes. Connection details are in the MCP docs.
Consistency is the real win
When demo videos are generated from a template, every release looks like it belongs to the same product. The intro is identical, the typography is fixed, the brand color is a constant. A human editing fifty videos will drift — slightly different timing here, a wrong shade there. Code doesn’t drift. That consistency is what makes a video changelog feel professional rather than cobbled together.
ReDock — a free (alpha) native macOS app — keeps this entirely local: your release data, your screenshots, your renders, all on your machine at zero marginal cost. Render the back catalog, then render each new release as it ships. If you’re assembling a no-cost pipeline, it fits the zero-dollar creator stack. New to Remotion? Start with the Remotion tutorial.
One honest note: screenshots and screen recordings are assets you supply — the template places and animates them exactly, but it doesn’t capture your UI for you. Point it at the images you already have.
FAQ
Does this record my product’s screen automatically?
No. You supply the screenshots or screen recordings; the template places and animates them precisely. Remotion draws the layout from your data — it doesn’t capture your UI on its own.
How consistent are the videos?
Fully consistent. Every video comes from one template, so intro, typography, and branding are identical across releases. Only the per-feature content changes.
Can I regenerate old videos if I rebrand?
Yes. Change the template’s colors or layout once and re-render the whole changelog. Because it’s code driven by data, the entire back catalog updates from a single edit.
A video per release, generated from data you already keep. Download ReDock and turn your changelog into demos today.