Claude Opus 5.5 Video Prompts You Can Actually Run

Before you paste a prompt

Use Claude Code with Opus 5.5 at high or xhigh effort. Prepare Node.js, a Chromium-based browser, and FFmpeg. Start in a new directory, and give Claude only assets you own or are licensed to use. Ask for a low-resolution preview before a full render; a 30-second 1080p render is much cheaper to debug than to redo.

The prompt templates assume that Claude can create files and run local commands. They do not hide API keys in .env, silently download stock footage, or call a video-generation API while claiming the result is pure code animation.

1. A 15-second motion showreel

Why this made the cut: it is short, self-contained, and gives beginners a quick test of the complete browser-to-MP4 pipeline. The original one-line showreel prompt is useful as an idea, but this version adds the constraints that make the output inspectable.

Copy this into an empty Claude Code project:

Create a 15-second motion-graphics showreel for a fictional developer tool called Northstar.

Before coding, write a 5-shot storyboard with timestamps. Then build the animation as a single local HTML page using Canvas or SVG, with no remote assets. Use 1920x1080 at 30 fps, a dark background, one accent color, kinetic typography, geometric transitions, and a clear beginning, middle, and end. Keep text short enough to read at normal playback speed.

Add a deterministic preview mode and a render script. First render a 3-second low-resolution preview and inspect the first, middle, and last frames. Fix blank frames, clipped text, accidental layout shifts, and console errors before rendering the final MP4 with Chromium and FFmpeg.

Deliver the source files, the exact render command, the storyboard, and out/northstar-showreel.mp4. Do not use a video-generation API or download assets.

Expected result: a short MP4, a reproducible source project, and a render command. If the first version is visually flat, change one variable at a time: stronger timing, fewer words, or a more distinctive transition.

2. A 30-second business explainer

Why this made the cut: the five-part structure maps to a real communication job: problem, product, process, proof, and close. Replace the bracketed fields with your own facts; do not ask the model to invent customer numbers.

Act as a motion designer and information designer. Create a 30-second animated explainer for [PRODUCT], made for [AUDIENCE]. The verified product facts are: [FACTS]. Brand colors are [COLORS]. The only proof point you may use is [PROOF POINT].

Plan exactly five scenes before coding:
1. 0–5s: the audience's problem;
2. 5–11s: what the product does;
3. 11–21s: the workflow in three visual steps;
4. 21–26s: the verified proof point;
5. 26–30s: product name and one call to action.

Build it as a local HTML animation at 1920x1080, 30 fps. Use simple shapes, readable typography, smooth transitions, and no more than one main action per scene. Keep all on-screen claims faithful to the supplied facts. First show me the storyboard and a low-resolution preview; then render the final MP4 with a local browser and FFmpeg.

Deliver the MP4, source code, storyboard, and a list of every external asset or font used. If a fact is missing, leave a clearly marked placeholder instead of guessing.

This is a better first product video than a prompt that says “make it slick”: the model has a narrative, a duration budget, an input boundary, and a definition of done.

3. A process or recipe explainer

Why this made the cut: step-by-step animations are forgiving. The viewer can understand the output even when the visual style is simple, and the same template works for a recipe, onboarding flow, lab procedure, or API request.

Make a 30-second process explainer for [PROCESS]. The steps are exactly: [STEP 1], [STEP 2], [STEP 3], [STEP 4]. Use an empty starting state and a completed ending state so the transformation is obvious.

Create a storyboard before implementation. Give each step a visible number, a short label, a measurable value where relevant, and one animation that shows the step happening. Use HTML Canvas or SVG in a single local page, 1080x1080, 30 fps, with a 4-second opening, 5 seconds per step, and a 6-second conclusion. Keep labels inside safe margins and never let an animation hide the information it explains.

Render a 5-second sample first. Check that the order, labels, timing, and final state are correct. Then export the complete MP4 with local Chromium and FFmpeg. Deliver the source, render command, and a frame-by-frame timing table. Do not invent measurements or use copyrighted images.

For a recipe, replace [PROCESS] with the recipe and supply the exact measurements. For a technical tutorial, use real commands or screenshots as inputs instead of asking Claude to guess an interface.

4. A line-art educational short

Why this made the cut: the public examples show that line-art animation is a practical way to explain an abstract topic without requiring photorealistic assets. The important improvement is to require a fact sheet and a narration plan before drawing.

