Make motion graphics videos with Claude from a single prompt: 46 fill-in-the-blank prompts for launch films, explainers, logo reveals and more.
Get the interactive app + PDF: https://aiunfiltered.gumroad.com/l/claude-motion-graphics-prompts

Updated 11 Oct 2026: first version, with render times, file sizes and every bug from four sandbox renders on HyperFrames 0.8.146.

Claude motion graphics prompts are instructions that get Claude to write animation code, usually HTML with GSAP through HyperFrames or React through Remotion, which a headless browser then renders to video one frame at a time. The prompts that work name the duration, resolution, frame rate, exact text, timing per beat, palette, font and how the shot should end.

That's the whole trick. Claude doesn't generate pixels. It writes a program that draws every frame, and good Claude motion graphics prompts are really small creative briefs for that program.

Which means the prompt is only half the story, because a perfectly worded brief can still produce a video with an underline that appears too early, a word that dims when it shouldn't, or a render that dies after capturing every single frame. The other half is what happens when the code meets the renderer, and that part nobody posting showreels on X talks about. So I tested it. Properly.

On 11 October 2026 I took four prompts from this page and had Claude Opus 5.5 build them in a cloud sandbox (2 vCPUs, 8 GB RAM), then rendered each one with HyperFrames 0.8.146 and checked the frames by hand. Every render worked in the end. None on the first try. Zero. The kinetic typography prompt alone took three render passes, because two bugs got past the first attempt and the built-in checker only hinted at one of them.

I'm a software engineer who builds prompt libraries for image and video models and writes the Roo newsletter. Everything below the test results is a copy-paste library of 24 Claude motion graphics prompts. The four I actually rendered are marked as tested. The rest are written to the same pattern, and I'd treat them as strong starting drafts rather than guarantees.

Key facts about Claude motion graphics prompts

Fact

Detail

How it works

Claude writes code, a headless browser renders frames, FFmpeg encodes them

Main frameworks

HyperFrames (HTML + GSAP, Apache 2.0) and Remotion (React)

Install (HyperFrames)

npx skills add heygen-com/hyperframes

Install (Remotion)

npx skills add remotion-dev/skills

Model behind the trend

Claude Opus 5.5, released 22 Sept 2026

Opus 5.5 API price

$4 per million input tokens, $20 per million output tokens

My render speed

6s 1080p clip in about 17 seconds on 2 vCPUs

Transparent overlay sizes

ProRes MOV 11,960 KB vs WebM 116 KB for the same 5s lower third

Remotion licence

Free for individuals and for-profit teams of up to 3 employees

Why everyone started writing Claude motion graphics prompts in late September

Opus 5.5 shipped on 22 September 2026, and within days X filled up with launch films and kinetic type that people said came from a single prompt. Revid's ranking page collects 64 of the most-liked Opus 5.5 motion graphics videos from that launch week. AI × Leaders, a prompt wall updated on 10 October, tracks 84 of these videos but marks only 17 of them as having a complete prompt published.

That last number is the useful one. Seventeen. Most of the viral reels you've seen don't come with the Claude motion graphics prompt that made them, and the ones that do rarely mention how many follow-up messages it took to get there, which is the part you actually need to budget for.

The method itself is plain once you see it, and it explains why Claude motion graphics prompts read more like specs than like image prompts. The model writes an HTML or React project where every visual property is a function of time. A renderer opens that project in headless Chrome, seeks to frame 1, takes a screenshot, seeks to frame 2, and so on, then hands the stack to FFmpeg. HyperFrames' README describes exactly this: a paused GSAP timeline registered on window.__timelines, seeked frame by frame and encoded with FFmpeg.

Because it's code, the result is deterministic. Same input, same frames. Render it twice and you get the same video. Fix one tween and only that moment changes. Nothing else moves. That's the real advantage over text-to-video models. It's also why bugs behave like bugs. Not like bad luck.

What happened when I rendered four Claude motion graphics prompts

Here's every number from the session. Nothing rounded up. Nothing left out. Render time is wall-clock for npx hyperframes render on 2 vCPUs with HyperFrames' low-memory profile, which pinned capture to one worker because the machine had under 8,192 MB.

Test

Output

Passes to final

Render time per pass

Final size

What broke

Kinetic typography, 6s

1920x1080, 30 fps, 180 frames, H.264

