Feature launch video examples: 20 videos and their structures

A feature launch video has a narrower job than a product launch video. The audience already knows the product, so it only has to show one new thing, prove it works, and get out. Most do that in well under a minute.

Below are 20 feature launch video examples from the Motion Reference library, grouped by the structure they follow. For each one: what it's best for, how it's built, the moment that does the most work, and one idea you can reuse.

What feature launch videos have in common

As of November 2026, the library holds 32 feature launch videos. Across them:

• They're short. The typical one runs 32 seconds. 15 are under 30 seconds, and all but one are under a minute. The longest, Replit's Parallel Agents, runs 1:17.
• The interface is the star. 27 of the 32 show product UI, and 26 use UI choreography: the interface animated on screen, cursor, clicks and all. Kinetic typography appears in 23.
• One structure dominates. 18 are feature montages. Problem → solution and hook → reveal account for 4 each, walkthroughs and product-first openings for 3 each.
• Music leads, and fast. 20 are music-led and 5 carry a voiceover. 18 are cut at a fast pace.

At a glance

Video	Company	Structure	Length
Claude Artifacts	Anthropic	Feature montage	0:58
Bring Code to the Canvas	Figma	Feature montage	0:35
Shot Coverage	Luma	Feature montage	0:10
Dictation Orb	ElevenLabs	Feature montage	0:25
New Features	Airbnb	Feature montage	0:53
Environments	Factory	Feature montage	0:34
Wabi × OpenTable	Wabi	Problem → solution	0:35
Devin Oncall	Cognition	Problem → solution	0:55
Emails	Base44	Problem → solution	0:30
Framer Agents	Framer	Problem → solution	0:23
Inboxes	Resend	Hook → reveal	0:11
Shaders	pen.dev	Hook → reveal	0:42
Cast	Melius	Hook → reveal	0:38
Parallel Agents	Replit	Hook → reveal	1:17
Seedream 5.5 Retouch	Magnific	Walkthrough	0:22
Video Clipping	X	Walkthrough	0:29
MCP Write Actions	Mercury	Walkthrough	0:29
OmniHuman V2	fal	Product-first	0:16
ROGO Notes	ROGO	Product-first	0:16
Comments	Morphic	Product-first	0:18

Feature montage

Several capabilities, each shown working, back to back. Use it when the release is a bundle, or when one feature has several faces.

Anthropic: Claude Artifacts

• Best for: launching three related features in one video.
• Structure: whiteboards, then sheets, then data storytelling, each in under twenty seconds.
• Technique: cursor-driven typography and several collaborators' cursors on screen at once.
• Standout moment (0:06–0:22): one plain-language prompt produces a project timeline on an infinite canvas.
• Steal this: open each feature with the action that triggers it, so the viewer sees cause, then effect.

Figma: Bring Code to the Canvas

• Best for: a feature with many entry points.
• Structure: sources first (a frame, a web page, Figma MCP, a GitHub repo), then what you can do once the code is on the canvas.
• Technique: multiplayer cursors with name tags, and code blocks that morph into the Figma logo at the end.
• Standout moment (0:16–0:22): a designer changes card values, clicks "Update code layer", and the component re-renders.
• Steal this: list every way in during the first six seconds, then spend the rest of the video on one workflow.

Luma: Shot Coverage

• Best for: a feature you can prove in one comparison.
• Structure: ten seconds. A line of copy, the settings panel, the result, the end card.
• Technique: split screen, with the original take on the left and generated camera angles on the right.
• Standout moment (0:04–0:08): one bar scene shown from performance-led, spatial-led and action-led angles.
• Steal this: if the feature is a before-and-after, put both on screen at once. Split screen does the explaining.

ElevenLabs: Dictation Orb

• Best for: a new way to use features people already know.
• Structure: one input, many uses: dictating a script, generating a voiceover, prompting an image, sharing the result.
• Technique: a morphing fluid orb stands for the voice input and travels through every scene.
• Standout moment (0:06–0:11): spoken words appear in the editor, then become a finished voiceover in one tap.
• Steal this: give the new input a visual form, and carry it through each use case.

Airbnb: New features

