APIMODELSAPIMODELS

Claude Opus 5.5 Video Editing & Post-Production 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

Raw talking-head clip cut into a punchy captioned edit

Cut a raw talking-head clip into a punchy, fun edit with subtitles, graphics and music

Model:
Post: "Opus 5.5 + OpenEdit".
Reported cost:
About 1 h 51 min; about $23 of tokens plus about $49 of generation-API usage.
Clip:
About 37 s, 1920x1080.
by @sab8aSource
Hover to preview · click for sound

Opus 5.5 driving After Effects to post-process generated clips (two tests)

Summary

Test 1: gave Opus 5.5 a 15-second clip generated by MiniMax H3 and had it drive After Effects to retime the cuts to the beat and add one effect per section (particles, light rays, kaleidoscope, datamosh). Test 3: Suno wrote the track, MiniMax H3 made a character dance to it, and Opus extracted full-body skeleton data frame by frame from the dance and fed it into After Effects to drive text, light and camera.

Model:
Post (Japanese): had Opus 5.5 operate After Effects.
Toolchain:
Author's conclusions: rough instructions still give decent results, and the output is saved as an .aep project a person can edit afterwards; skeleton data removes manual tracking, but deciding when to show the tracked effect still takes a human.
Links:
Test 1: x.com/aicreataro/status/2102656273112326609 (15 s, 1440x1280).
Clip:
Test 3: about 32 s, 1920x1080, about 380K views.
video by @aicreataroSource
Hover to preview · click for sound

A full YouTube video edited by Opus 5.5 through a DaVinci Resolve MCP

Prompt not published

Prompt not transcribed (the author says it is in his video and article). Raw footage recorded in Tella; DaVinci Resolve 21.1 driven through an MCP server; HyperFrames for B-roll and animation; Opus 5.5 as the editor of a full nine-minute YouTube video.

Model:
Post: "Claude Opus 5.5 edited my entire YouTube video".
Clip:
About 539 s (9 minutes), 3840x2160.
video by @NickSpisak_Source
Hover to preview · click for sound

Grok-generated dance clip recut and packaged by Opus 5.5

Prompt not published

No prompt published. A raw dance clip generated by Grok was recut and packaged (captions and on-screen text) by Opus 5.5; the post shows before and after.

Model:
Post (Chinese): video 1 is the Opus 5.5 edit, video 2 is the raw Grok output.
Clip:
Two clips of about 15 s each (1920x1080 and 960x960).
video by @Gorden_SunSource
Hover to preview · click for sound

Opus played its own game and cut the best moments into a demo reel

Prompt not published

No prompt published. The creator built a full game with the Unity CLI and Opus 5.5; Opus then played it with several characters and spliced the best moments into the demo video.

Model:
Post: "I turned this into a full game with unity cli + opus 5.5, also opus did this full demo video, it played the game with multiple characters and spliced together the best bits".
Links:
Playable: rehan-remade.github.io/hollow-crown/
Clip:
About 29.7 s, 1920x1080.
video by @rehan_sheiSource
Hover to preview · click for sound

Demo reel for a 110K-rigid-body WebGPU physics solver

Prompt not published

No prompt published. From a single text prompt in Claude Code, Opus 5.5 put together a demo reel for an open-source WebGPU physics solver running 110,000 rigid bodies.

Model:
Post: "Opus 5.5 even put together this whole demo reel video just from a single text prompt in Claude Code".
Links:
Code (MIT): github.com/sbobyn/three-avbd. Live: three-avbd.vercel.app
Clip:
About 26 s, 1920x1080.
video by @nybobsSource

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