3

16.7 to 17.0 s

341 KB

Accent rule visible at full width before its animation; the accent word dimmed with the rest

Revenue count-up with bars, 8s

1080x1920, 30 fps, 240 frames

1 render, 3 checks

20.6 to 21.0 s

391 KB

A tween on bottom failed the checker, which then hid a second layout error

Lower third overlay, 5s

MOV (ProRes 4444 alpha)

1

27.2 s

11,960 KB

Nothing

Same lower third

WebM (VP9 alpha)

1

19.1 s

116 KB

Nothing

Same lower third

MP4 (no alpha)

1

13.3 s

152 KB

The transparent background flattened to solid white

Hindi Diwali title, 3s

1080x1080

1

not timed

not measured

Asked for weight 800, got a regular-weight fallback font

Three findings changed how I write Claude motion graphics prompts now. Here they are.

The first two failures were setup. Not prompting. The fresh blank project loads GSAP from the jsDelivr CDN, my sandbox blocks that domain, and the render captured all 300 frames over 25 seconds before refusing to encode with sub_timeline_script_failure. Then HyperFrames tried to download its own headless Chrome from storage.googleapis.com and failed with ENOTFOUND. Pointing HYPERFRAMES_BROWSER_PATH at an installed Chromium fixed one; copying gsap.min.js into the project fixed the other. If you render on a locked-down work laptop, a corporate network with a strict proxy, a CI runner, or any cloud sandbox that only allows package registries through, you'll almost certainly hit both of these before you ever see your first frame. I did.

The second finding is that npx hyperframes check is good but not sufficient. On the kinetic test, the orange underline sat at full width from the first frame because the runtime overrode my CSS width: 0. The checker reported it only as an info-level "panel out of canvas" note and still printed "Check passed". The other bug, where the accent word "camera." dimmed along with the rest of the line at 4.2 seconds, came from two GSAP tweens fighting over the same opacity. No check flagged it. None. I found it by pulling a frame at 4.8 seconds with FFmpeg and looking at it. Old-fashioned, but it worked.

The third is about transparency. The ProRes MOV is the format editors expect. It's also 103 times bigger than the WebM for the same five seconds. Both carried a real alpha channel when I tested the corner pixel: fully transparent at (10,10), solid at the panel. If your editor accepts WebM with alpha, that's a lot of disk saved. Premiere users should test it on one clip first.

The Claude motion graphics prompt formula that survived testing

Every one of the Claude motion graphics prompts below follows this order. Duration and canvas go first because they decide everything else: how many frames the renderer captures, where the safe areas sit, how big the type needs to be, and how much the model has to fit into each beat. Exit behavior goes last because it's the part models most often forget.

Make a [duration]-second [type of motion graphic] in [HyperFrames / Remotion],
[width]x[height] at [fps] fps.
Text, exactly: "[copy]".
Beats: [what happens at 0.0s], [at 0.4s], [at 1.2s] ...
Style: [background hex], [text hex], one accent [hex] on [element], [font + weight].
Motion: animate transforms and opacity only, [ease names], no layout-property tweens.
End: [hold / exit] for the last [n] seconds.
Bundle every script and font locally, no CDN links.
Before rendering, extract frames at [times] and show me them.

The last two lines come straight from my failures. "Bundle every script locally" prevents the CDN block. "Transforms and opacity only" prevents the bottom tween that failed the checker. "Extract frames and show me" catches the bugs no linter sees. Each costs a few words. Each saves a render pass.

Why does my Claude motion graphic look wrong? A debugger

These rows come from my own renders plus the failure modes the source guides mention. When Claude motion graphics prompts go wrong, it's usually one of these ten. Find the symptom, apply the fix.

Symptom

Likely cause

Fix

Render fails with sub_timeline_script_failure

GSAP or another script loaded from a CDN that's blocked

Install the package locally and reference the file, not the CDN

"Chrome not found" / ENOTFOUND storage.googleapis.com

HyperFrames can't download its headless shell

Set HYPERFRAMES_BROWSER_PATH to an installed Chrome or Chromium

An element shows up fully drawn before it animates

CSS start state overridden; no explicit start set on the timeline

Set the starting value with gsap.set() before building the timeline

One element ignores a later animation

Two tweens on the same property overlap

Exclude that element from the group tween instead of re-setting it

