Use case

Turn release notes into a short changelog video

Ship a new feature, then show it moving. Flowcase records your app, paces the run, and hands you a captioned MP4 you can drop straight into the changelog.

A line in a changelog tells people something changed. A short video shows them what it does. Flowcase takes the feature you just shipped and turns it into a clean clip: the camera leans into each click, captions name what is happening, and the whole thing renders in the cloud while you move on to the next ticket.

You do not script a screen recording, fight a cursor, or re-shoot when you miss a step. You point Flowcase at the page, say what to demonstrate, and review the result.

One clip per release

Turn each changelog entry into a short, focused video without opening editing software.

Eyes on the new thing

Auto-zoom eases into the button or field you shipped, so viewers never hunt for what changed.

Captions written for you

Every scene gets generated captions, so the clip reads clearly even when it plays on mute.

Reusable for next time

Copy a flow, adjust the steps, and re-render when the feature evolves instead of re-recording.

From release note to rendered clip

Give Flowcase your app's URL and the feature you want to show. Write it in plain English, like "open the new bulk export, pick CSV, and start the download," or hand over exact steps if the path matters. The AI agent plans the clicks and typing, then captures a clean run.

A director pass groups those raw actions into named, paced scenes with timing and importance, the way an editor lays out a timeline. Auto-zoom eases into each button and field and back out, so the new control is always the thing in focus. Captions are generated for you. Then it renders up to 4K in the cloud and gives you the file.

The output is a self-contained MP4. Embed it in your changelog entry, attach it to the release post, or send it to the team that asked for the feature.

Why this beats recording it yourself

Hand-recording a changelog clip means setting up the right window, hitting every step without a fumble, trimming the dead air, and starting over when the mouse jumps. Repeat that for every release and it quietly eats hours you would rather spend shipping.

Flowcase removes the manual takes. Because the run is driven, not performed, the cursor moves smoothly and lands where it should. Because the director pass handles pacing, you get even timing without scrubbing a timeline. Re-running on the next release means updating the steps, not re-filming.

Recording behind a login

Most new features live behind sign-in. Save a login session once on the Connections page and Flowcase records as your account, so the changelog clip shows the real, authenticated product instead of a marketing shell.

Flowcase never sees your password. It reuses the saved session to reach the feature, captures the flow, and renders it like any other run.

A realistic example

Say you just shipped saved views in a project tool. You point Flowcase at the boards page and type: "filter tasks by 'In Review', save the view as 'Review Queue', then switch back to it from the view menu." The agent runs it. The director pass cuts it into three scenes: apply the filter, save the view, recall it. Auto-zoom pushes in on the save dialog and the view menu, captions label each step, and you have a short clip ready for the changelog.

Next sprint you ship sorting inside saved views. You copy the same setup, add two steps, and render an updated clip. No new screen-capture session, no editing software.

Frequently asked questions

What is a changelog video?
It is a short clip that shows a single product change in action instead of just describing it in text. Flowcase makes one by recording your app performing the new flow, then adding auto-zoom and captions so viewers can see exactly what shipped.
How long does it take to make one?
Most changelog clips are a minute or less of footage. You spend a few minutes describing the flow and reviewing the result; the cloud render runs on its own and produces a finished MP4.
Do I need to write a script for every step?
No. You can describe the flow in plain English and the AI agent plans the clicks and typing. If a release has an exact path you want followed, you can give precise scripted steps instead: click this, type that, confirm the result.
Can it record a feature that is behind a login?
Yes. Save a login session once on the Connections page and Flowcase records as your account. It reuses that session to reach gated features and never sees your password.
What resolution and format do I get?
You get an MP4 rendered in the cloud, up to 4K depending on your plan. The file is self-contained, so you can embed it in a changelog, attach it to a release post, or share the link.
How do I keep clips consistent across releases?
Reuse a flow as a starting point. Copy an existing setup, adjust the steps for the new feature, and re-render. The director pass and auto-zoom apply the same pacing and framing every time.

Keep exploring

Make your next release note move

Start free and render 3 minutes of demo every month, no card needed. Point Flowcase at your latest feature and turn the changelog line into a clip people actually watch.

3 min of rendered demo free every month · no card needed