• Best for: a seasonal release with many features.
• Structure: five features in 53 seconds: connections, natural-language search, listing details, side-by-side comparison, services.
• Technique: fast cutting to a disco track, with 3D miniatures for the services section.
• Standout moment (0:12–0:22): "Search in your own words" turns a conversational description into filtered listings in Le Marais.
• Steal this: set a long feature list to a strong track and cut on the beat. The rhythm keeps five features from feeling like a list.

Factory: Environments

• Best for: infrastructure for a technical audience.
• Structure: hook, scale, then the pipeline step by step, then monitoring.
• Technique: brutalist type, terminal snippets and 3D wireframe cubes that tile across the screen as the "fleet".
• Standout moment (0:03–0:07): batch requests run in a terminal while sandbox cubes multiply, showing scale without a chart.
• Steal this: show the real command a developer would type, then visualise what it does.

Problem → solution

Start with a moment the viewer has lived, then show the feature ending it. It works best when the problem is one specific situation.

Wabi × OpenTable

• Best for: an integration with a well-known partner.
• Structure: friends planning dinner, the assistant checks calendars, recommends, and books.
• Technique: phone messaging UI composited into live city and lifestyle footage.
• Standout moment (0:06–0:20): the assistant finds a time that suits everyone and shows OpenTable options in the chat.
• Steal this: show the integration inside the moment it's used, not in a settings screen.

Cognition: Devin Oncall

• Best for: a pain your audience knows by heart.
• Structure: the 3 a.m. alert, a rewind to setup, then the alert handled while the engineer sleeps.
• Technique: live action with interface cards tracked into the scene, and typed text cards synced to keyboard sounds.
• Standout moment (0:22–0:36): the footage rewinds from the scramble to the daytime, when the engineer set Devin up.
• Steal this: a rewind turns "before and after" into a story with a turning point.

Base44: Emails

• Best for: a feature aimed at small business owners.
• Structure: first-time buyers who don't return, the feature, a prompt-built campaign, regulars coming back.
• Technique: warm live action in a bakery, cut against clean dashboard UI, and a voiceover.
• Standout moment (0:00–0:06): busy transactions are set against a dashboard showing first-time buyers who never return.
• Steal this: state the problem as a number on a dashboard the viewer would recognise, then show the fix moving it.

Framer: Agents

• Best for: a speed claim.
• Structure: an urgent request, a prompt, a page built and published, the reply sent. Sixteen seconds from ask to done.
• Technique: a real-feeling desktop: a macOS notification, the dock, then the app.
• Standout moment (0:00–0:04): a notification asks for a new campaign page "ASAP".
• Steal this: to prove speed, show the whole task between two messages: the request and the reply.

Hook → reveal

Open with something that makes the viewer ask a question, then answer it with the feature.

Resend: Inboxes

• Best for: a teaser that only needs to plant a name.
• Structure: eleven seconds. The interface rises, the name appears, two lines of positioning.
• Technique: dark-mode UI with a teal glow behind it, and large distressed type scaling in behind the window.
• Standout moment (0:03–0:06): light spreads behind the panel as the wordmark "INBOXES" fades in.
• Steal this: for a teaser, one interface shot, one word and one line of positioning is enough.

pen.dev: Shaders

• Best for: a visual feature where the output is the hook.
• Structure: a rapid shader montage, use cases by component, prompt-to-shader, live controls, then a catalogue.
• Technique: the word "shaders" cycles through glass, chrome, bubble and CRT styles. A chrome pen nib opens and closes the video.
• Standout moment (0:00–0:10): one word, re-rendered in style after style. The range is the hook.
• Steal this: end with a list of everything shown, so viewers can find the effect they liked.

Melius: Cast

• Best for: an AI generation feature where realism is the claim.
• Structure: what looks like a creator reviewing headphones, then the reveal that the creator was generated, then the workflow.
• Technique: user-generated-content styling for the hook, then dark UI with red and orange accents.
• Standout moment (0:00–0:06): the "creator" presents headphones across several angles and desk setups before anything is explained.
• Steal this: let the output pass as real first, then reveal how it was made.

Replit: Parallel Agents