Motion stutters on slow eases

Tweening layout properties like bottom, top, left

Animate x, y, scale and opacity instead

Checker says layout and contrast pass with "0/0 text checks"

A lint error stopped the browser stage, so nothing was measured

Fix lint errors first, then rerun the check

Hindi or other non-Latin text looks thin

Fallback system font lacks the bold weight

Bundle a webfont with the weights you need

Overlay sits on a solid white or black box

Rendered as MP4, which has no alpha (mine came out white)

Render --format mov or --format webm

Render is slow or crashes

Low memory forces one capture worker

Close other apps, or render on a machine with more than 8 GB

Every video looks like the same showreel

Prompt gives mood words but no beats or palette

Write timed beats and hex colors; ban the effects you're tired of

HyperFrames or Remotion for Claude motion graphics prompts?

For most Claude motion graphics prompts I'd pick HyperFrames. Use it if you think in HTML and CSS, want transparent overlays without fuss, or work at a company of more than three people and don't want a licence conversation. Use Remotion if you already write React, want its Studio for scrubbing, or need its map and caption skills.

HyperFrames

Remotion

Who makes it

HeyGen, open-sourced 17 Apr 2026

Remotion

Licence

Apache 2.0

Free for individuals, non-profits and for-profit teams up to 3 employees; company licence above that

What Claude writes

One HTML file with data-* timing attributes and a GSAP timeline

React components

Skill install

npx skills add heygen-com/hyperframes

npx skills add remotion-dev/skills

Requirements

Node 22+, FFmpeg

Node; see Remotion's docs for its setup

Transparent output

--format mov (ProRes 4444) or --format webm

Not tested here; check Remotion's docs

What I tested

All four renders on this page

Not tested here

The licence row matters more than it looks. A lot more. The Remotion licence is free for a for-profit organisation with up to three employees. A four-person agency making client videos with it needs the paid company licence. HyperFrames' Apache 2.0 licence has no such line.

I didn't benchmark Remotion for this page, so I won't claim it's slower or faster. Sabrina Ramonov's five Remotion prompts are the most detailed set I found for that framework, and they're worth reading if you're on React.

Kinetic typography prompts

Kinetic type is the easiest place to start with Claude motion graphics prompts because there are no assets to source. It's also where small timing mistakes show most, so write beats in seconds, not vibes.

Kinetic typography headline (tested)

Words slam in one at a time, accent on the last word, underline draws in.

Make a 6-second kinetic typography motion graphic in HyperFrames, 1920x1080 at 30 fps.
Text, exactly: "Code is the new camera."
Beats: each word rises in from below and settles, one word every 0.4s starting at 0.3s.
At 2.15s give "camera." a quick 6% scale pop. At 2.4s draw a 10px accent underline left to right in 0.6s.
At 4.2s dim every word except "camera." to 35% opacity. Hold to the end.
Style: background #0b0b0c, text #f2efe8, accent #ff5a1f on "camera." and the underline, heavy grotesk at 168px.
Motion: transforms and opacity only, power4.out on entries, expo.out on the underline.
Bundle GSAP locally, no CDN. Set every starting value with gsap.set before the timeline.
Before rendering, extract frames at 1s, 3s and 5s and show me them.

Best for: HyperFrames 0.8.146 with Claude Opus 5.5 · Tested: Oct 2026, 3 passes, 17 s render · 1920x1080, 30 fps

Word-by-word quote reveal

For pull quotes and podcast clips.

Make an 8-second quote reveal in HyperFrames, 1080x1350 at 30 fps.
Text, exactly: "[your quote]" and the attribution "[name, role]".
Beats: words fade up from 20% opacity to 100% in reading order, 0.18s apart, starting at 0.4s. Attribution slides in from the left 0.5s after the last word.
Style: background #f4f1ea, text #1b1b1b, attribution #8a6d3b, a serif display face for the quote, sans for attribution.
Motion: opacity and y only, gentle power2.out, no bounce.
End: hold the full quote for 2s.
Bundle fonts and scripts locally.

Best for: HyperFrames with Claude Opus 5.5 or Sonnet 5.5 · 4:5 for Instagram and LinkedIn

Big number title card

One stat, full screen.

