Build a video prompt in under a minute, or copy one of our templates. Each one includes the details most creator prompts leave out: aspect ratio, a ban on the AI template look, self-review and a clean MP4 export.
Updated •14 templates•496 prompts analysed
Prompt builder
Seven quick choices on the left. The prompt on the right updates as you go. Paste it into Claude Code or claude.ai with Opus 5.5.
Make a launch video for [Inkwell, a note app that turns voice memos into tasks]. Length: 15 seconds.
Structure, one beat each:
- Hook: the problem in one line
- The product appears
- Three real features, one per beat
- Proof: a number or a quote
- Name, URL and call to action
Something must happen in every shot, and each thing the viewer has to read gets enough time to read it.
Pick one strong visual style that suits this and tell me which one in a single line.
I will supply a licensed music track at 120 BPM. Put every cut and key hit on the beat grid. ffmpeg will mux the track in, so do not generate audio.
Format: 1920x1080 (16:9), 60fps. Keep text inside a 5% safe margin.
Build it as one self-contained HTML file. Every frame must be a pure function of time: expose window.renderAt(t), seed all randomness, no timers, counters or CSS transitions.
Avoid: particle bursts, lens flares, neon glow, RGB split, glitch effects, bouncy elastic easing on everything, gradients as decoration, text that repeats what the picture already shows, and dead time where nothing moves.
Before the final render, make a contact sheet with one frame per second, look at it, and fix overlapping text, unreadable labels and dead time.
Then write a Playwright + ffmpeg script that steps time frame by frame and exports an MP4.
Start by showing me the storyboard with timestamps. Wait for my OK before writing code.
How often each element appears in 496 full prompts that creators shared alongside their Opus 5.5 videos. The rare ones at the bottom are where your video can beat theirs.
Duration
44%
Sets the number of beats. 15s is the most common ask, then 30s and 20s.
Music, sound or narration
33%
Without it Claude makes a silent piece or synthesizes weak music.
Camera language
23%
"Slow push in", "whip pan", "cut on action" give it real moves to perform.
Things to avoid
19%
The fastest way to lose the generic AI look.
Style reference
19%
One named style beats five adjectives.
Export instructions
17%
Without them you get a page to watch, not a file.
Scene-by-scene beats
14%
Controls pacing. Most bad clips are too fast in the middle.
Frame rate
13%
60 for UI and motion graphics, 24 for drawn or filmic.
Aspect ratio
8%
Decides layout. The most skipped spec with the biggest effect.
Self-review of frames
7%
Rare in prompts, common in the best results.
Prompt templates
Replace the [brackets] with your details.
15-second SaaS launch spot
Product launch15s16:9
Make a 15-second launch video for [product], which [one sentence on what it does].
Audience: [who it is for]. Real features to show, do not invent others: [feature 1], [feature 2], [feature 3].
Structure, one beat each: the problem in five words, the product UI appears, the three features, the URL [url].
Build the UI from HTML components in the product's own colours ([hex codes]), not screenshots.
1920x1080, 60fps. Every frame must be a pure function of time, render(t).
Avoid particle bursts, lens flares, glow and bouncy easing.
Show me the storyboard with timestamps first, then build a single HTML file.
The showreel one-liner, done properly
Showreel / surprise me20s16:9
Make a 20-second motion design piece that shows what an excellent motion designer you are, themed around [topic].
Rules: at least six distinct visual ideas, each on a beat of a 120 BPM grid. One slower moment around second 12 so it can breathe. End on a clean title card that says [text].
No particle bursts, lens flares, glow or RGB split. Flat colour, strong typography.
Single HTML file, 1920x1080, 60fps, every frame computed from t so it can be rendered offline.
How-it-works explainer
Explainer45s16:9
Make a 45-second explainer of how [concept] works, for [audience].
First, list the 4 to 6 things a viewer must understand, in order. Give each one its own time slot of at least 5 seconds. Only one new idea on screen at a time.
Visual style: clean diagrams that build piece by piece, labels appear only when the part they name appears.
Write a voiceover script timed per scene, then the animation.
1920x1080, 30fps, single HTML file, render(t) is deterministic. Double-check every fact and number. If you are unsure, say so instead of drawing it.
Logo sting, 6 seconds
Logo reveal6s16:9
Here is my logo as SVG: [paste SVG]. Make a 6-second logo reveal.
Take the logo apart into its real shapes and animate them assembling. Do not redraw or change the mark. The wordmark resolves last, then hold the final frame for a full second.
Motion: confident and quick in, soft settle. One accent colour [hex] on white.
1920x1080 and 1080x1080 versions, 60fps, single HTML file per version with render(t).
Animated chart from real numbers
Data story20s1:1
Turn this data into a 20-second animated data story: [paste CSV or table].
Lead with the single most surprising number, big. Then build the chart one series at a time. Add one annotation that says why the change matters. End with the source line "[source]".
Use only the numbers given. Axis labels must be readable on a phone.
1080x1080, 60fps, single HTML file, every frame from t. Render a contact sheet of 6 frames and check label overlaps before you finish.
Vertical feature announcement
Product launch15s9:16
Make a 15-second vertical video (1080x1920) announcing [feature] in [product].
The first second must make sense with the sound off: a big, short headline. Keep everything inside the middle 80% of the frame so platform buttons do not cover it.
Show the feature as a real UI interaction: cursor or finger, tap, the result. End on "[call to action]".
30fps, single HTML file, deterministic render(t). No particle effects, no glow.
Lyric video synced to a track
Lyric / kinetic type60s16:9
Make a kinetic typography lyric video. Track: [song], [BPM] BPM. Here are the lyrics with start times in seconds: [paste lines with timestamps].
Each phrase gets its own layout. Emphasis words get scale or colour, never both. Words enter on beats, not at random.
Do not generate audio. I will mux the track with ffmpeg.
1920x1080, 60fps, single HTML file, every frame from t. Show me the layout plan per phrase before coding.
App walkthrough from your real UI
App / UI walkthrough30s16:9
Read the components in [path to UI code or screenshots] and make a 30-second walkthrough of [user flow].
Rebuild the screens in HTML with the real colours, fonts and copy. Animate a cursor through the flow: [step 1], [step 2], [step 3]. Zoom in on each detail that matters, then pull back.
Pace: one action per 3 to 4 seconds, so a viewer can follow.
1920x1080, 60fps, render(t) deterministic, no fake features.
3D world flythrough
3D world20s16:9
Build a 3D scene of [place or world] in Three.js and make a 20-second camera flythrough.
Shots: wide establishing shot, slow push into [main area], one moment of life ([what moves]), pull out to reveal everything.
Everything is procedural, no external models. Fixed random seed. Objects sit on the ground, never float.
1920x1080, 60fps. Expose render(t) that sets the camera and all animation from t. Screenshot four frames and check them before delivery.
Hand-drawn character short
Character short15s16:9
Make a 15-second animated short of [character] trying to [goal].
Story: wants it, tries, fails in a funny way, surprise solution, payoff. Something happens in every shot.
Look: hand-painted brush strokes on paper texture, no plain vector shapes, no text on screen. Faces act, not just bodies.
Timing: list what the viewer must notice in each shot and give each moment enough frames to read.
24fps, 1920x1080, p5.js, every frame a function of t. Storyboard first.
Research paper in 60 seconds
Explainer60s16:9
Read this paper: [link or PDF]. Make a 60-second explainer for engineers who have not read it.
Cover: the problem, the key idea as one diagram, how it works in three steps, the main result with the real number, one limitation.
Write the narration first, about 150 words, and time each scene to it.
Style: clean whiteboard diagrams that build up, math only where it helps.
1920x1080, 30fps, deterministic render(t). Do not state any number that is not in the paper.
GitHub repo promo
Product launch20s16:9
Read this repository's README and code: [repo]. Make a 20-second promo video for it.
Show: the one-line pitch, the install command typed into a terminal, the result it produces, the star count as [number]. Use a real terminal look and the project's own name and colours.
No made-up features or testimonials.
1920x1080, 60fps, single HTML file with render(t), then write a Playwright + ffmpeg script that exports an MP4.
Seamless background loop
Showreel / surprise me10s16:9
Make a 10-second seamless loop to use as a website hero background.
The last frame must match the first exactly: drive all motion from sin and cos of (2*PI*t / 10).
Calm, slow, low contrast so text can sit on top. Colours: [palette].
GLSL fragment shader or Canvas, 1920x1080, 30fps, render(t) deterministic.
Changelog / release notes video
App / UI walkthrough30s16:9
Turn these release notes into a 30-second video: [paste notes].
Pick the 3 changes a user would care about most. For each one show a before and after in the UI, 6 to 8 seconds each. Open with the version number, close with how to update.
Rebuild UI in HTML with our colours [hex codes]. 1920x1080, 60fps, deterministic render(t).
topFDEjobs
Forward Deployed Engineer roles
Building with Claude? Get paid for it.
Forward Deployed Engineers ship AI agents inside real customer systems. Open roles at Anthropic, OpenAI, Cognizant and more.
A short one with five things in it: what the viewer should understand, duration, aspect ratio, a style, and what to avoid. Then ask for a storyboard before code. Use the builder on this page to assemble one, or start from a template.
How long should a video prompt be?
The median creator prompt is about 35 words, and nearly half are under 200 characters. Long specs help for 3D scenes, games and anything with exact timing. For a first draft, short is fine.
Do I need to tell Claude which library to use?
Usually not. In the prompts we analysed, only 38% named a library, yet the results used Canvas, SVG, Three.js and shaders fluently. Name one when you need a specific look: Three.js for 3D, p5.brush for hand-painted.
Why does my Claude video look generic?
Usually the same handful of effects: particle bursts, glow, lens flares, bouncy easing, and text that repeats the picture. Ban them by name and give one concrete style reference instead of adjectives.
How do I get the video synced to music?
Give Claude the BPM and the start offset of the first beat. Ask for cuts and key hits on the beat grid, and for a storyboard laid out on that grid. Supply the track yourself and mux it in with ffmpeg.
How do I iterate without breaking what works?
One change per message and name what to keep: "Keep everything else, only change scene 2." Review at half resolution and save the full quality render for the end.
Can I use these prompts commercially?
Yes. We wrote the templates on this page. Your output is subject to Anthropic's terms and to the licenses of any music, fonts or logos you put in.
Templates written by Awesome Claude. Statistics come from our analysis of 703 publicly shared Opus 5.5 video prompts by 616 creators. Last updated 2026-10-21.