DEV Community: Jonathan Everleigh

Opus 5.5 Video Prompts: A Six-Part Spec That Gets Past the Default Look

Jonathan Everleigh — Sun, 04 Oct 2026 00:26:29 +0000

An Opus 5.5 video is code, and any decision your prompt doesn't make gets resolved with a default. When it's asked for frontend work with no design direction, Opus 5.5 falls back on a few default styles, and a vague "avoid a generic AI look" mostly trades one default for another. The fix is to treat the prompt like a spec: decide format, content, structure, look and motion yourself, and list the defaults you want gone by name. After the first render, append whatever default showed up to that list and run it again.

Most shared prompts skip almost all of that. The Opus 5.5 video prompts people post tend to be short. Among those at roughly 100 words or under, the median length is 26 words and more than a quarter are one sentence. Fewer than 2% mention color at all.

What the Prompt Actually Controls

In the common setup, Opus 5.5 emits a single self-contained HTML file built on Canvas, SVG, GSAP or Three.js. A headless browser steps through that file one frame at a time, and the captured frames get encoded into an MP4. So the prompt can only steer what code can decide: on-screen text, colors, layout, typography, motion and timing. It can't shoot a scene or record a voice; those jobs go to other tools.

Anthropic documents the defaults Opus 5.5 reaches for in frontend work, cream backgrounds and pill-shaped buttons among them. The video equivalent everyone has seen is centered text on a gradient with everything fading in.

How much the prompt has to carry depends on the runtime:

In Claude or Claude Code, the prompt also has to carry the render contract: one HTML file, every frame computed as a pure function of time through a seek(t) function, and no timers or CSS animations. That's what lets a renderer grab any frame in any order.
On opus6.video, the contract is built in. The tool sets the motion-designer role, makes Opus produce a storyboard before any code, enforces the rendering rules, and adds baseline craft: varied rhythm, a clear type hierarchy, a definite ending. Format and length are buttons, the look comes from a preset or up to three brand colors, and you can attach up to four named effects. The brief field takes up to 2,000 characters, and output is silent. That leaves content and design for your brief.

The Spec: Six Fields in an Opus 5.5 Video Prompt

Format: Duration, Aspect Ratio, Playback Context

Format covers the duration, the aspect ratio, and the viewing context: a phone with the sound off, a five-second intro, a loop on a landing page. Put it on line one. Leave out the length and Opus chooses: a one-line prompt asking for the history of AI returned a video of nearly three minutes.

A 15-second 16:9 launch video for a product page, readable with the sound off.

Content: Literal Copy, Names, and Figures

With nothing but "Make a launch video for my plant care app," Opus called our test app "Verdant" and closed on a "Download free" card dated spring 2026. Every string a viewer reads (product name, headline, features, figures) gets made up if you don't pass it in. A one-line launch prompt for a real product priced it in dollars when the product uses pounds and redrew the app from imagination.

Pass the copy literally, in quotation marks, exactly as it should render. For explainers, supply the dates and numbers yourself, or verify every one Opus writes before shipping.

Headline: "Your plants, finally on schedule." Features: snap a photo to identify any plant; a watering reminder for every pot; a care log that shows what worked.

The most reused Opus 5.5 prompt is the showreel one-liner. Posts that ran it unchanged have a median of 3 likes; posts that added their own product, topic or music to that same sentence have a median of 34. The previous post in this series, 13 code-rendered clips and their prompts, has all 13 finished videos with their full prompts, the showreel included.

Structure: Beat List and End Frame

Structure defines the beat count, what each beat does, and how the video ends. Assign the last frame a job and a duration; a video that stops mid-motion reads as unfinished.

Open on a drooping houseplant in the first second, reveal the Fernly name, one beat per feature, then end on a card with the headline and fernly.app, held for the last 2 seconds.

Look: Reference, Palette, Type Rule

The look is three decisions, and shared prompts rarely make the second or third.

A named reference. In our test, "Swiss botanical poster" produced flat, poster-like shapes. Two or three words like "Sand animation", "origami" or "Grand Budapest Hotel" are enough to load an entire visual world, as the story examples in the previous post show.
Literal colors. Pass hex values and give each one a role, and append "No other hue" when nothing else should appear, the way the previous post's 20-second identity bumper does. All three hex values in our test rendered exactly as written.
A typeface by name. Anthropic's design guidance names Inter, Roboto and Arial as overused defaults. Choose a face with some character and bind it to a role: one for headlines, one for small labels. Archivo Black and Archivo, named in our brief, are what rendered.

Look: a Swiss botanical poster. Background #10352A, accents #8FD694 and #F2B134, all type in white. Archivo Black for headlines, Archivo for small labels. Big type on a strict left-aligned grid.

Motion: Tempo and Transition Rules

"Punchy" hands both speed and transitions back to Opus. A tempo in beats or seconds snaps every change to a count, like the UI video in the previous post that used "120 BPM, 7 bars, something happens on every beat". A transition rule disables the fade-in default, as in the previous post's photo-print launch: "Every scene is made out of the previous one: nothing fades, blurs or cuts". Add one spot where the video holds still, so the pace has contrast. Transitions described in detail get implemented: in our test, the leaf-into-F-into-phone transition from the brief showed up on screen.