Make a 4-second title card in HyperFrames, 1080x1920 at 30 fps.
Text: "[number]" on line one, "[label]" on line two.
Beats: the number counts up from 0 over 1.5s with power2.out, the label fades in at 1.4s, a thin accent line grows under it at 1.8s.
Style: background #111, number #fff at 260px tabular figures, label #9aa3ad, accent #3ddc97.
Format the number with Indian digit grouping if it's in rupees.
End: hold for 1.5s.

Best for: HyperFrames or Remotion · 9:16 for Shorts and Reels

Data and stat motion graphics prompts

Charts are where code-generated video beats every text-to-video model, because the bars come out exactly as tall as the data says. Exactly. Supply the numbers in the prompt. Never let the model invent them. Data-driven Claude motion graphics prompts should treat your numbers as fixed input, the same way you'd hand a designer a spreadsheet and expect the chart to match it to the last digit.

Revenue count-up with bar chart (tested)

Vertical reel: a rupee figure counts up, then four quarterly bars grow in sequence.

Make an 8-second vertical data motion graphic in HyperFrames, 1080x1920 at 30 fps.
Label "FY26 revenue", then a number counting from ₹0 to ₹4,200 over 1.8s using en-IN digit grouping, then the line "crore, up 38% year on year".
From 2.6s, four bars for Q1 to Q4 with values 820, 960, 1,080, 1,340 grow one after another, 0.45s apart, each value label fading in above its bar. At 5.2s turn the Q4 bar gold.
Style: background #0e1116, text #eef1f5, bars #3ddc97, highlight #f5c84c, a clean sans.
Motion: transforms and opacity only for labels. Mark axis labels that sit below the chart as intentional overflow.
Small footer: "Sample data for a demo reel".
Bundle GSAP locally.

Best for: HyperFrames 0.8.146 with Claude Opus 5.5 · Tested: Oct 2026, 21 s render, 391 KB · 1080x1920

Line chart that draws itself

For growth stories.

Make a 10-second line chart animation in HyperFrames, 1920x1080 at 30 fps.
Data (month, value): [paste 12 rows].
Beats: axes fade in by 0.5s, the line draws left to right over 4s with an SVG stroke-dashoffset tween, a dot follows the tip, the final value pops in a label at the end of the line.
Style: background #0d1117, line #58a6ff 6px, grid #21262d, labels #8b949e.
End: hold 2s, then fade everything except the final value.
Use the exact data values; don't smooth or round them.

Best for: HyperFrames or Remotion with Claude Opus 5.5 · 16:9

Before and after comparison bars

The classic "we cut load time" slide.

Make a 6-second comparison graphic in HyperFrames, 1080x1080 at 30 fps.
Left bar labelled "Before" at [value + unit], right bar "After" at [value + unit].
Beats: both bars grow together for 1s, then the "After" bar keeps going or shrinks to its real value, then a delta badge "[−62%]" stamps in at 2.5s.
Style: background #fafafa, before #c9ced6, after #ff5a1f, text #111.
Scale both bars to the same axis. Don't exaggerate the difference.

Best for: HyperFrames with Claude Sonnet 5.5 · 1:1

Logo sting and lower third prompts

Overlays are where format matters most in Claude motion graphics prompts. Ask for MOV or WebM up front, or you'll get an MP4 where the transparent background is flattened to a solid color. Mine came out white.

Name and title lower third (tested)

A panel wipes in from the left, name and role follow, everything exits after 4 seconds.

Make a 5-second transparent lower third in HyperFrames, 1920x1080 at 30 fps.
Name: "[Full Name]". Role: "[ROLE · COMPANY]".
Beats: a dark rounded panel scales in from the left edge over 0.55s at 0.2s with expo.out, name fades and slides in at 0.45s, role at 0.6s. At 4.0s text slides out, panel collapses at 4.2s.
Style: panel #111418 with a 12px accent bar #ff5a1f on its left edge, name #f4f2ec 56px extra bold, role #a9b0bb 30px tracked caps.
Place it in the bottom-left safe area. Transparent background.
Render as MOV for Premiere and WebM for the web.

Best for: HyperFrames 0.8.146 with Claude Opus 5.5 · Tested: Oct 2026, MOV 27 s / WebM 19 s · transparent

Minimal logo reveal

Needs a clean SVG logo.

