APIMODELSAPIMODELS

Claude Opus 5.5 Video Explainer & Education Prompts

Sixty real videos made with Claude Opus 5.5, each credited to its creator and linked to the original post, with the toolchain they used and, where they published it, the prompt word for word. Opus 5.5 does not draw pixels: every clip here was rendered from code it wrote, or cut together from video models it directed.

← All 60 Claude Opus 5.5 Video prompts

Last updated: · Claude Opus 5.5 API — pricing & playground · API docs

TL;DR

Claude Opus 5.5 (model id claude-opus-5-5, released by Anthropic on 22 September 2026) is a language model. Anthropic's documentation lists text and image input and text output only, states that Claude cannot generate or edit images, and offers no video input: an animated GIF is read as its first frame. The videos credited to it are made in one of three ways. It writes animation code (a self-contained HTML page driven by a seek(t) function, Remotion or HyperFrames compositions, Manim scenes, Three.js and WebGL shaders, Blender Python) that a headless browser or renderer turns into frames and FFmpeg encodes into an MP4. It directs video, image and music models through APIs, writing the shot list and every prompt, then edits the results. Or it edits existing footage through FFmpeg, After Effects or DaVinci Resolve. A video billed as "one prompt" is often a brief of several thousand characters, run inside an agent with skills, API keys and hours of autonomous work, so each case below records what the creator actually supplied and what they reported spending. The 60 cases were posted between 22 September and 3 October 2026 and each was checked against the original post. On apimodels.app, Opus 5.5 is $2.40 per 1M input tokens and $12 per 1M output tokens, against Anthropic's $4 / $20 list.

Source: Anthropic · Claude Opus 5.5 (the model vendor’s official site)

Hover to preview · click for sound

Manim lesson on derivatives with edge-tts narration

请用Manim给我制作一个导数概念学习的视频,要求通俗易懂,并且有例子,引人思考。配音使用edge-tts

Model:
Post (Chinese): Opus 5.5 + Manim made a lesson on derivatives; "Opus 5.5 is clearly very good at Manim".
Toolchain:
Claude Code with Manim, LaTeX and edge-tts installed locally.
Clip:
457 s (about 7.6 minutes), 1920x1080.
Pitfalls:
No length was given and it planned a 7.6-minute lesson; add a time limit if you need one.
by @LinearUncleSource
Hover to preview · click for sound

12-minute Chinese explainer "What is a Transformer", rendered in JS

帮我用js制作一个视频,主题是:什么是 Transformer 要深入浅出,让高中生也能看得懂,不仅high level说的清楚,也要有细节,包括注意力机制,甚至一些数学概念 你可以用任何工具或者安装工具,可以联网检索 请给我惊喜

Model:
Post (Chinese): made with Claude Code + Opus 5.5.
Clip:
About 732 s (12.2 minutes), 1920x1080, about 190K views.
Pitfalls:
A short prompt with wide autonomy (any tool, web search allowed); the model chose the length and structure itself.
by @doteySource
Hover to preview · click for sound

Epic chronicle of Chinese civilization, frame-rendered with FFmpeg

做一支史诗编年片《中华文明史》,可以写代码逐帧渲染,再用 ffmpeg 合成。 配乐当时钟:五声调式,乐器从骨笛、编钟一路演进到管弦,BPM 随年代加快,所有切点踩拍。 宣纸白描和玄底泥金两种画风交替;每卷一个主色和一套随时代演变的纹样(彩陶纹 → 饕餮纹 → 云气纹 → 卷草纹 → 缠枝纹 → 回纹)。 每镜一个按词组出现的书法大字关键词,配一幅线稿。全片 HUD:左上朱印卷号,右侧竖排朝代名,底部卷轴时间尺和年份计数。 卷交界用朱印盖下、鼓钟重击的冲击转场。先定拍点网格和分镜表,再渲染。 地图只画示意,不画近现代真实人物,年代核对后再交付。

Model:
Post title: "Chinese Civilization by Opus 5.5" (Chinese).
Clip:
About 217 s, 1920x1080.
Pitfalls:
A model Chinese director brief: the score is the clock, the beat grid and shot table come before rendering, dates are checked before delivery, and real modern people are kept out of frame.
by @doteySource
Hover to preview · click for sound