• Best for: a technical feature that needs a model of how it works.
• Structure: the claim, creating tasks, isolated copies, automatic merging, then a comparison with a human team.
• Technique: red and black type on cream, and abstract diagrams for branching and merging.
• Standout moment (0:45–1:02): agents' work merges back into the main app, with conflicts resolved automatically.
• Steal this: when the mechanism matters, give it its own diagram section between the hook and the demo.

Walkthrough

One task, start to finish, at a readable pace. Use it when the steps are the selling point.

Magnific: Seedream 5.5 Retouch

• Best for: an editing feature.
• Structure: one photo, four edits: jacket, hair, trousers, background.
• Technique: brush strokes and prompts over a single image.
• Standout moment (0:10–0:17): one brush stroke replaces a petrol station with a coastal harbour.
• Steal this: keep the same image throughout and stack the edits. The viewer sees each change against the last.

X: Video Clipping

• Best for: a consumer feature people should try today.
• Structure: find a post, trim it, share it, then availability.
• Technique: black and white title cards between phone UI clips.
• Standout moment (0:07–0:13): trim handles set the start and end of a clip inside the player.
• Steal this: end with where it's available (iOS and Android here). It answers "can I use this?"

Mercury: MCP Write Actions

• Best for: an AI feature that touches money or other risk.
• Structure: ask in ChatGPT, see a structured payment card, approve it, done.
• Technique: minimal off-white UI in Mercury's style, with kinetic type framing each step.
• Standout moment (0:10–0:18): the payment waits for a "Slide to approve" confirmation on the phone.
• Steal this: if trust is the question, give the approval step its own beat in the video.

Product-first

No setup. The feature is on screen from the first frame.

fal: OmniHuman V2

• Best for: a generation model that can announce itself.
• Structure: title, demo, "Now on fal". Sixteen seconds.
• Technique: an AI-animated portrait delivers the announcement, framed by fal's pixel particle grid.
• Standout moment (0:02–0:11): a generated man speaks to camera in a misty forest, explaining the model that animates him.
• Steal this: if the output can talk, let it present the launch.

ROGO: Notes

• Best for: a workflow feature for a specialist audience.
• Structure: join, record, stop, process, then values and logo. Sixteen seconds.
• Technique: a "Join meeting" button morphs into a recording pill. Finance dialogue scrolls behind.
• Standout moment (0:06–0:09): status steps run through "Generating Notes", "Executing tasks" and "Updating Intelligence".
• Steal this: use your audience's own language in the background (here, a lender call and EBITDA). It signals who it's for without saying so.

Morphic: Comments

• Best for: a small collaboration feature.
• Structure: add a comment on the canvas, review the thread in the player, then the announcement.
• Technique: animated cursors, click sounds and dark-mode UI.
• Standout moment (0:00–0:08): a cursor draws a box over a video frame and leaves a timestamped note.
• Steal this: for a small feature, show it once, clearly, and put the announcement at the end instead of the start.

How to choose a structure for your feature launch

• Several features, or one feature with several uses: feature montage. Open each section with the action that triggers it.
• A sharp, familiar pain: problem → solution. Make the pain one specific moment.
• A feature that needs curiosity first: hook → reveal. Let the output impress before you name it.
• A task where the steps sell it: walkthrough. Keep one example throughout.
• A small or self-explanatory feature: product-first. Show it in the first frame and keep it under 20 seconds.

FAQ

How long should a feature launch video be?

In the library, the typical feature launch video runs 32 seconds, and 31 of 32 are under a minute. Short works because the audience already knows the product. Go longer only when the feature needs its mechanism explained, as Replit does at 1:17.

What should a feature launch video show?

The interface. 27 of the 32 feature launches in the library show product UI, and 26 animate it on screen. Show the feature being used: the click, the prompt, the result.

Does a feature launch video need a voiceover?

Usually not. 20 of the 32 are music-led, with on-screen type carrying the message, and 5 use a voiceover. A voiceover helps when there's a story to tell, as in Base44's bakery story, or when the product speaks, as in fal's OmniHuman.

---

Every video here is in the Motion Reference library with its full breakdown and timed moments. Search it for your own category, or from your AI agent over MCP.