Create a 25-second line-art explainer about [TOPIC] for [AUDIENCE]. Use only the verified facts below: [FACTS]. The visual style is friendly hand-drawn 2D animation with a restrained palette, light background texture, and no photorealistic people.

First write a five-shot storyboard and a narration/subtitle script with timestamps. Each shot must show one concrete event or transformation; do not replace an explanation with a decorative title card. Keep subtitles to two lines maximum and leave safe margins for mobile viewing. Use deterministic animation code so the same input produces the same frames.

Implement the short locally with Canvas or p5.js at 1080x1920, 30 fps. Use generated shapes rather than unlicensed images. Render a silent preview first, inspect it at 0s, 12s, and 24s, then add either a local audio file supplied by me or a clearly labeled placeholder. Export the final MP4 and provide the source, timing table, and audio-sync command. Do not make historical or scientific claims beyond the supplied facts.

This template is intentionally more modest than “summarize five thousand years of history.” A broad topic can work, but only after you provide a checked outline and accept that the model is illustrating your facts, not doing source-critical research for you.

5. A hand-painted character short

Why this made the cut: a small character story gives the animation a beginning, an action, a reaction, and a payoff. It is a good test of timing and continuity without the geometry and performance cost of a large Three.js world.

Make a 12-second hand-painted 2D short about [CHARACTER] trying to [GOAL] and reacting when [OBSTACLE]. The story must have three beats: setup, attempt and reaction/payoff. Use flat 2D brush-like shapes, a small palette, visible frame-to-frame motion, and no 3D camera or realistic assets.

Plan three shots with exact timestamps before coding. Keep one focal action in each shot. The character's pose, proportions, and key props must remain consistent across cuts. Use Canvas or p5.js in a local HTML page at 1080x1080, 24 fps. Make the animation deterministic and keep the total render lightweight.

Render a contact sheet or short preview first. Check that the character does not slide, pop between poses, disappear behind the background, or finish the action before the viewer can read it. Then export out/character-short.mp4 with Chromium and FFmpeg. Deliver source code, storyboard, and render instructions.

Prompts I did not include

Some public examples are valuable as inspiration but poor beginner instructions. I left out one-line requests such as “make a modern slick video,” long historical films that need research and reference art, prompts whose source text is truncated, and entries that rely on private skills, paid image services, or another video model. A prompt can produce a spectacular post and still be a bad copy-and-paste recommendation.

From prompt to API key

Claude Code is the tool that writes and renders the project; APIMaster is the API route you can use when your workflow calls Claude programmatically or when you want a single key for multiple models. Create an APIMaster account, add a small pay-as-you-go balance starting from $1, create a key in the console, and use claude-opus-5-5 at https://apimaster.ai/v1. Check the live card and route status before a long render.

FAQ

Does Claude Opus 5.5 output an MP4 by itself?

No. Claude writes the animation code and local render commands. Chromium, a browser recorder, or another renderer produces frames, and FFmpeg commonly assembles them into an MP4.

Can I paste these prompts into the Claude web app?

You can use the planning portions there, but the complete workflow assumes a local project where Claude Code can create files, run a browser, inspect output, and call FFmpeg.

Which prompt should I try first?

Use the 15-second showreel to test your setup. Use the business explainer or process explainer when you need a useful video rather than a technical demo.

Are these prompts guaranteed to produce the same videos as the public examples?

No. Results depend on the model version, effort setting, local tools, assets, follow-up edits, and rendering pipeline. The templates make the work reproducible; they do not remove iteration.

Sources and selection method

This article was checked on September 29, 2026. The selection was based on whether a prompt had a clear output, feasible local dependencies, a bounded duration, and a way to inspect or repair the result.

• joeseesun/opus-video-prompts for public examples including showreels, explainers, recipe graphics, and line-art animation.
• yihui-dev/awesome-opus5-5-videos for the larger public prompt archive and its warning that entries vary in completeness.
• athemeroy/awesome-opus-5-5-videos for the prompt playbook and disclosure guidance around code, assets, and external video models.
• ClaudeAnimationBase for the reproducible local rendering pattern and the importance of timing checks.
• APIMaster live route data and model card for current pricing and availability.

Start with a small render

Open APIMaster, create a key in the console, and test claude-opus-5-5 through https://apimaster.ai/v1 before sending a long coding or rendering job.