How to Make a Feature Announcement Video for Your Changelog (20-Second Template)

A feature announcement video for your changelog works best at about 20 seconds and five beats: the old way (4 seconds), the new way (4), one cropped screen (6), who it's for (3) and where to find it (3). Make one only when a feature changes how people do a task they repeat; fixes and settings tweaks read faster as a line of text and a screenshot. Caption every line, keep one look across releases so the series looks like your brand, and export a 16:9 file for the changelog and LinkedIn and a 9:16 file for vertical feeds.

This is for product marketers and founders who ship every week or two, already write a text changelog, and want a short video per release without hiring a video team.

Oakgen is our product. Oakgen Motion is one way to build these videos and is covered near the end, alongside the cases where a plain screen recording does the job better.

The short version

How this was put together: researched on October 22, 2026, from the W3C's WCAG 2.2 pages, LinkedIn's video ads page and Can I email's video support table. Lengths per placement are our recommendations, not platform rules. The worked example uses an invented product.

Video or text changelog: a decision rule

Most of a changelog should stay text. A video costs you at least an hour each time, and a video for a bug fix teaches readers to skip your videos.

Sort by two things: how big the change is, and who you're telling.

Then run three quick checks, in order, and stop at the first no:

1. Can you say the old way in one sentence? "You approved swaps over text messages." If you can't name the pain, the video will just be a tour.
2. Does seeing it change someone's mind faster than reading? A before-and-after on screen does. A new API field doesn't.
3. Will you put it somewhere people actually look? A video only on the changelog page reaches the people already reading the changelog. If you won't also use it in-app, in email or on social, a screenshot is enough.

For the headline launch row, use the longer format in how to make a product launch video in one evening. This post is the smaller, weekly version.

The 20-second feature announcement video template

Fill in the on-screen and voice columns, then read the voice lines aloud with a timer. If they run over, cut words rather than speaking faster.

Two things make this different from a launch video. The product name appears at second four, not second seven, because changelog viewers already know you. And the closing beat is a location, not a sales ask. "Settings, then Shifts, then Swaps" is more useful to an existing customer than "Try it free".

The "who it's for" beat is the one people cut, and they shouldn't. It's where you mention that a feature is on a higher plan, or admin-only, before someone spends five minutes looking for a menu they can't see.

Example: a filled-in 20-second storyboard

Rotafox is an invented product, used only to show the template filled in. It is not a customer or a real company. It does shift scheduling for restaurants, and this week it shipped approvals for shift swaps.

That's about 35 spoken words. It works muted, because every voice line is also on screen in some form, and it uses a single screen. If you can't explain your feature with one screen, that's a hint it needs the longer, narrated format covered later.

Capturing the one screen

A full-width dashboard shrunk into a feed is grey noise. Capture at 2x on a demo account with fake data, crop to the control that changed, and clean the frame, as set out in the launch video guide's prep section. Two things matter more for a weekly feature series:

• Show the state after the action. A screenshot of an "Approve" button says less than one where the row has just turned green.
• Keep your capture setup fixed. Same window size, same theme (light or dark), same zoom every week, so the screens match from release to release.

If the feature is the movement itself (drag and drop, a live preview, an animation), a still screenshot undersells it. That's a case for a short screen recording.

Where to publish it, and how long for each placement

These are our recommendations, not platform limits, except where a source is linked.

Changelog page. Put the video above the text entry, not instead of it. Readers who scan want the text; search engines and screen readers need it. If you autoplay a loop, remember that WCAG's Pause, Stop, Hide criterion (2.2.2, Level A) asks for a way to pause, stop or hide moving content that starts automatically, lasts more than five seconds and sits alongside other content. A 20-second loop with no controls would fail that. Show the player's controls, or make it click-to-play. An MP4 is usually smaller and sharper than a GIF of the same clip, and a GIF can't carry sound or a captions track.

In-app. Show it to the people who can use the feature (the right plan and role), once, at the point where they'd use it. Don't autoplay with sound.

Email. Don't embed the file. Can I email's video table shows Gmail replacing the video element. The page was last tested in 2019, and its Outlook.com rows updated in 2021 and 2024 say the element is "supported, but the video can not play" under a strict security policy. Don't rely on video playing in email. Use a still from the "one screen" beat with a play icon, linked to the changelog entry.

LinkedIn and X. Assume a silent start and caption everything; the launch video guide cites LinkedIn's own wording on muted autoplay, as of October 2026. In a release thread, post one feature per clip and put the changelog link where your threads usually carry it.

Vertical feeds. Make a 9:16 version only for features a stranger would care about; a new export option is changelog material, not Reels material. Re-lay out each scene for the tall frame rather than cropping the wide one.

A weekly workflow you can keep up

The format only pays off if you make it every release. Book one fixed slot two days before each release and stop choosing styles.

Batch the writing. If you ship two or three video-worthy features in a release, write all the scripts in one sitting. The second and third go faster because the beats repeat.

Lock the look once. Pick the style, colours, voice, opening tag ("New in Rotafox") and end card ("Find it under...") one time, then reuse them; recreating a motion graphics style with your own brand covers choosing that look.

Use one music track. A different track every week makes each video feel like a one-off. A licensed track you own, or a short sting reused at the end, does more for recognition than a better track each time.

Make both sizes in one pass. Decide on 16:9 and 9:16 together at the start, from the same script, so you aren't rebuilding the vertical version on release day. Keep one folder per release with the script, screens and finals.