Explaining recursion in nine radically different video styles

A video explaining recursion, where every explanation about recursion has a radically different video style, make this self-referential & clever & fast moving.

Model:
Post by Ethan Mollick: "I had Claude Opus 5.5 make…".
Clip:
About 75 s, 1920x1080, about 70K views.
Pitfalls:
A concept plus one structural rule (every section changes style) works better than a pile of adjectives.
by @emollickSource
Hover to preview · click for sound

Negroni recipe motion graphic from a single photo

We're going to try a little test. Do you think you could render a recipe motion graphic animation using javascript or html (w/e you think will produce the best) to show the full recipe from start to finish (empty glass to completed cocktail) - Explainer video style - Showing the recipe ingreidents + measurements as they're going into the cup. Should be a 30s video.

Model:
Post: "Opus 5.5 rendered this in HTML from (1) image".
Toolchain:
One reference photo uploaded, then an HTML/JS animation, then recorded. Typos in the prompt are the author's and kept as published.
Clip:
30 s, 1080x1080.
Pitfalls:
The typical image-in, animation-out use: Opus 5.5 can read a photo, not a video.
by @Ror_FlySource
Hover to preview · click for sound

Interactive Raptor 3 rocket engine you can take apart (screen recording)

Summary

Asked Opus 5.5 to explain how a rocket engine works by building an interactive Raptor 3 in the browser that you can take apart: cut it open, trace oxygen and methane through the two turbopumps, and throttle it to watch the shock diamonds move. The video is a screen recording of that page.

Model:
Post: "I asked Claude Opus 5.5 to explain how a rocket engine works by building an interactive Raptor 3".
Links:
Live page: airsup.ai/rocket-engine. Same author, fusion-reactor version: x.com/konstantinsaifo/status/2104216976801587629
Clip:
About 34.7 s, 1920x1080, about 1.15M views.
video by @konstantinsaifoSource
Hover to preview · click for sound

Twin-paradox explainer in Japanese, paper-cutout style, 1,395 Canvas frames

Prompt not published

Prompt not published beyond the method: in Claude Code the author gave Opus 5.5 the URL of a reference post plus brief instructions, and it produced a Japanese version of a twin-paradox explainer in a paper-cutout style, entirely in code, including BGM and sound effects generated in JavaScript.

Model:
Post (Japanese): "made a Japanese version with Claude Code x Opus 5.5".
Toolchain:
Canvas rendered 1,395 frames and converted them to MP4; rendering took about 2 minutes.
Clip:
46.5 s, 1080x1080.
Hover to preview · click for sound

3Blue1Brown-style explainer on variational autoencoders

Prompt not published

No prompt published (the author calls it "one short prompt"). Manim for the animation and equations, a model actually trained on MNIST so every digit on screen is real, narration from a cloned voice with Qwen3-TTS on MLX, and original background music.

Model:
Post: "Opus 5.5 can now make animated explainer videos end to end, in a style similar to 3Blue1Brown".
Clip:
About 5.6 minutes, 1920x1080 (low reach, about 1.5K views).
video by @ng169onXSource
Hover to preview · click for sound

Three-minute history of AI, 100% code in Remotion

Prompt not published

No prompt published. A three-minute history of AI made 100% in code in Claude Code: about 7,400 lines of React and TypeScript in Remotion, every image drawn in SVG or Canvas, open-source TTS narration and a score composed in Python.

Model:
Post: "This 3-minute film was made 100% in code by Claude in Claude Code", with Opus 5.5.
Reported cost:
About 1 hour and 7% of a weekly usage allowance.
Clip:
About 180 s, 1920x1080, about 200K views.
video by @kimmonismusSource
Hover to preview · click for sound

Black-hole lensing lab polished by reviewer and fixer agents overnight

Prompt not published

First prompt not published. One prompt produced the first version of an interactive gravitational-lensing lab; then three rounds of three agents each (two reviewers listing 9-10 issues ranked P0/P1/P2, one fixer), focused in turn on materials, lighting and UI; camera interaction and science design; and a design-director sign-off with visual QA and performance. Each round started from a backup, ended with screenshot checks, and rolled back anything it could not fix.