Make a 4-second logo reveal in HyperFrames, 1920x1080 at 30 fps, using the SVG at ./logo.svg.
Beats: the logo's outline strokes draw on over 1.2s, the fill fades in at 1.1s, the wordmark slides up underneath at 1.5s, a soft glow pulses once at 2.2s.
Style: background #0a0a0a, use the logo's own colors, no extra gradients.
End: hold 1.2s. Also export a transparent MOV version.
Don't redraw or restyle the logo. Animate the file as supplied.

Best for: HyperFrames with Claude Opus 5.5 · 16:9 plus transparent MOV

Subscribe and follow call-to-action

An end card for Shorts and Reels.

Make a 3-second call-to-action overlay in HyperFrames, 1080x1920 at 30 fps, transparent background.
Text: "Follow for part 2" with a small arrow.
Beats: pill-shaped button pops in with back.out(1.6) at 0.2s, text types on at 0.5s, the arrow nudges right twice.
Style: button #ffffff, text #111111, arrow #ff5a1f.
Keep it inside the bottom third, clear of the platform's caption area.
Render as WebM with alpha.

Best for: HyperFrames · 9:16 transparent WebM

Product launch and SaaS prompts

These are the Claude motion graphics prompts behind most of the launch-week showreels. Give Claude real assets (screenshots, logo, brand colors) or it'll invent a UI that doesn't match your product.

Website-to-launch film

Your own site, recut as a launch film.

Make a 20-second product launch video in HyperFrames, 1920x1080 at 30 fps, for [URL].
First capture the site and pull the real logo, brand colors, headline and two product screenshots. Show me what you captured before building.
Scenes: 0 to 3s hook line "[problem in 6 words]"; 3 to 8s product name and logo; 8 to 15s the two screenshots with a simulated cursor clicking the main action; 15 to 20s three feature callouts and the URL.
Style: use the captured brand palette and fonts only.
Motion: smooth camera-style pans on screenshots, transforms only.
Wait for my approval of a frame at each scene start before rendering the full video.

Best for: HyperFrames /product-launch-video workflow with Claude Opus 5.5 · 16:9

Continuous UI morph loop

A website hero loop.

Make a 6-second looping UI animation in HyperFrames, 1600x1000 at 60 fps.
Three app cards: [card A content], [card B content], [card C content].
Beats: card A morphs into B at 1.5s, B into C at 3.5s, C back into A at 5.5s, so frame 360 matches frame 1.
Style: background #f6f7f9, cards #ffffff with soft shadow, accent #4f46e5.
Motion: shared-element morph on size and position using transforms, no fades to black.
Export as WebM for a website background and confirm the first and last frames match.

Best for: HyperFrames with Claude Opus 5.5 · 60 fps, loop

Feature callout with zoom

One feature, one punch-in.

Make a 7-second feature highlight in HyperFrames, 1080x1350 at 30 fps, using ./screenshot.png.
Beats: screenshot appears at full size, at 1.2s the frame punches in 2.2x on the [element] over 0.8s, a label "[feature name]" pins next to it at 2.2s, at 5s ease back out.
Style: background #0f172a, label pill #22c55e with dark text.
Keep the screenshot sharp: render at 2x device scale if needed.

Best for: HyperFrames keyframes with Claude Sonnet 5.5 · 4:5

Explainer prompts

Explainers are longer, so these Claude motion graphics prompts ask for a script and storyboard first. Approving five scene descriptions costs a minute. Maybe two. Re-rendering a 60-second video because scene 3 is wrong costs much more.

Faceless explainer from a topic

Text in, explainer out.

Make a 45-second faceless explainer in HyperFrames, 1080x1920 at 30 fps, about "[topic]".
Step 1: write a 5-scene script with on-screen text of 12 words or fewer per scene and show it to me.
Step 2 after approval: build each scene as its own sub-composition with one diagram or icon animation per scene.
Style: background #101418, text #eef2f6, one accent #f59e0b, large readable type, minimum 36px body.
Motion: one idea moving at a time, 12-frame transitions between scenes.
End with a summary card listing the 3 key points.

Best for: HyperFrames /faceless-explainer with Claude Opus 5.5 · 9:16

Code change explainer from a pull request

For developer launches.

