Home / Opus 5.5 video prompts

Opus 5.5 video prompts

Copy-paste prompts for making an Opus 5.5 video with Claude: our own templates for the videos people actually need, the viral one-liners that started the trend, and a review prompt that turns a rough first Opus 5.5 video cut into something you can post.

Paste each Opus 5.5 video prompt into Claude Code (not the chat app) so Claude can write files, render frames and run ffmpeg. Updated September 30, 2026.

Short answer: the best Opus 5.5 video prompt names the length, aspect ratio and audience, gives Claude your real URL and screenshots, and asks for a shot list and still frames before any animation. Then run a review pass after every render.

Before you write an Opus 5.5 video prompt

Opus 5.5 doesn't generate video pixels. It writes an HTML, Canvas, SVG or Three.js scene, renders it frame by frame in a headless browser and stitches the frames into an MP4 with ffmpeg. So an Opus 5.5 video prompt is really a creative brief for a programmer who can animate. Three things make the biggest difference:

  1. Name the format. Length, aspect ratio, frame rate. "30 seconds, 1920×1080, 30 fps" beats "a short video".
  2. Give it real material. Your URL, real screenshots, real numbers. Invented UI always looks fake.
  3. Ask for stills first. Have it show keyframes before animating. Fixing a still takes seconds; fixing a render takes minutes.

Replace everything in [brackets]. Each Opus 5.5 video template is written by us and free to use.

1. Opus 5.5 video prompt: launch video (20-30 s, 16:9)

# Opus 5.5 video prompt: launch video
You are a senior motion designer who animates in code. Make a [30]-second launch video for [PRODUCT NAME] - [ONE-LINE PROMISE].