Model:
Post: "I asked Opus 5.5 to explain gravitational lensing…".
Reported cost:
5 hours 28 minutes in total, about $90 at API prices.
Clip:
About 21.8 s, 3840x2160.
Pitfalls:
The most complete public example of the review-and-fix loop.
video by @Voxyz_aiSource
哔哩哔哩

4.6 billion years of Earth's evolution (Bilibili)

Prompt not published

No prompt published. The uploader says it was one simple prompt that ran for about two hours and produced a delivery-grade result.

Model:
Bilibili title: "Opus 5.5's miracle" (Chinese).
Clip:
290 s, 2560x1440, about 80K plays.
哔哩哔哩

"The Beauty of Group Theory" promo film (Bilibili)

Prompt not published

No prompt or toolchain published; the evidence is the title and description only.

Model:
Bilibili title: "opus5.5 has arrived: The Beauty of Group Theory promo" (Chinese).
Clip:
263 s, 1920x1080, about 340K plays.
video by sadssxaSource

How to write great Claude Opus 5.5 Video prompts

  1. 1Ask for the plan before the code. The strongest briefs in this library end the same way: show me the shot list, the beat grid or the list of states, then wait. Fixing a storyboard costs one message; fixing a rendered film costs a re-render and often a rewrite.
  2. 2Make every frame a function of time. Have it expose window.seek(t) and compute every style from t: no timers, no requestAnimationFrame loop, no CSS transitions, no unseeded randomness. Then a headless browser can render any frame on demand and FFmpeg can encode a steady 60fps. A live animation captured by screen recording drops frames whenever the machine is busy.
  3. 3Name the framework, or it will not use one. Left alone, Opus 5.5 writes one dependency-free HTML file from scratch even when Remotion or HyperFrames is installed. If you want a React timeline, Manim's equation animation or Blender's renderer, say so in the first line and install the matching skill.
  4. 4Ban the defaults by name. Anthropic's own prompting guide for Opus 5.5 notes that asking it to avoid a generic look only swaps one default style for another. The briefs that stand out list exactly what is banned (centered text on a gradient, everything fading in, particle bursts, neon glows, bouncy easing, lens flares) and pair that with one accent colour and one typeface.
  5. 5Render stills and make it critique them. It can read images but not video, so the review loop runs on frames: one still per beat, or twenty sampled frames, inspected before the full render. Several creators here ran that loop dozens of times or split it into reviewer and fixer agents, and credit it for the difference between a good clip and a forgettable one.
  6. 6Hand it the soundtrack, then let it do the maths. Give it a track whose licence covers your use and ask it to measure tempo and beats (numpy is enough), cut on downbeats, place each sound effect by its measured peak rather than where the file starts, and normalise loudness to -14 LUFS. With no track, it can synthesise music and effects in Web Audio or Python on the same timeline.
  7. 7Put a cost gate in front of every paid call. When it directs video or image models, make it list every generation with its estimated cost and wait for your OK, and show you stills before each expensive step. Without that line, an agent running for hours will happily spend whatever the keys allow.
  8. 8Match effort and time to the job. Creators report xhigh or max effort on the pieces that travelled and medium for small fixes; Anthropic suggests raising effort only where you measure a quality gain. Budget wall-clock time too: a five-minute history film here took 90 minutes to build and four hours to render, and one music video ran overnight.

Prompt formula

Director brief = the inputs it must ask you for + direction (one style, one accent colour, one typeface, an explicit banned list) + structure (every shot timed on a beat grid) + build contract (resolution, fps, seek(t), renderer, how to check frames) + known gotchas + a start line that asks for the plan before any code

Example: <inputs> Ask me for the app name, three screenshots and a 100 BPM track I hold a licence for. </inputs> <direction> 20 seconds, 1080x1920, one continuous take. Off-white background, one green accent, Inter. Banned: gradients, particle bursts, glows, bouncy easing. </direction> <structure> Eight bars: the name types on; a screenshot rises into a phone; a cursor taps through three screens on the beat; a delivery route draws itself; logo and the line "Fresh beans every Friday". </structure> <build> One HTML file, every style computed inside window.seek(t). Render with Playwright at 60fps, encode with FFmpeg, check one frame per bar first. </build> <start> Ask for the inputs, then show me the bar-by-bar plan before writing any code. </start>

