Release notes videos

Turn your changelog into a release notes video

Paste your release notes or link to the changelog entry. Motiongist turns the changes users will notice into a short narrated video, ready to post on release day.

  • 500 free credits at sign-up
  • Free storyboard review
  • 45–180 s, vertical 9:16
  • 8 voices, 10 languages

Your link

9:16 · 1080×1920

“https://yourapp.example/changelog/4-2 (dark mode, CSV export, faster search)”

Length
45–60 s
Look
Night
Voice
Daniel
Rendering
2D · English

Storyboard · 5 scenes

  1. 0–4 sOpening. A version badge reading “4.2” lands in the middle of the screen. Title: “What’s new”.
  2. 4–16 sDark mode. A dashboard mock-up flips from light to dark, row by row, as the narration names the setting.
  3. 16–30 sCSV export. A table mock-up, a cursor on “Export”, and a file icon dropping into a folder.
Estimated price481 credits
With the final voice. The studio shows the exact price before you confirm.

Your team ships every week, and most users never hear about it. Changelogs are written for the people who already read changelogs. A sixty-second “what’s new” video reaches everyone else: the followers who would scroll past a link, the customers who skim newsletters, the prospects deciding whether the product is alive.

Because the source is your own release notes, the script sticks to what you actually shipped. Each change becomes one scene, with an animated mock-up of the screen that changed, and the video ends on where to find the full notes.

How it works

From release notes to release-day video

  1. Step 1

    Give it the notes

    Link to the changelog entry or paste the release notes. Add a note on which two to four changes matter most to users; internal fixes can stay in the text.

  2. Step 2

    Pick a tone and a look

    Short (45–60 s) suits most releases. Night works well for developer tools, Light for business apps, or use your brand look from the Solo plan.

  3. Step 3

    Check names and numbers

    In the free storyboard step, make sure feature names, version numbers and any figures match the notes exactly.

  4. Step 4

    Ship it with the release

    Publish now or schedule to YouTube, TikTok, Instagram or LinkedIn, with post copy for each, or embed the video on your changelog page.

Example

What’s new in version 4.2

What you give: “https://yourapp.example/changelog/4-2 (dark mode, CSV export, faster search)”

What the video shows, scene by scene

  1. 0–4 s

    Opening. A version badge reading “4.2” lands in the middle of the screen. Title: “What’s new”.

  2. 4–16 s

    Dark mode. A dashboard mock-up flips from light to dark, row by row, as the narration names the setting.

  3. 16–30 s

    CSV export. A table mock-up, a cursor on “Export”, and a file icon dropping into a folder.

  4. 30–44 s

    Faster search. A search bar returns results instantly, with the speed figure exactly as written in the release notes.

  5. 44–56 s

    Where to find it. Logo, “Full notes at the link”, and the changelog address as the closing title.

An illustrative storyboard for this brief (Night look, 2D). Motiongist writes its own scenes from your input, and you can edit them for free before rendering.

5 scenes · 56 s

What’s new in version 4.2

Watch real renders

Why Motiongist

Why it fits a release rhythm

  • Your changelog is the source

    Give a link and the script is based on that page, with a fact review before rendering. Nothing is added that you didn’t ship.

  • Automate it from your pipeline

    From the Studio plan, the REST API can create the video from your notes, and a webhook tells your system when it is ready.

  • Post on release day

    Publish or schedule to YouTube, TikTok, Instagram and LinkedIn from the video page. Publishing costs no credits.

  • A known cost per release

    A short video is 400 credits plus the final voice. Every render shows its exact price first, and failed renders are refunded.

  • Readable in a feed

    Word-by-word captions, music and sound effects come built in, so the video works muted while people scroll.

Automating it, step by step

There is no ready-made plug-in for a specific tool, but the pieces are there. From the Studio plan, a script in your release process can create a project with the release notes as the source, request a quote, approve it, and wait for the webhook that says the video is ready. Every render needs an approved, signed quote, so automation can’t spend credits without a price on record.

If you prefer to ask an agent, the MCP server lets Claude, ChatGPT or Cursor do the same from a chat: “Make a short video of the 4.2 notes and show me the storyboard.”

What to leave out

Bug fixes, refactors and dependency bumps belong in the written notes. The video is for changes a user can see or feel. If a release has nothing like that, skip the video that week.

What it costs

One credit balance. A short video is 400 credits, a standard one 700, a long one 1,000, plus 1 credit per 10 narrated characters for the final voice.

Full pricing
  • Free

    $0

    500 credits at sign-up

    To try it out: a first video, draft voice, discreet watermark.

  • Solo

    $19 / month

    3,000 credits / month

    To post every week: final voice, clean exports, your brand.

  • StudioMost popular

    $49 / month

    30,000 credits / month

    To produce at volume: priority rendering, custom looks, API and MCP.

  • Team

    $149 / month

    100,000 credits / month

    For teams and agencies: 5 seats, 4 renders in parallel, one invoice.

Prices before tax, in US dollars. Yearly billing is 35% cheaper. Failed renders are refunded automatically.

FAQ

Questions, answered

Can it read our changelog page directly?

Yes. Give the link to the entry and the script is based on what the page says. You can also paste the notes as text if the page needs a login.

Can we generate a video automatically for every release?

Yes, through the REST API or the MCP server, from the Studio plan. Your pipeline sends the notes, approves the quote and gets a webhook when the video is ready. See the API docs.

How long should a release video be?

Short (45–60 s) fits two to four changes. For a major version with a story to tell, a standard video (90–120 s) gives each change more room.

Will the feature names be right?

They come from your notes, and you can check every line in the storyboard step. Put names that must appear exactly in the “must show” notes.

Does it work for developer tools?

Yes. Pick the developer audience and the Night look; the script can mention commands or settings, shown as clean on-screen text rather than a terminal recording.

Ready to make your first one?

500 free credits at sign-up. Review the storyboard for free, see the exact price, then render.

Create your video