Audience: [WHO IT'S FOR]. Where it will be posted: [X / Product Hunt / landing page].
Source of truth: read [URL] first (home page + one feature page). Pull the product name, value proposition, 3 concrete capabilities, any real numbers, brand colors and fonts. Do not invent numbers or features.
Assets: [PATH OR LINK TO LOGO + SCREENSHOTS]. Use real screenshots for UI; never draw fake app screens.

Structure:
1. Hook (0–3 s): the problem or the promise, big type, max 6 words.
2. Name reveal (3–6 s).
3. Three beats (6–24 s), one capability each, each shown as a concrete mechanism on screen (UI appearing, a counter rising, data flowing) - one idea per beat.
4. Proof (optional): one real number.
5. End card: name + one line + URL, held for 2 seconds.

Style: [bold kinetic type / clean SaaS / playful]. Max 2 brand colors plus near-black and near-white. Max 8 words on screen at once. Spring easing, slight overshoot, no bouncy chaos, no glow, no gradients on UI.
Sound: royalty-free music around [110–125] BPM; cut on the beat; subtle whooshes on transitions.
Tech: one HTML file with a window.seek(t) function that draws any frame from the time alone (no Math.random without a seed). Render 1920×1080 at 30 fps with Playwright, encode with ffmpeg.

Before animating, show me a shot list with timings and one still per shot. Wait for my OK, then render.

2. Opus 5.5 video prompt: product demo (30-45 s)

# Opus 5.5 video prompt: product demo
Turn these app screenshots into a [40]-second product demo: [FOLDER WITH 5–10 SCREENSHOTS].

Product: [NAME] - [WHAT IT DOES] for [WHO].
Walk through one real task from start to finish: [TASK, e.g. "import a CSV and get a chart"].
For each step: place the real screenshot inside a clean device frame, zoom smoothly to the part that matters, and add one short caption (max 6 words). Animate a cursor that clicks where a user would click.

Camera: slow push-ins and pans, 1.5–3 s each, ease-in-out. No hard cuts inside the flow; one cross-fade between chapters.
Colors: [BRAND COLORS]. Font: [FONT or "match the screenshots"].
End: logo + "[CALL TO ACTION]" + [URL].
Music: calm, royalty-free, ducked under nothing (no voiceover).

Render 1920×1080, 30 fps, MP4. First send me the step list and three stills.

3. Opus 5.5 video prompt: vertical ad (15 s, 9:16)

# Opus 5.5 video prompt: vertical ad
Make a 15-second vertical ad (1080×1920, 30 fps) for [PRODUCT] aimed at [AUDIENCE].

Second 0–1: a pattern-interrupt hook - huge text "[HOOK, e.g. Stop doing X by hand]" slamming in.
Seconds 1–11: three fast beats showing [BENEFIT 1], [BENEFIT 2], [BENEFIT 3], each with a real screenshot or product shot from [ASSETS] and one line of text.
Seconds 11–15: offer + CTA: "[CTA]" and [URL / handle].

Keep all text inside the middle 80% of the frame (platform UI covers the edges). Captions must be readable on a phone with the sound off.
Style: high contrast, [BRAND COLOR] accents, punchy cuts on every beat of a ~120 BPM royalty-free track.
No fake testimonials, no invented numbers.

Show me the beat sheet and 4 stills before rendering.

4. Opus 5.5 video prompt: explainer with voiceover

# Opus 5.5 video prompt: explainer
Make a [60]-second animated explainer about [TOPIC / PRODUCT] for [AUDIENCE].

Step 1 - script: write a voiceover script in plain English (about 140 words for 60 s): the problem → why it matters → how it works in 3 steps → one proof point → call to action. Show me the script before anything else.
Step 2 - voice: generate the voiceover with [TTS PROVIDER; API key is in .env as TTS_API_KEY - do not print it]. Measure the real duration of each sentence.
Step 3 - storyboard: one shot per sentence, timed to the measured audio. Each shot is a clear diagram or animated metaphor, not stock-looking decoration.
Step 4 - build and render: [line-art / flat illustration / clean infographic] style, [COLORS], burned-in captions synced to the voice, soft background music ducked under the voice.

1920×1080, 30 fps MP4. Stop after each step for my approval.

6. Review pass: run it after every Opus 5.5 video render

Act as a picky senior motion designer reviewing this Opus 5.5 video cut. Render a contact sheet: the first frame, the last frame, one frame just before and just after every cut, and every 0.5 s in between. Look at them and list every problem you find, most serious first:
- text that overlaps, gets clipped, or is on screen too briefly to read (under ~1.2 s for a short line)
- blank or near-empty frames, especially at the start
- anything that sits still for more than 1.5 s
- transitions that stack two pieces of text on top of each other
- inconsistent colors, fonts or corner radii
- motion that ignores the beat of the music
- an ending that stops abruptly
Then fix everything on the list, re-render, and repeat the check once more. Tell me what you changed.

This loop - render, look, critique, fix - is what separates a good Opus 5.5 video from a forgettable one. One-shot results are a lottery.

One-liners behind a viral Opus 5.5 video

Each one-liner below was posted publicly by its creator and produced an Opus 5.5 video that got attention in the first week. They show how far a single sentence goes, and why results vary run to run. Quoted with credit; follow the links to see the original videos.

The showreel Opus 5.5 video

make a dynamic 15-second motion graphics video that shows what an incredible motion designer you are, like it's your showreel for a résumé. go all out.

Opus 5.5 video prompt posted by @stephanlivera (1.6M views) and many others. Swap the ending for "…for [your website URL]" to get a product showreel, as @melvynx did.

The one-line startup Opus 5.5 video

make a modern slick and punchy video for a modern startup that works on inference

Opus 5.5 video prompt posted by @deedydas (339K views). Replace "works on inference" with what your startup does.

Research-first Opus 5.5 video

Make a dynamic 15-second motion graphics video that shows what an incredible motion designer you are. The content should focus on [your product]. You should visit the pages first to learn about the product, then write the video content yourself.

Opus 5.5 video prompt posted by @ann_nnng.

Square, looping Opus 5.5 video

Make a dynamic 15-second motion graphics video that shows why [your product] is the best at [what it does], like a showreel. Go all out: 1080×1080, 1s hook, loop.

Opus 5.5 video prompt posted by @Ishaaqahamed.

Milestone launch Opus 5.5 video

Create a launch video for MotionSites AI, just hit 1 million monthly visitors after 8 months after launch.

Opus 5.5 video prompt posted by @viktoroddy. A real milestone gives the video a story.

An Opus 5.5 video from your app's own assets

can you help me use the pig assets on new branch of lovelee to make a 9:16 short story animation with sound effects about the pig sending his partner love notes in the mailbox and make it fun and good tease app at end?

Opus 5.5 video prompt posted by @jackfriks. Running Claude Code inside your own repo lets it reuse your characters and brand.

Homage ad as an Opus 5.5 video

create a 30 second ad for Opus 5.5 inspired by Apple 1984 ad, iykyk! avoid the border text or frames!

Opus 5.5 video prompt posted by @1littlecoder. Note the last line: it bans the corner labels and frames that give away AI-made videos.

Longer public Opus 5.5 video templates worth reading in full at the source: @twoclipping's UI-morph template (asks you for 8–12 UI states, one accent color and a song, then builds on a beat grid) and @rexan_wong's six-step pro workflow (reference video → code renderer → real UI components → stills first → director notes).

Quick fixes for a weak Opus 5.5 video

ProblemAdd this to your Opus 5.5 video prompt
Your Opus 5.5 video looks generic"No corner labels, frame borders, timecodes or fake UI chrome. Use only real screenshots."
Text in the Opus 5.5 video is too fast to read"Every line of text stays fully visible for at least 1.2 seconds. Max 8 words on screen."
The Opus 5.5 video starts on a blank frame"Frame 0 must already show the hook."
The Opus 5.5 video ends abruptly"Hold the end card for 2 seconds and let the music resolve."
The Opus 5.5 video flickers or jumps between frames"Every frame must be computed from time t only - no Date.now, no unseeded Math.random, no CSS transitions."
Everything in the Opus 5.5 video moves at one speed"Vary rhythm: fast cuts on the beat, then one slow 2–3 s move per section."
Each Opus 5.5 video burns through your usage"Render 5 sample frames first; only render the full video after I approve."

Opus 5.5 video prompt FAQ

What is the best prompt for an Opus 5.5 video?

There is no single magic line. The prompts that work give the format (length, aspect ratio, frame rate), real material (your URL and screenshots) and a style reference, and they ask for stills before animation. Template 1 above is a good default for a launch Opus 5.5 video.

Does a longer Opus 5.5 video prompt give a better result?

Only when the extra words are decisions: which shots, which numbers, which colors, what to avoid. Long lists of adjectives do not help. The viral one-liners show that a short prompt can work, but results vary a lot between runs.

Can I use these prompts with Sonnet 5.5?

Yes. Several creators report Sonnet 5.5 producing an Opus 5.5 video level of motion design at lower cost for short pieces. For long or complex scenes, Opus 5.5 is still the safer pick.

Where do I paste an Opus 5.5 video prompt?

In Claude Code, in an empty folder or inside your product's repo, with Opus 5.5 selected. The chat app can preview animation but cannot render an MP4 on its own.

Rather skip the prompting?

We run this whole process for you: brief, stills, render, review, 3 revisions. Your Opus 5.5 video costs $50.

Order a video →