Motion: 120 BPM, something changes on every beat. Each scene grows out of the previous one. Fast cuts, with one held beat on the headline.

Avoid: The Denylist

List the exact patterns you don't want. A blanket "no AI slop" just gets you a different default; a list of named patterns removes them. A starting denylist:

centered text on a gradient
everything fading in
an ending that is only a logo
cream or off-white backgrounds
italic accent words
numbered 01/02/03 labels
small uppercase labels above every headline
pill-shaped buttons
a glow on a dark background

About one in twelve of the short prompts people share has any "no" or "avoid" instruction at all.

All six fields together fit in a short block you can fill in:

Format: [length], [aspect ratio], watched [where and how].
Content: [product or topic]. Headline: "[exact words]". [Features, facts, numbers].
Structure: [opening beat], [middle beats], end on [final frame], held for [seconds].
Look: [named reference]. Background [#hex], accents [#hex] and [#hex]. [Typeface] for headlines, [typeface] for labels.
Motion: [tempo]. [Transition rule]. Hold on [moment].
Avoid: [default], [default], [default].

Test Run: One Brief, Three Versions on opus6.video

We generated the same launch video three times on opus6.video for a made-up plant-care app called Fernly. All three runs used 16:9, 15 seconds, the "From my prompt" look, no template and no effects, so the brief was the only variable. Each generation took about 75 seconds.

Run 1: Topic Only

Make a launch video for my plant care app.

Run 1: name, release date and features were all invented by Opus.

The scenes switched between a dark green radial gradient and a cream background, headlines were set in a serif, and the features were Opus's own. The end card added a pill-shaped button.

Run 2: Content and Structure

Run 2's brief, 82 words long, supplied the name, the headline and three features, and laid out every beat through to a held end card.

Run 2: the copy is correct and the look is all Opus defaults.

Every word, feature and beat rendered as written, including the end card holding for the final two seconds. The look came straight off the default list: a cream background, numbered "01 / 02 / 03" labels, a pill-shaped button and Inter for body text.

Run 3: Look, Motion and a Denylist

This brief kept everything from run 2 and appended three lines, for 192 words in total.

Look: a Swiss botanical poster. Background #10352A (deep fern green), accents #8FD694 (leaf green) and #F2B134 (pollen yellow), all type in white. One typeface: Archivo Black for headlines, Archivo for small labels. Big type on a strict left-aligned grid.
Motion: 120 BPM, something changes on every beat. Each scene grows out of the previous one: the drooping leaf straightens into the F of Fernly, and the F's stem becomes the phone outline. Fast cuts, with one held beat on the headline.
Avoid: centered text on a gradient, everything fading in, cream or off-white backgrounds, italic accent words, numbered 01/02/03 labels, neon glow, and an ending that is only a logo.

Run 3: colors, typeface, grid and transitions follow the brief.

The three colors, the typeface and the grid all show up as written, and the transitions followed the brief: the drooping leaf straightened into the stem of a giant "F", and the F folded into the phone outline. None of the cream backgrounds, centered gradient text or numbered labels came back. Two new issues did. Opus kept a small label above every headline and replaced the banned numbers with uppercase words ("DAY 9 · NO WATER", "ANY PLANT, ONE PHOTO"), plus dash page indicators in the corner. And the layout broke twice: the wordmark overflowed the right edge at 3.4 seconds, and the end-card plant overlapped the headline.

Version	Added to the brief	What changed	What was still wrong
1	The topic	A finished launch video	Invented name, date and features; gradient and cream end card
2	Name, headline, features, structure	Every word and beat correct	Cream background, 01/02/03 labels, pill button
3	Look, motion, avoid list	Colors, type, grid and transitions as written	Labels swapped to uppercase words; two layout slips

Fill-in Templates for Four Video Types

Swap out the bracketed text, keep the structure, and change one field at a time when the output is off.

Product Launch

Inputs to prepare: the product name, the headline, three features of a few words each, the URL, and two or three brand colors.

A 30-second launch video for [Product], [what it does in one line].
Headline: "[headline]". Features: [feature 1]; [feature 2]; [feature 3].
Structure: a hook in the first second, the product name, one beat per feature with a simple product-screen illustration, then an end card with the headline and [url], held for the last 3 seconds.
Look: [named reference]. Background [#hex], accents [#hex] and [#hex]. [Typeface] for headlines, [typeface] for labels.
Motion: [tempo]. Each scene grows out of the previous one. One held beat on the headline.
Avoid: centered text on a gradient, everything fading in, cream backgrounds, numbered 01/02/03 labels, pill-shaped buttons.

Settings: 16:9, 15 or 30 seconds. To raise the energy, edit Motion first; to shift the mood, edit the named reference. Finished launch videos with their prompts are examples #2 to #4 in the previous post. opus6.video's Product launch template starts from this structure.

App Walkthrough

Inputs to prepare: the three or four actions to demo, plus a description of each screen: sidebar items, list names and button labels. Opus draws the UI from that description, so the more exact the screen text, the closer it looks to your product.

A 30-second walkthrough of [App], [what it does].
Show these actions in order: [action 1], [action 2], [action 3]. A cursor performs each one with a real click or drag.
Screens: [screen 1: sidebar items, header, list contents]; [screen 2: ...].
End on "[closing line]" over the final screen, held for 3 seconds.
Look: [your app's real colors as #hex], [your app's typeface]. Keep the interface flat and exact, no glassy reflections.
Motion: zoom in on each click, hold for one beat after every state change.
Avoid: invented features, placeholder text, a logo-only ending.

Settings: 16:9, 30 seconds. For a more ambitious take, one shape can morph through every state, as in the single-shape UI example from the previous post.

Vertical Social Ad

Inputs to prepare: one claim, one number or contrast that backs it up, and the call to action.

A 15-second vertical ad for [Product]. It must read with the sound off.
Hook in the first second: "[hook line]". Then "[claim]", then "[proof]", then "[call to action]".
One idea per screen, big type, at least half the screen height for the main line.
Look: [named reference]. Background [#hex], text [#hex], one accent [#hex]. [Typeface].
Motion: a hard cut every 2 seconds, one held beat on the proof.
Avoid: centered text on a gradient, everything fading in, small captions.

Settings: 9:16, 15 seconds. The fintech ad among the previous post's examples hangs its whole pitch on one contrast: "Money still moves like it's 1973."

Explainer

Inputs to prepare: the steps in order and every fact, date and number that should appear on screen.

A 30-second explainer: [topic] in [number] steps.
Steps: 1. [step]. 2. [step]. 3. [step]. Use only these facts: [facts and numbers].
Structure: a title card, one step per scene with a diagram that builds up, a progress tracker showing which step we're on, then a one-line summary held for 3 seconds.
Look: [named reference, e.g. a technical manual or a chalkboard]. Background [#hex], diagram lines [#hex]. [Typeface].
Motion: each diagram draws itself in, then holds for one beat before the next step.
Avoid: invented numbers, centered text on a gradient, everything fading in.

Settings: 16:9, 30 seconds. A step tracker like the one in the previous post's Negroni recipe keeps viewers oriented. On opus6.video, anything longer than 30 seconds has to be split into parts.

Iterating on a Video Prompt

Check the Storyboard Before the Render

opus6.video streams Opus's storyboard while the code is still being generated. Run 2's storyboard opened with "Warm cream background, a terracotta pot centre-left" before a single frame existed. If the storyboard is wrong, stop and edit the brief before the code gets written.

One Class of Bug per Round

Include a timestamp. Something like "At 3.4 seconds" or "from 13.5 seconds" gives Opus the exact location, and scoping each round to a single kind of problem keeps the rest of the video untouched.

Report the Symptom and the Expected Result

Don't prescribe the patch. A note that prescribes a fix gets that fix, whether or not it solves the problem. Our first edit to run 3 described both layout bugs and the expected outcome:

Two layout problems. At 3.4s the Fernly wordmark runs off the right edge of the frame. From 13.5s the potted plant on the end card overlaps the end of "schedule.". I want the whole wordmark inside the frame with clear margin, and the plant fully clear of the headline so the end card reads cleanly. Keep everything else as it is.

A single message fixed both layout bugs and left the rest of the video as it was.

Append Each New Default to the Denylist

See which default the output used in place of the ones you banned, and add it to the list. The second edit added run 3's new default:

Add two more things to the avoid list: small uppercase labels above the headlines ("DAY 9 · NO WATER", "ANY PLANT, ONE PHOTO" and the rest), and the dash page indicators in the bottom-left corner. Remove both. Keep everything else as it is.

Labels and indicators removed; nothing else changed.

Each edit took under a minute.

When the Preview Never Loads, Report the Error

The generated code can fail at runtime. One of our three generations hung on "Loading preview…" because the script declared the same variable twice. One chat message describing the error and asking for no other changes fixed it in about 40 seconds.

Ship When the Video Does Its Job

Some gaps no prompt can close: real footage, a recorded voiceover, a licensed song, or a runtime beyond the tool's limit. opus6.video videos run up to 30 seconds and render silent, and opus6.video loads fonts only from Google Fonts and public CDNs, so a private brand font file won't load. For footage, audio or long cuts, move to Claude Code with a renderer such as Remotion, which can place your own video and audio files in a composition through its <Video> and <Audio> components.

FAQ

How Long Should an Opus 5.5 Video Prompt Be?

As long as it takes to fill all six fields. Run 3's brief needed 192 words for that, versus a 26-word median for the short prompts people share. On opus6.video the brief holds up to 2,000 characters, and format and length are set with buttons.

This article was drafted with AI assistance. opus6.video is built by the author.

Opus 5.5 Video Examples: 13 Code-Rendered Clips and Their Prompts

Jonathan Everleigh — Sat, 03 Oct 2026 06:00:23 +0000

Claude Opus 5.5 makes video by writing the animation as code. A browser draws that code one frame at a time, and the frames get encoded into an MP4. So the output behaves like motion design work: crisp typography, exact colors, mocked-up interfaces, charts, and shape-to-shape transitions.

Across 475 public Opus 5.5 videos, about six in ten are motion graphics, four in five are 16:9 landscape, and the median length is 30 seconds.

How an Opus 5.5 Video Gets Rendered

Veo, Kling, and Seedance output pixels. Opus 5.5 outputs a self-contained HTML file built on Canvas, SVG, CSS, GSAP, or Three.js. A headless browser then renders that file one frame at a time, and ffmpeg encodes the captured frames into the final file. Canvas shows up most often, in 336 of the 475 videos. SVG follows at 193 and Three.js at 141. Video isn't mentioned anywhere on the Opus 5.5 announcement page; creators worked out this use themselves.

Treating video as code has three practical effects:

Type renders as type and color values are literal. Put a hex code in the prompt and that exact hex code ends up in the frame.
Iteration is cheap. A scene change is a diff of a few lines.
Photorealism isn't on the table. Deedy Das, whose video appears below as #2, put it this way when talking about explaining technical ideas: "photorealistic video gen like Seedance is not very useful here" (post).

Left to its defaults, Opus 5.5 drifts toward centered text over a gradient with every element fading in. That default is why so many of the first videos looked interchangeable. The good ones share four traits you can spot in seconds:

The pacing varies: quick cuts alternate with beats that hold.
The type has hierarchy, with one dominant line, smaller supporting labels, and an obvious reading order.
Scenes are connected, so one shape becomes the next scene.
The clip resolves on an end card or a clean loop point.

Showreels and Motion Design

1. The One-Sentence Showreel Prompt Dozens of Creators Reused

From Stephan Livera's post: 16,983 likes, 15 seconds, 16:9.

The whole prompt fits on one line:

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 treated it as a portfolio piece, complete with a timecode HUD and chapter labels. One chapter plots six easing curves next to each other under the heading "Six ways to get from A to B." Another fills the frame with a tiling pattern on loop. A single word slams in at poster scale, and a red end card wraps it up.

The prompt sets a goal, a 15-second length, and an ambition level, then leaves every content decision to the model. That makes it a good test of the model's taste and a poor fit for anything tied to your own brand.

At least 90 public Opus 5.5 videos use this sentence or something close to it, among them reels from Ajith (4,057 likes) and Leon Abboud, and each one looks different. We gave Opus 5.5 the same sentence:

Our run of the same prompt: 15 seconds, 450 frames.

Stephan's version leaned on easing curves and tiles. Ours started with a bouncing ball that bursts into the word "MOTION," then cut to a wave made of 2,304 dots and a ring of points morphing from circle to square to star.

Launch Videos

2. A Startup Launch Film From a Single Vague Sentence

From Deedy Das's post: 3,264 likes, 26 seconds.

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

No company name was given, so Opus made one up: "muda," Japanese for waste. The film opens on a user stuck waiting 2.81 seconds for a response, shows a GPU cluster ramping to 94% utilization, and lands on a logo. Every scene has a small numbered label, the way keynote slides are chaptered. Nobody asked for a problem-product-proof-name arc; the model supplied it.

How it was made: the single sentence above. It took Deedy about a minute and roughly $2.

The product, every number on screen, and the brand name are fiction, so a real launch means feeding those in yourself.

3. A SaaS Launch Assembled From Real Product Assets

From Moritz Kremb's post: 418 likes, 46 seconds.

How it was made: Moritz told Opus to pick a product people know and pull its real assets from the internet.

I want you to create a highly professional SaaS product launch video. Go and find some SaaS, preferably just one that people know, so it's easier to identify with it. Pick that, and then make sure to get actual assets and images and all of that stuff from the internet.

Opus went with Notion and hit the standard launch-film beats: "Docs here. Chats there. Tasks everywhere." over drifting app icons, a rebuilt project board, a feature line paired with a chart, a strip of customer logos, and a closing card where a cursor clicks the call to action.

Those real inputs are where the specificity comes from. For your own product, give it screenshots, your headline, and your feature list. Notion owns the brand and logos in this one, so it only works as a demo.

4. A Print App Launch Shot as One Continuous Take

From zero's post: 2,103 likes, 29 seconds, 1:1.

This one is a long, structured prompt of several thousand characters, organized into <inputs>, <direction>, <structure>, <build>, <gotchas>, and <start> blocks. Here is how the direction block begins:

An Apple-keynote launch film, 2D only, one continuous take. Every scene is made out of the previous one: nothing fades, blurs or cuts. [...] Banned: crossfades, blur-ins, brightness "developing", 3D flips, particles, glows, holds longer than 1s, anything that looks like a template.

How it was made: the photos, music, and wall footage were the creator's own, and the prompt requests them up front. It also has Opus produce a beat map plus four still frames for review before writing the full film.

A button turns into a photo, a glass slider relights that photo to golden hour, the image travels from a phone to a browser window, and the sequence finishes as a framed print on live footage of a wall. The banned list strips out the template look faster than extra adjectives would.

These three launch videos follow the same arc: hook, product, a few features, end card.

UI Motion and App Walkthroughs

5. Nine UI States, One Morphing Element

From zero's post: 12,044 likes, 14 seconds, 1:1.

Dribbble-level UI motion. One shape, never cut: every state is the same element morphing its size, radius and color while its content swaps with a short blur. A cursor drives every change with real clicks and drags.

One black element cycles through a button, a checkmark, a music player, a volume slider, a toggle, a tab set, a chart, a ⌘K command palette, and a toast before returning to the button. Each transition is triggered by a cursor on the beat of a 120 BPM track, and the final frame matches the first, so the clip loops without a seam.

A single persistent object keeps the eye locked for all fourteen seconds. The states themselves are placeholders; for a real app you'd swap in your actual screens.

How it was made: zero supplied the music, and the prompt pins the tempo ("120 BPM, 7 bars, something happens on every beat"), which gives each morph a fixed slot on the timeline.

Social Ads and Identity Bumpers

6. A Vertical Fintech Ad for Social Feeds

From David Marcus's post: 283 likes, 23 seconds, 9:16.

make a punchy and modern short video for social that promotes @lightspark capabilities. Needs to be production grade with sound

Oversized type on a pale grid, one idea per screen: "Money still moves like it's 1973," then a USD-to-MXN transfer finishing "In seconds," then "For humans. And AI agents" and "The TCP/IP of money," then the logo. The whole pitch rests on one contrast, a 1973 date against an instant transfer, and every line reads on a phone with the sound off.

7. A 20-Second Kinetic Identity Loop

From TechHalla's post: 270 likes, 20 seconds, 1:1.

How it was made: a prompt that reads like a spec sheet, with the whole look written as numbers.

DURATION: exactly 20.00 seconds. LOOPABLE: frame 0 == frame last (position, opacity, cursor if any).
FORMAT: one HTML file, 1080×1080 (square, X-native). 60fps.
PALETTE (strict): bg #0A0A0A, magenta #FF2BD6, acid green #B8FF00 [...] No other hue

Heavy white type on black, acid-green characters scrambling until they settle into words, and a handle typing itself out over a magenta bar.

Replace the palette with yours and keep the numbers that tight. There isn't much room for content in a piece like this, so it fits best as an intro or outro.

Explainer and Data Story Videos

8. A Negroni Recipe, One Measured Pour at a Time

From Rory Flynn's post: 1,025 likes, 30 seconds, 1:1.

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.

The prompt left both the drink and the choice between JavaScript and HTML to Opus. It picked a Negroni. A hand-drawn glass fills in layers, with measurement ticks running up its side. A step card reads "1 oz GIN" or "20 SEC STIR," and a six-step tracker at the bottom checks off ice, gin, Campari, vermouth, stir, and peel as each happens.

The tracker is the piece worth reusing: any step-by-step video is easier to follow when the viewer can see which step they're on. Name the recipe or product you want; otherwise the model chooses.

9. Recursion, Taught in a New Genre Per Layer

From Ethan Mollick's post: 554 likes, 75 seconds.

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

Every explanation sits inside the previous one and jumps genre: corporate explainer, nature documentary, movie trailer, kids' TV. A "call stack" bar along the top gets one level deeper per layer, which turns the nesting into a visible data structure. At the end, the video plays inside itself under "STILL CONFUSED?"

10. A Timeline of Key Moments in AI History

From klöss's post: 192 likes, 2 minutes 52 seconds.

make a video highlighting key moments in the history of AI.

One line was enough for Opus to build a dark timeline with orange accents, split into numbered chapters: the 1943 artificial neuron rendered as a logic diagram, ELIZA's 1966 dialogue typed out on a terminal, and a bar chart for the 2012 ImageNet results. A caption strip at the bottom carries the narration, and the end card credits motion design, sound design, and code to Claude.

Timelines map well onto code animation because every moment reduces to text, a number, or a simple diagram. Opus generated all the dates and figures itself, so check them before publishing an explainer like this one.

Narrative and History Animations

11. The Human Story as an Origami Doodle

From songkeys's post: 423 likes, 1 minute 48 seconds.

Create a short origami / doodle-style animation showing humanity's development, progress, and civilization from birth to the present, and ultimately the hatching of AI. [...] Style: doodly, cute, warm, strongly narrative, no spoken language (simple text is OK, but don't use too much explanatory/narrative text, because I want different civilizations to be able to understand it), poetic, moving, high quality.

Soft paper-cut hills at sunrise lead into a first village, then the Earth at night strung with glowing icons, then network lines spreading across a village, and finally a sketchbook page where a pencil draws a small creature. Asking for "no spoken language" pushed the entire narrative into visuals, so the video works in any market without translation.

12. 250 Years of U.S. History in Sand

From Michael Guo's post: 349 likes, 2 minutes.

Make a 2-minute sand animation that tells the story of 250 years of U.S. history. Keep it lively, engaging, and tasteful. Add appropriate background music and sound design.

Grainy sepia silhouettes with a year stamped in the corner of each scene: wagons rolling west in the 1840s, a steamship gliding past the Statue of Liberty in 1886 beneath the line "Give me your tired, your poor...", the crowds of 1963, and fireworks over "250, 1776-2026." From the two words "sand animation," Opus derived the sepia grain, the silhouettes, and scene transitions that look like sand being swept.

13. Four Seasons Through a Train Window

From Ole Lehmann's post: 264 likes, 30 seconds.

4 seasons passing outside a train window, a cozy carriage, a cup of coffee on the table, Grand Budapest Hotel style

A locked, symmetrical frame of purple curtains, two table lamps, and a coffee cup never moves, while the view outside cycles through spring, summer, autumn, and winter and back to blossom, with a pink hilltop palace in the distance. Four words of film reference brought the symmetry, the pastel palette, and the pink building.

Each of the three narrative pieces names a medium or a reference: origami, sand, a Wes Anderson film.

Patterns Across the 13 Prompts

The one-sentence showreel prompt gave polished reels that could belong to anyone. The launch videos that pass for a real company had real inputs behind them: an actual product, screenshots, a palette, photos or footage from the creator. Rexan Wong's summary: "everyone has the same model. the context you give it is what makes it look pro" (post, 6,730 likes).

Six of the 13 prompts specify a duration or a tempo, and that group contains the two most-liked videos in this list (#1 and #5). Across all 475 public videos, half run between 15 and 43 seconds. Leave the length out and Opus decides on its own: klöss's one-line history prompt gave no duration and returned a video just under three minutes long.

The creators also named styles: origami, sand animation, Grand Budapest Hotel, Apple keynote, Dribbble-level UI motion. Each of those names encodes a palette and a pace that would take a full paragraph to spell out.

The longest prompts put a planning step ahead of the animation. They ask for a beat map, a list of states, or still frames before code gets written, so problems show up while they are still cheap to fix.

Time and cost range widely. At the fast end, about a minute and $2 (Deedy Das). At the slow end, about eight hours for a launch video whose soundtrack was itself written in code (Leon Lin). Between those: 15 minutes (Chain), 19 minutes including two revisions (David Ch), and three prompts (Miles).

Limits of Code-Rendered Video

It can't film anything. For a realistic person or location you need a camera or a video generation model like Veo or Seedance. Opus can edit that footage and layer type and graphics over it, but only in a setup that can load video files, for example Claude Code with Remotion, where the <OffthreadVideo> component drops clips into a composition. The browser tool covered below works from a text description and doesn't accept video input.
It won't record songs or voiceovers. In #4 and #5 the creators brought the music and Opus synced the animation to it. Opus can generate audio in code, as Leon Lin did for a full soundtrack and sound effects, but a recorded track or voiceover has to come from another source.
It doesn't know your brand. Without a reference, a logo, and a palette, output slides back toward the same centered-text look.

Make Your Own Opus 5.5 Video

Choose an entry point based on what you already have:

To test what the model does on its own, run the showreel prompt from #1.
To announce a product, reuse the launch structure from examples 2 through 4 with your product name, three features, and brand colors.
For more than 30 seconds, or for your own footage and audio, work in Claude Code with a renderer such as Remotion or HyperFrames.

Option 1: Run Your Own Render Pipeline

Pair Claude Code with a pipeline that opens the HTML in a headless browser, captures every frame, and encodes with ffmpeg. The Hugging Face walkthrough has the setup details. This path supports long videos, audio, and footage.

Option 2: Use a Hosted Browser Tool

opus6.video runs Claude Opus 5.5 on its side, so there's no Claude subscription and nothing to install. Write a description or start from a template like Designer showreel, App launch video, or Product walkthrough, then choose 16:9, 9:16, or 1:1 and a length of 10, 15, or 30 seconds. Opus 5.5 drafts a storyboard and writes the scenes, you iterate in chat, and the result downloads as a 1080p MP4. Each video maxes out at 30 seconds, and exports have no audio, so music goes in during editing.

The same site keeps a gallery of finished videos next to the prompts that made them.

FAQ

Is There a Length Limit on Opus 5.5 Videos?

Not when you render locally; the examples here span 14 seconds to almost 3 minutes. Render time grows with length, because each frame is drawn and captured individually. The hosted browser tool above caps each video at 30 seconds.

Can These Prompts Be Reused?

Yes, as templates. Replace the product, subject, and palette with your own. The videos belong to the people who made them, so link back to their original posts.

This article was drafted with AI assistance. opus6.video is built by the author.

Best Free AI Image Generator in 2026: 10 Tools Tested on Their Free Plans

Jonathan Everleigh — Mon, 21 Sep 2026 08:51:44 +0000

"Free" means something different on every platform. Here's what 10 AI image generators actually give you without paying a cent.

Image generated by Free AI Image

On some tools, free means a fresh batch of images every day. On others, it means 10 credits total, ever. Some stamp a watermark on everything. Some quietly post your images to a public gallery. And a few really are free, with no limits at all.

So I tested 10 AI image generators on their free plans only, with no credit card and no trial upgrades.

Here's what each one actually gives you.

Quick answer:

No account needed: Free AI Image, or Stable Diffusion on your own machine
Most generous refill: Grok Imagine, about 10 images every two hours
Stingiest free plan: Adobe Firefly, 10 credits once and never again
Adds a watermark: Gemini, Bing, and Recraft
Publishes your images publicly: Ideogram, Recraft, and Leonardo
Not licensed for commercial use: Recraft and Leonardo

How I Tested

I checked the same four things on every tool:

Free limit: whether it refills, and on what schedule
Watermark: whether the free plan adds one, and how visible it is
Privacy and rights: whether free images are public, and whether you can use them commercially
Getting started: whether you need an account, and how many steps it takes to reach your first image

I checked every limit in September 2026. Free plans change often, so I'll keep this list updated.

Disclosure: Free AI Image is our own tool. It went through exactly the same tests as everything else here.

1. Free AI Image

Best for: getting an image fast, without an account

Most tools on this list ask you to sign in before your first image. Free AI Image doesn't. You open the page, type a prompt, and download the result.

The prompt box sits right on the homepage. Write your prompt, choose an aspect ratio (1:1, 3:4, 4:3, 9:16, or 16:9), and click "Generate free image."

To edit a photo instead, upload a PNG, JPG, or WebP file (up to 10MB) and describe the change.

The site also includes one-click tools for the jobs that usually come right after generation: a background remover, an upscaler, an object remover, an image extender, and a resizer.

Where it falls short: the free tier runs on Z-Image Turbo for text-to-image and FLUX Klein 4B for photo edits, both tuned for speed rather than maximum detail. That's the trade. It's built for everyday images, a blog header, a quick mockup, a placeholder in a deck. When the image itself has to hold up to close inspection, Gemini and ChatGPT (below) go further.

Two smaller things. Each request returns one image, not a batch of variations. And normal use isn't capped: the free model doesn't spend credits, and the rate limit that exists is there to stop scripted abuse, not ordinary clicking.

Sign-up: Not needed
Free limit: No cap for normal use
Watermark: None
Commercial use on free plan: Yes

2. ChatGPT

Best for: editing images through conversation

ChatGPT's image model is one of the strongest available right now, and free users get the same model, just with tighter limits.

What sets it apart is context. Because it works inside a chat, you can refine an image step by step: generate it, then say "make the raincoat red" or "move the dog to the left," and it changes that detail while keeping the rest.

To start, open ChatGPT, sign in with a free account, and describe the image you want.

Tip: change one thing per message. Asking for three edits at once makes it more likely to redraw the whole image.

The limits: OpenAI doesn't publish a free cap, and it moves with server load. In practice the free plan is a few images a day, at low priority. Generation is also slower than most tools here, and you get one image per request.

Sign-up: Free account
Free limit: Undisclosed, a few images a day
Watermark: None
Commercial use on free plan: Yes, you own the output

3. Google Gemini (Nano Banana 2)

Best for: realistic images and photo edits

Nano Banana 2 is Google's image model, built into Gemini. For a free model, its realism is good, and it follows detailed prompts closely.

It's especially strong at editing. Change one thing in a photo and everything you didn't mention stays exactly as it was.

Tip: Gemini has almost no settings panel. Put format instructions right in the prompt, like "16:9, wide shot."

The free plan refills every day, at around 20 images. The bigger catch is the watermark: Gemini stamps a visible one on everything it generates, which rules it out for anything you publish as-is.

Sign-up: Free Google account
Free limit: Refills daily, around 20 images
Watermark: Yes, visible
Commercial use on free plan: Yes, Google doesn't claim ownership

4. Microsoft Bing Image Creator

Best for: comparing several models for free

Bing Image Creator puts several image models in one free interface, so you can run the same prompt through each and keep the best result.

Speed is the trade-off. You get 15 fast generations a day, and after that it keeps working, just slower. There's also a ceiling of 200 prompts in 24 hours, and edits count against it.

Its content filters are the strictest here. Editing is locked to one model too: upload an image and GPT-4o takes over automatically. And every image carries a visible watermark plus Content Credentials metadata.

Sign-up: Free Microsoft account
Free limit: Refills daily, 15 fast generations
Watermark: Yes, visible
Commercial use on free plan: Yes, but not exclusive

5. Ideogram

Best for: posters, thumbnails, and anything with words

Most AI image generators still mangle text. You ask for "OPEN LATE" and get "OPNE LAET."

Ideogram is the exception. Its model is built to render readable text, which makes it the best free option when the words have to come out right.

The free plan is limited, though. You get a dozen slow credits a day, you wait in a queue, and every image is public by default. That's fine for a blog thumbnail, but not ideal for a client project.

Sign-up: Free account
Free limit: Refills daily, 12 slow credits
Watermark: None
Commercial use on free plan: Yes, but images are public

6. Recraft

Best for: logos, icons, and vector graphics

Recraft outputs real vector files (SVG). For logos and icons, that matters: a vector scales to any size without getting blurry.

Create a free account at Recraft, choose "Vector" as the image type before you write the prompt, and generate.

You get 30 credits a day, refilled whether you used them or not.

The catch is ownership. On the free plan Recraft keeps the rights to what you generate, your images land in a public gallery, and commercial use isn't allowed. Use it for personal projects and prototypes, and upgrade before anything goes into a real brand.

Sign-up: Free account
Free limit: Refills daily, 30 credits
Watermark: Yes
Commercial use on free plan: No

7. Leonardo AI

Best for: fine control over models and settings

Leonardo gives you more control than anything else here: multiple models, style references, character consistency, and detailed settings for size and quality.

After signing up at Leonardo, open the Image tool, pick a model, set the dimensions, and generate.

The free plan gives you 150 Fast Tokens a day, but premium models burn through them fast. In practice that's a handful of images.

Tip: to stretch your tokens, test prompts on a cheaper model first, then switch to a premium model for the final image.

Like Recraft, the free tier is public: other people can see what you generate, and Leonardo keeps broader usage rights. It's not the place for confidential work.

Sign-up: Free account
Free limit: Refills daily, 150 Fast Tokens
Watermark: None
Commercial use on free plan: No

8. Adobe Firefly

Best for: images you can use commercially without worrying

Adobe trains its own Firefly models on licensed and public-domain content, and markets them for commercial use. If your company has rules about where images come from, that matters more than a few points of image quality.

Sign in at Firefly and write your prompt. Generated images move into Adobe Express and Photoshop without a download step.

Tip: check which model is selected. Firefly also hosts partner models, and those carry different licensing terms than Adobe's own.

The free plan is the strictest here, and it's strict in an unusual way: you get 10 credits once, not 10 a day. A basic generation costs one credit, larger images cost more. When they're gone, they're gone.

Sign-up: Free Adobe account
Free limit: 10 credits, one-time
Watermark: None
Commercial use on free plan: Yes, on Adobe's own models

9. Stable Diffusion (Running Locally)

Best for: unlimited, private generation

Stable Diffusion is an open-source image model. You can download it and run it on your own computer, which means no account, no daily limit, and no one else seeing your images.

Setup is the hard part. You install an interface such as ComfyUI, download a model, and launch it locally. The GitHub README for each interface covers the installation steps.

The main requirement is hardware: you'll need a capable GPU.

Licensing depends on the model you download, so check its license before commercial use.

Sign-up: Not needed
Free limit: None (your hardware is the limit)
Watermark: No
Commercial use: Depends on the model license

10. Grok Imagine

Best for: a quota that resets in hours, not days

Every other online tool here makes you wait until tomorrow. Grok refills about 10 images every two hours, which is the difference between stopping work and taking a coffee break.

Open Grok, switch to image generation, and write your prompt.

xAI is clear about rights: you own what you generate and can use it commercially. The one condition is labeling. xAI asks that you mark content as created with Grok.

Sign-up: Free account
Free limit: About 10 images every 2 hours
Watermark: None, but xAI asks you to label output
Commercial use on free plan: Yes, with labeling

Side-by-Side Comparison

Tool	Best for	Sign-up	Free limit	Watermark	Commercial use (free)
Free AI Image	Fast start, no account	No	No cap for normal use	None	Yes
ChatGPT	Editing by chat	Free account	Undisclosed, a few a day	None	Yes
Google Gemini	Realistic images	Google account	~20 a day, refills	Visible	Yes
Bing Image Creator	Comparing models	Microsoft account	15 fast a day, then slower	Visible	Yes, non-exclusive
Ideogram	Text in images	Free account	12 slow credits a day	None	Yes, but public
Recraft	Vector graphics	Free account	30 credits a day	Yes	No
Leonardo AI	Fine control	Free account	150 tokens a day	None	No
Adobe Firefly	Commercially safe images	Free account	10 credits, one-time	None	Yes
Stable Diffusion (local)	Unlimited, private	No	Unlimited	No	Depends on model
Grok Imagine	Fastest quota reset	Free account	~10 every 2 hours	None	Yes, with labeling

A note on the watermark column: some tools label images to mark them as AI-generated, others do it to nudge you toward a paid plan. Either way it's the hardest thing on this table to work around.

How to Choose

Start with your constraints, not with which tool is "best."

You want one image and you're not signing up for anything: Free AI Image.
You need a lot of images in one sitting: Grok Imagine first, then Bing. Bing slows down instead of stopping.
The image is going into paid work: skip Recraft and Leonardo. Their free plans don't license commercial use.
The work is confidential: skip Ideogram, Recraft, and Leonardo. Free-plan images on all three are public.
A watermark would be a problem: skip Gemini, Bing, and Recraft.
Your company asks where the training data came from: Adobe Firefly, on Adobe's own models.

One more practical point: free limits reset on different schedules. Grok comes back in two hours, most others tomorrow, and Firefly never does. When one runs out, switching is usually faster than waiting.

Final Thoughts

No free plan here is generous in every direction. Every one of them gives something up: an account, a watermark, a public gallery, a quota that never refills. But between these 10, there's one that gives up the thing you don't care about.

If you want to see how little it takes to get started, Free AI Image needs no account, no credit card, and nothing to install.