Frequently asked questions

Can Claude Opus 5.5 generate a video by itself?

Not as pixels. Anthropic's documentation lists text and image input and text output for its current models and states that Claude cannot generate, produce or edit images. Every video on this page was either rendered from code Opus 5.5 wrote (HTML and Canvas, Remotion, HyperFrames, Manim, Three.js, Blender Python and so on) by a headless browser or renderer plus FFmpeg, or made by video models it directed through an API and then cut together. In a chat window with no shell you get the animation as an HTML page you can open and screen-record; producing an MP4 directly needs an agent environment that can run commands.

Can Opus 5.5 watch a video I give it?

No. It has no video input, and an animated GIF is read as its first frame only. The workaround every editing case here uses is to have it extract frames (and transcribe the audio) with FFmpeg and look at those stills. It reviews its own renders the same way.

Do the "one prompt" videos really come from one sentence?

Some do: the 15-second showreel prompt is a single sentence. Many of the widely shared cases ran on briefs of thousands of characters, with skills installed in advance, API keys for voice, music or video models, and runs of one to twelve hours, sometimes with dozens of review rounds. Costs on these cards are what each creator reported, from about $2 for a 26-second launch clip to around $400 of credits across 33 versions of a product trailer. Every card is marked as an original prompt, our summary of a method the creator described, or a case whose prompt was never published.

What do I need installed to reproduce these?

For an MP4: an agent that can run commands (Claude Code or a similar tool), Node.js, Playwright or another headless Chromium, and FFmpeg. The UI-motion templates also use Python with numpy to analyse the soundtrack; Manim cases need Manim and LaTeX; Blender cases need Blender; music-video and director cases usually need API keys for voice, music or video models.

Which approach should I start with?

For a product clip or a UI animation, start with the single-HTML route or a framework such as Remotion; both are on this page with full prompts. For a lesson, use Manim. For anything with real people, natural motion or physics, let Opus direct a video model and keep a cost gate in the brief. For footage you already shot, use the editing route and expect to make the pacing calls yourself.

How much does Opus 5.5 cost for this on apimodels.app?

$2.40 per 1M input tokens and $12 per 1M output tokens (Anthropic lists $4 / $20), billed per token with failed calls free, through /v1/messages or the OpenAI-compatible /v1/chat/completions, so Claude Code and other Anthropic-compatible agents connect with a base URL and a key. Video work is output-heavy: one creator's Blender test wrote about 200K output tokens, roughly $2.40 of output at our rate. Our own single-HTML test through apimodels.app was one call of 31,786 output tokens, billed $0.368, for a 12-second 1280x720 promo. If Opus directs video models, those calls are billed separately per model; Seedance 2.5, MiniMax H3, Kling V3 and Wan 3.0 run under the same key.

Can I reuse these prompts and videos?

The videos belong to their creators. Clips from X play straight from X's own servers, every card links to the original post, and we do not host or re-upload any of them. Prompts are quoted with credit and a link: several authors explicitly invited reuse, others simply published theirs, so check the post before using one commercially. Some cases use third-party music, pay homage to an existing film or show real people, and each of those cards names the source material. If you made one of these and want the card removed or the credit corrected, email us.

Run these prompts on apimodels.app

Claude Opus 5.5 is live here alongside 180+ other image, video, audio and language models — one API, one key, pay as you go, with $0.10 of trial credit on sign-up.

This library is open source on GitHub

The whole collection is on GitHub as Markdown and JSON: all 60 cases with credits and links to the original posts, the six workflows with templates, and the prompt and render scripts from our own run. The videos stay with their creators and are linked, not re-hosted. Prompts are quoted in full when the author invited reuse or the prompt is short; long ones are excerpted and unpublished ones are left out. Our own notes, templates and code are licensed CC BY 4.0. Open an issue to add a case or correct a credit.

View on GitHub

Other prompt libraries