Make a 40-second explainer in HyperFrames, 1920x1080 at 30 fps, for the GitHub pull request [owner/repo#N].
Read the PR description and diff. Scenes: what problem it fixes, the before code, the after code with the changed lines highlighted, the result in one sentence.
Style: dark editor theme, monospace at 34px minimum, highlight #fbbf24 at 25% opacity behind changed lines.
Never show secrets, tokens or .env contents even if they appear in the diff.

Best for: HyperFrames /pr-to-video with Claude Opus 5.5 · 16:9

Route map animation

A route drawn across a map.

Make a 12-second route animation, 1920x1080 at 30 fps, from [city A] to [city B] via [city C].
Beats: map fades in, the route line draws over 6s, a marker pulses at each stop with its name, distance total appears at the end.
Style: muted map #e9e5dc, route #d9480f 8px, labels #222.
Use real coordinates for the cities and say which map data source you used.

Best for: Remotion /remotion-maps or HyperFrames · 16:9

Vertical social reel prompts

Social reels live or die in the first second. So the hook text goes on screen at frame 1, never after an intro, and vertical Claude motion graphics prompts should say where the platform buttons sit.

Hook text reel

No footage needed.

Make a 9-second vertical text reel in HyperFrames, 1080x1920 at 30 fps.
Lines: "[hook, visible from frame 1]", "[line 2]", "[line 3]".
Beats: hook is on screen at frame 1 and shakes once at 0.3s, line 2 replaces it at 3s with a vertical whip, line 3 at 6s.
Style: background #ffde59, text #111 extra bold 110px, centered in the middle 60% of the frame.
Keep all text out of the top 250px and bottom 400px where platform buttons sit.

Best for: HyperFrames with Claude Sonnet 5.5 · 9:16

Real quotes only.

Make a 15-second testimonial reel in HyperFrames, 1080x1920 at 30 fps.
Quotes, exactly as written: [quote 1 + name], [quote 2 + name], [quote 3 + name].
Beats: each card slides up, five stars fill left to right, the quote holds 3.5s, card slides out.
Style: background #f8f5f0, cards #ffffff, stars #f5b301, text #1c1c1c.
Use only the quotes I've given. Don't paraphrase or invent reviews.

Best for: HyperFrames or Remotion · 9:16

Hindi and Indian festival motion graphics prompts

None of the guides I read had a single Hindi or Indian festival example, which is odd for a format so many Indian D2C brands and creators use every Diwali. The test result matters for Hindi Claude motion graphics prompts: my Hindi title rendered correctly through a fallback font, but the weight-800 heading came out regular because that font had no bold. Bundle a Devanagari webfont with real weights and say so in the prompt.

Diwali sale title card (tested)

Hindi greeting, English offer.

Make a 3-second square festival title card in HyperFrames, 1080x1080 at 30 fps.
Line 1 in Hindi, exactly: "शुभ दीपावली". Line 2: "Diwali sale · 40% off".
Beats: line 1 rises and fades in at 0.2s over 0.6s, line 2 follows at 0.6s, a few warm light particles drift upward.
Style: background #1a0f0a, line 1 #ffcf6b, line 2 #f3e6d8.
Bundle a Devanagari webfont such as Noto Sans Devanagari or Mukta in weights 400 and 800 locally, and use it for line 1.

Best for: HyperFrames 0.8.146 with Claude Opus 5.5 · Tested: Oct 2026 (font fallback found) · 1:1

Hindi kinetic quote

Word by word, in Hindi.

Make a 7-second Hindi kinetic typography reel in HyperFrames, 1080x1920 at 30 fps.
Text, exactly: "[Hindi line]".
Reveal whole words, never individual characters, so matras and conjuncts stay joined. One word every 0.35s.
Style: background #0f0f12, text #ffffff, accent #ff8a00 on the last word, Devanagari webfont bundled locally in weight 700.
End: hold 2s.

Best for: HyperFrames with Claude Opus 5.5 · 9:16

Cricket score lower third

A generic match-score bug.

Make a 6-second transparent score overlay in HyperFrames, 1920x1080 at 30 fps.
Teams: "[TEAM A]" and "[TEAM B]". Score: "[187/4]" in "[18.2]" overs. Target: "[205]".
Beats: the bar slides up from the bottom edge, team names and score fade in, the run count ticks from the previous ball's score to the current one, required run rate appears at 2s.
Style: navy #0b1d3a, white text, accent #ffcc00. No league logos or team crests.
Render as WebM with alpha.

Best for: HyperFrames · transparent WebM

Festive offer countdown

For a sale ending tonight.

Make a 5-second countdown reel in HyperFrames, 1080x1920 at 30 fps.
Text: "Sale ends in" then a timer showing "[05:59:59]" ticking down one second per real second, then "[Shop now · link in bio]".
Style: background gradient #ff3d7f to #ffb800, text #ffffff, bold sans.
Keep the timer digits tabular so they don't jump as they change.

Best for: HyperFrames with Claude Sonnet 5.5 · 9:16

Follow-up prompts that fix a motion graphic

The first render is a draft. Always. These are the messages I'd send after it, and they're the reason my four tests ended up clean. Think of them as the second half of any Claude motion graphics prompt.

Frame review before the final render

Before the final render, extract frames at [0.5s, 1.5s, 3s, end minus 0.5s] and show them to me. For each frame, tell me what should be on screen at that moment according to my beats, and point out anything that doesn't match.

Best for: any framework · catches start-state and overlap bugs

Render QA pass

Run the framework's check command and fix every error and warning before rendering. If the check stops early because of a lint error, fix that and run the check again, because the layout and contrast stages won't have run.

Best for: HyperFrames npx hyperframes check

Timing notes in plain words

Animation notes: the entrance of [element] feels slow, cut it to 0.3s. Everything after 2s should happen 0.2s earlier. The exit at the end is too abrupt; ease out over 0.5s instead. Change nothing else.

Best for: any framework · "change nothing else" keeps the rest of the timeline intact

How much do Claude motion graphics prompts cost?

Running Claude motion graphics prompts through the API means paying per token. Opus 5.5 costs $4 per million input tokens and $20 per million output tokens, according to Anthropic's pricing page. Sonnet 5.5 is half that at $2 and $10.

The finished code is cheap. Really cheap. My kinetic typography composition was 2,056 characters, roughly 514 output tokens, which works out to about one cent at the Opus 5.5 output price. The revenue chart was 3,906 characters, about two cents. Those are estimates from character counts, not metered usage.

What actually costs money is everything around the code: Claude reading skill files, running checks, reading error logs and making fix passes. I didn't meter that for this session. So no made-up number. Expect it to dwarf the cost of the final file. Every extra pass adds more. The frame-review prompt above is the cheapest way I know to cut passes.

On a Claude subscription you pay through usage limits instead of per token. The five-hour limits on Pro, Max and Team were raised with the Opus 5.5 release, according to Thurrott's launch coverage.

When not to use Claude for motion graphics

Skip Claude motion graphics prompts for anything that needs real people, acting, animals or organic physics. Code draws shapes, type, charts and UI beautifully, and it'll keep drawing them identically every time you render, which is exactly what you want for a brand system and exactly what you don't get from most text-to-video tools. It doesn't draw a convincing person walking through rain. Use a dedicated video model for that and bring the footage into HyperFrames for titles and overlays.

Skip it too if you need one graphic a year and already own After Effects. The setup (Node 22, FFmpeg, a browser, a skill install) pays off on the tenth video, not the first. Be honest about your volume.

Frequently asked questions about Claude motion graphics prompts

Can Claude make videos directly?

No. With Claude motion graphics prompts, Claude writes code that a renderer such as HyperFrames or Remotion turns into video. The model plans and programs every frame, and headless Chrome plus FFmpeg produce the actual MP4, WebM or MOV file.

What is the best framework for Claude motion graphics prompts?

For most Claude motion graphics prompts, HyperFrames if you prefer HTML and CSS or need transparent overlays, Remotion if you work in React. HyperFrames is Apache 2.0. Remotion is free for individuals and teams of up to three employees, with a paid company licence above that.

How long does a render take?

Rendering is the fast part of Claude motion graphics prompts. In my test a 6-second 1080p clip at 30 fps rendered in about 17 seconds on a 2-vCPU, 8 GB cloud machine. An 8-second vertical chart took about 21 seconds. Faster machines with more memory can use more capture workers.

Why did my render fail after capturing every frame?

Most likely a script failed to load, often GSAP from a blocked CDN, which is why my Claude motion graphics prompts all end with a line about bundling scripts locally. HyperFrames reports it as sub_timeline_script_failure and refuses to encode. Install the library locally, reference the local file and render again.

Can I make transparent overlays for Premiere?

Yes. Ask for it in the Claude motion graphics prompt, then render with --format mov for ProRes 4444 with alpha, or --format webm for VP9 with alpha. In my test the same 5-second lower third was 11,960 KB as MOV and 116 KB as WebM, both fully transparent.

Do Claude motion graphics prompts work in Hindi?

Yes, Hindi Claude motion graphics prompts work, but bundle a Devanagari font. Without one, Chromium falls back to a system font that may lack bold weights. Reveal whole words, not characters, so matras stay attached.

Opus 5.5 or Sonnet 5.5?

Opus 5.5 for multi-scene launch films. Sonnet 5.5 for short single-beat graphics, at half the price.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Article",
      "headline": "Claude Motion Graphics Prompts I Rendered, Broke and Fixed",
      "description": "24 Claude motion graphics prompts, four rendered in HyperFrames with measured render times, file sizes, bugs and fixes.",
      "image": "https://YOURDOMAIN/wp-content/uploads/claude-motion-graphics-prompts-test-renders.webp",
      "datePublished": "2026-10-11",
      "dateModified": "2026-10-11",
      "author": {
        "@type": "Person",
        "name": "Ved Vyas",
        "url": "https://YOURDOMAIN/author/ved-vyas/",
        "sameAs": ["https://x.com/KangarooHere", "https://roo.beehiiv.com"]
      },
      "about": [{"@type": "Thing", "name": "Claude motion graphics prompts"}, {"@type": "Thing", "name": "Code-generated video"}],
      "mentions": [
        {"@type": "SoftwareApplication", "name": "Claude Opus 5.5"},
        {"@type": "SoftwareApplication", "name": "HyperFrames"},
        {"@type": "SoftwareApplication", "name": "Remotion"},
        {"@type": "SoftwareApplication", "name": "GSAP"},
        {"@type": "SoftwareApplication", "name": "FFmpeg"}
      ]
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {"@type": "Question", "name": "Can Claude make videos directly?", "acceptedAnswer": {"@type": "Answer", "text": "No. With Claude motion graphics prompts, Claude writes code that a renderer such as HyperFrames or Remotion turns into video. The model plans and programs every frame, and headless Chrome plus FFmpeg produce the actual MP4, WebM or MOV file."}},
        {"@type": "Question", "name": "What is the best framework for Claude motion graphics prompts?", "acceptedAnswer": {"@type": "Answer", "text": "For most Claude motion graphics prompts, HyperFrames if you prefer HTML and CSS or need transparent overlays, Remotion if you work in React. HyperFrames is Apache 2.0. Remotion is free for individuals and teams of up to three employees, with a paid company licence above that."}},
        {"@type": "Question", "name": "How long does a render take?", "acceptedAnswer": {"@type": "Answer", "text": "Rendering is the fast part of Claude motion graphics prompts. In my test a 6-second 1080p clip at 30 fps rendered in about 17 seconds on a 2-vCPU, 8 GB cloud machine. An 8-second vertical chart took about 21 seconds. Faster machines with more memory can use more capture workers."}},
        {"@type": "Question", "name": "Why did my render fail after capturing every frame?", "acceptedAnswer": {"@type": "Answer", "text": "Most likely a script failed to load, often GSAP from a blocked CDN, which is why my Claude motion graphics prompts all end with a line about bundling scripts locally. HyperFrames reports it as sub_timeline_script_failure and refuses to encode. Install the library locally, reference the local file and render again."}},
        {"@type": "Question", "name": "Can I make transparent overlays for Premiere?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Ask for it in the Claude motion graphics prompt, then render with --format mov for ProRes 4444 with alpha, or --format webm for VP9 with alpha. In my test the same 5-second lower third was 11,960 KB as MOV and 116 KB as WebM, both fully transparent."}},
        {"@type": "Question", "name": "Do Claude motion graphics prompts work in Hindi?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, Hindi Claude motion graphics prompts work, but bundle a Devanagari font. Without one, Chromium falls back to a system font that may lack bold weights. Reveal whole words, not characters, so matras stay attached."}},
        {"@type": "Question", "name": "Opus 5.5 or Sonnet 5.5?", "acceptedAnswer": {"@type": "Answer", "text": "Opus 5.5 for multi-scene launch films. Sonnet 5.5 for short single-beat graphics, at half the price."}}
      ]
    }
  ]
}
</script>