By hand in a timeline editor, the expensive video isn't the first. It's the fifth: the same title card rebuilt, words re-timed to a voice, two sizes re-exported after a late copy change.

Accessibility checks

Captions. WCAG's Captions (Prerecorded) criterion (1.2.2, Level A) asks for captions on prerecorded audio in synchronized media, and its definition of captions covers non-speech audio too, such as meaningful sound effects and music. For a 20-second voiced feature video that means every spoken line, plus a note for music if it carries meaning. If your on-screen type already says what the voice says, check that it really says all of it.

No flashing. WCAG 2.3.1, Three Flashes or Below Threshold (Level A) says pages should not contain anything that flashes more than three times in any one-second period, unless the flash is below the general and red flash thresholds. Fast cuts between a dark UI and a white one can count as flashes. Avoid strobing "NEW" badges and rapid inversions.

Reading time. Each line should stay still long enough to read twice. The kinetic typography guide covers words per second and hold times with sources; the short version is to plan around two words per second and hold the last frame for two seconds or more.

Contrast and size. Labels over screenshots need a solid plate behind them. Check them on a phone, not a monitor.

The text entry is your text alternative. Keep the written changelog entry directly under the video, saying the same thing. Readers who can't or won't watch get the full message.

Measuring whether it helped

There's no universal good number for a changelog video, and we won't invent one. Compare against your own releases.

• Feature adoption. The share of eligible active accounts that used the feature in the two to four weeks after release. Compare it with releases of similar size you announced in text only. Features differ, so look for a pattern over several releases, not one.
• Click-through from the release email to the changelog entry, with and without the still frame.
• In-app announcement clicks versus dismissals, if your in-app tool reports them.
• Watch behaviour. If your player or host reports where people stop watching, look at the first four seconds. A big drop there means the "old way" beat isn't landing.
• Support tickets about the feature in the first two weeks. A clear "where to find it" beat should mean fewer "where is it?" tickets.
• Social posts. Replies and profile visits show whether prospects care; they say little about adoption.

Note the numbers in the release folder. After six or eight releases you'll know which kinds of features earn a video.

Building it in Oakgen Motion

Oakgen Motion makes code-built motion graphics from a short description: big type, your screens, optional voice and captions, and music, with no AI-generated footage. The full step-by-step (brand from your site, the free storyboard, the price on the Make video button, free draft edits, MP4 in 16:9 and 9:16) is in the launch video guide; what's possible and what isn't is in what AI motion graphics can and can't do in 2026. For a feature video, change these settings:

• Brief and kind. Write the five beats into the brief and set "Kind of video" to Announcement.
• Length. There's no 20-second setting. Pick the 15-second target; the script and voice set the real length.
• Timing is the planner's job. Motion sets scene timing, not you. In Bold kinetic type the opening Slam design lasts at most about 3.5 seconds when unvoiced, shorter than the template's 4-second opener, so expect beats to be shortened. Treat the template timings as a target and judge the storyboard by eye.
• Screens. One or two cropped screenshots. Motion takes images (PNG or JPG), not screen recordings.
• A signature sound. The "new track" option makes music for each video, so upload the same MP3 every week instead. Pick the same look and voice each time too; there are no saved brand kits, so each project starts from your site or the same details entered by hand.

Rendering needs credits, which free accounts don't have; see pricing. Motion doesn't post anywhere: you download the MP4s and publish them yourself.

When a screen recording with voice is better

A 20-second motion graphic announces a feature. It doesn't teach one. Record your screen and talk over it when:

• The feature is a multi-step workflow. Five clicks across three screens won't fit one beat, and cutting it to fit will mislead.
• The movement is the feature. Drag and drop, live previews, real-time collaboration.
• The audience is existing users who need to use it today. They want to see exactly where you click, at normal speed. Pair it with the help article.
• It's a developer feature. A terminal and a code sample beat kinetic type.
• The release is a migration or a breaking change. People want detail and a real face or voice, not energy.

Any capture tool with a microphone will do. You can also do both: the 20-second video in the feed and the email, the recording in the help centre. And if one release grows into a full campaign, turning a product page into a launch kit covers the source brief that keeps every asset saying the same thing.

Two more mistakes

• Three features in one video. Each gets five seconds and none registers. A release thread can hold several one-feature clips.
• Shipping the video a week late. Publish it with the release, or the moment has passed.

Frequently asked questions

How long should a feature announcement video be?

About 20 seconds for a single feature in a changelog, feed or in-app slot. If you need more than a minute to explain it, make a narrated walkthrough instead.

Does every changelog entry need a video?

No. Bug fixes, settings and small tweaks read faster as one line of text and a screenshot. Save video for changes to a task people repeat.

Should a product update video have a voiceover?

It helps when the benefit needs a sentence of reasoning. Either way, put every spoken line on screen, because feed video often starts muted.

Can I put a video directly in a product update email?

Not reliably. Many email clients don't play embedded video, so use a still frame with a play button that links to the changelog entry.

Should I use a GIF or an MP4 on my changelog page?

An MP4 is usually sharper and smaller, and it can carry captions and a pause control. If anything moves for more than five seconds on its own, give people a way to pause it.

How do I know if changelog videos are working?

Compare adoption of the feature in the weeks after release with similar releases you announced in text only, and check click-through from your release email and in-app notice.

When is a screen recording better than a motion graphic?

When the feature is a multi-step workflow, when the movement itself is the feature, or when the audience is existing users who want to see exactly where to click.