A feature announcement video for every release
Most shipped features are announced in text: a changelog entry, a line in a release note, a post that scrolls past. Not because video would not work better, but because commissioning one costs more than the feature is individually worth. So the video budget goes to the two or three launches a year that can justify it, and everything else ships silently.
That maths is what Motionflare changes. Paste the changelog entry or feature page and you get a 15 to 30 second announcement with your real interface, your brand, a written script you approve, voice-over, and music. The cost per video is low enough that the question stops being which releases deserve a video.
How it works
1.Paste the release
A changelog entry, a feature page, or a docs page for what shipped. The script is drafted from that copy, so the claims are the ones you already published.
2.Cut it to the one idea
The draft arrives as editable text. A feature announcement usually wants one idea and one product moment, so this is mostly a deleting exercise.
3.Match the house look
Pick a style pack once and reuse it for every release, so the announcements read as a series rather than as unrelated one-offs.
4.Preview before paying
The full cut plays inline in the browser. Free signup credits cover a complete watchable video.
5.Ship to both surfaces
Export 16:9 for the changelog and the docs page, then re-render 9:16 from the same project for the social post.
Priced per release, not per campaign
A 1080p export is 2 credits, so a fortnightly announcement is a routine cost rather than a budget decision. That is the entire argument for this format.
The real UI, updated
Screenshots come from the live page, so the video shows the feature as it actually shipped rather than the mock from the spec.
Consistent across releases
Reusing one style pack makes twelve announcements over a year look like a series, which is worth more than any single video in it.
Why this is different from a launch video
A launch video introduces something new to people who do not know it exists, so it has to establish the problem before it shows the product. A feature announcement talks to people who already use the thing, so the context is assumed and the video can open on the change itself.
That difference shortens everything. Fifteen to thirty seconds is usually enough: what changed, what it does for you, where to find it. If you are announcing a new product or a major version rather than an increment, the product launch video format fits better, and it is linked below.
A changelog is already a script
Release notes are written the way an announcement script wants to be written: one change, stated plainly, with the user-facing benefit attached. That makes a changelog entry an unusually good input, better than a landing page, which has to sell several things at once.
The drafting step reads that entry and keeps your wording. You are editing an announcement you already wrote rather than reviewing a model's guess at what shipped.
The honest limit
This does not produce a screen recording. If the feature needs a click-by-click walkthrough of a complex flow, record it: a real capture with a real cursor communicates that better than composed motion graphics, and no generated video substitutes for it.
What this format does well is the announcement layer above that: the 20 seconds that make someone want to watch the walkthrough or open the app and look for the feature.
Frequently asked questions
What is a feature announcement video?
A short video, usually 15 to 30 seconds, that tells existing users about a change you shipped. It differs from a launch video by assuming the audience already knows the product, so it can open on the change itself instead of establishing context first.
How long should a feature announcement video be?
Fifteen to thirty seconds covers almost all of them: what changed, what it does for you, and where to find it. Motionflare offers 15, 30, and 60 second targets; 60 is usually more room than an increment needs.
Can I generate one from a changelog entry?
Yes, and it is the best input. Release notes are already written as one change plus its benefit, which is the shape an announcement script wants. Paste the changelog URL and the draft keeps your wording.
How do I keep every release looking consistent?
Choose one style pack and reuse it. The pack fixes typography, palette behaviour, and motion character, so a year of announcements reads as a series. The brand colours and logo are detected from each page you paste.
Is this cheap enough to do every release?
That is the design goal. A scene costs 1 credit at the base model tier and a 1080p export costs 2, so a short announcement is a few credits. Pro is $29/month for 100 credits, which covers roughly ten finished videos.
Does it replace a screen recording of the feature?
No. If the feature needs a click-by-click walkthrough, record it. This format is the announcement layer above that: the short piece that gets someone to open the app or watch the longer demo.
Keep reading
Start with the URL you already have.
Free to try, no credit card. Preview the complete video in your browser before you pay for anything.
Create your video