Want to access all premium content?
Become a paying subscriber to get access to all courses, guides like this, prompts and skills library, and $500+ worth of AI tools.
Opus 5.5 can build a 3D scene in code, render it inside Claude, and add sound timed to the animation. Your design system supplies the colors, fonts, and components.
We'll make a 14-second launch film for Fernway, a fictional road-trip planner. It opens with the problem, follows a route through three stops, and ends with the app on a phone screen. You'll need the Claude app with Opus 5.5 on an eligible paid plan, code execution enabled, and a design system or brand sheet.
Step 1: Open a render chat. Check that Claude can render a short video.
Step 2: Load your brand. Put your design rules into one file.
Step 3: Write the story. Plan the shots and review twelve stills.
Step 4: Render with sound. Build the video and audio from one timeline.
Step 5: Fix it by frame. Make specific edits, then export a vertical version.
Step 1: Open a render chat
Open Settings, then Capabilities, and enable code execution. Claude will run the rendering tools in its workspace, so nothing needs installing on your computer.
Start a chat with Opus 5.5 and paste:
In your workspace, install Three.js and make one HTML page with a spinning rounded box, one light, and a soft shadow.
Render 30 frames at 1280x720 using headless Chromium through Playwright. Encode them as a one-second MP4 with ffmpeg and send me the file.
If a required tool isn't available, report the error instead of claiming the render worked.Open the MP4 and check that the box moves, the lighting is visible, and the file plays.
If Chromium fails, ask Claude to check whether WebGL can run through SwiftShader. Get this test working before building the full scene.
Step 2: Load your brand
Ask Claude to turn your design system into a file the animation can use:
Read my [BRAND NAME] Design System and create brand.json.
Include:
- Colors as hex codes with their roles
- Display and body fonts with weights
- Corner radii for cards, buttons, and the phone frame
- Button and card styles
- The approved logo asset, if available
Check which fonts are available in your workspace. Suggest substitutes for missing fonts, but wait for my approval before using them.
List anything the film needs that the design system doesn't define.
If Claude can't access the system, attach your brand sheet and logo instead.
Review the missing details before continuing. A website's guidelines may not define a sky color, glow, or 3D materials. Agree on those additions now.
Check the font names too. An unnoticed fallback can change every title and card.
Step 3: Write the story
This version turns a messy planning process into one clear route. Replace the six product fields below, then adjust any shots that don't fit your product.
Make a 14-second launch film for [PRODUCT].
Use brand.json for the colors, fonts, and components.
Use only our approved branding.
PRODUCT: [what it does and who it's for]
CHAOS: [12 short messages, tabs, or tasks showing the problem]
JOURNEY: [the route or process the product simplifies]
STOPS: [three places, stages, or benefits]
ACTION: [the final button label]
END: [tagline and CTA]
FORMAT:
1920x1080, 30 fps, 14 seconds, 120 BPM.
Use a Three.js scene with a text layer.
Render in your workspace with Playwright and Chromium.
Keep all event times in timeline.py. Export those times for the animation and use the same data for the sound.
SHOTS:
0-2 s: Four short problem statements, one per beat, on full-screen brand colors.
2-3 s: The CHAOS objects swirl together into one glowing point.
3 s: On the drop, the point becomes the JOURNEY line across a 3D map. Our logo appears.
4.5, 5.5, 6.5 s: The camera follows the line as each STOPS card rises.
7-8 s: Four fictional avatars join a poll until it reads 4/4.
8.5-10.5 s: The camera rises overhead and the map shrinks into a phone screen.
11 s: The ACTION button is pressed, followed by a ripple and confirmation.
11.75-14 s: The phone moves left and the tagline appears right. Fade from 13.4 s.
LOOK:
Bright sky gradient, cream terrain, soft contour lines, turquoise sea, and our accent color for the route.
Use dark text on light cards. Limit bloom to the glowing route head.
CHECKS:
Before rendering the full film, send one contact sheet with stills at:
0.3, 1.1, 2.6, 3.2, 4.0, 4.7, 5.7, 7.6, 9.2, 10.3, 11.3, and 12.8 seconds.
For Fernway, the journey runs from San Francisco to Los Angeles, with three trip cards along the coast.
A course could follow three modules. For a physical product, replace the map and phone ending with shots that show how the product works.
Check the stills for readable text, consistent colors, and clear framing. Each should show the intended moment: the problem, the route, a stop, the phone, or the final action.
Fix these before rendering all 420 frames. Still images are quicker to review, though you'll need the video to judge pacing.
Step 4: Render with sound
Once the stills look right, paste:
Render all 420 frames and add sound synthesized in Python with numpy and scipy. Use no external samples or voice services.
Include:
- A short hit on each opening line
- A riser into the 3-second drop
- A bass hit and crash on the drop
- A 120 BPM beat after the drop
- A pluck for each stop card
- A blip for each vote
- A ding on the button press
- A held chord under the tagline
Read all event times from timeline.py.
Report peak levels and half-second RMS levels in dBFS. Keep the mix free of clipping, with the drop as the strongest accent.
Mux the audio into the MP4 as AAC and send the file.
Watch the drop at 3 seconds. The route reveal and bass hit should land together. At 30 fps, that event starts at frame 90 when counting from zero.
Listen at a comfortable volume. The opening hits should leave room for the drop, and the later effects shouldn't overpower it.
Use the level report to find unexpected spikes. Name the moment you want changed: “Lower the vote blip at 7.5 seconds by 3 dB.”
Step 5: Fix it by frame
Give each note a time, an object, and a clear change.
“At 5.7 seconds, the Big Sur card is unreadable because it's glowing” is enough for Claude to investigate. You don't need to diagnose the shader yourself.
These notes address problems found in the example film:
Problem | Note to send |
The scene looks too dark | Brighten the sky and terrain while preserving the brand palette |
Colors don't match | Compare the scene colors with brand.json and list any additions |
Black blocks appear | Inspect the shader around this frame for invalid values before changing the lighting |
Cards glow too much | Exclude the cards from bloom or reduce their brightness |
The phone view looks washed out | Reduce the distance fog during the overhead-to-phone transition |
A card leaves the frame | Adjust its position or fade it before the camera passes |
Ask for another contact sheet after each round. For a change affecting only one section:
Re-render frames 135-215 with the fix. Keep the other frames and existing audio, then encode a new MP4.
If the change affects frames outside that range, tell me before rendering.Then make the vertical version:
Make a 1080x1920 version for Reels and Shorts.
Keep the timing and sound. Reframe the camera and cards for the tall canvas, and place the tagline above the phone at the end.
Send a contact sheet before the full render.
Use cases
Once your first film works, reuse the parts that work and change the story for these three launches.
Use case #1: Launch a course
Turn scattered learning material into a path through your modules.
Adapt the film for my course, [NAME].
CHAOS: saved posts, unread tabs, unfinished videos, and scattered notes.
JOURNEY: first lesson to finished project.
STOPS: [MODULE 1], [MODULE 2], [MODULE 3].
ACTION: Start module 1.
Keep the 14-second timeline and send a contact sheet first.Check that module titles remain readable while the camera moves.
Use case #2: Announce a feature
Give one feature the whole film.
Make an eight-second version for [FEATURE].
Keep the drop at 3 seconds.
Reveal one feature card at 4 seconds.
Move into the phone at 5 seconds.
Press the action button at 6 seconds.
Show the tagline from 6.5 seconds.
Update the timeline and sound together.Watch the transitions and listen for effects left over from removed shots.
Use case #3: Make a teaser
Keep the opening and save the reveal for launch day.
Make a six-second teaser using the four opening lines and the drop.
End on our logo and [DATE].
Export a 16:9 MP4 under 15 MB.Check the date, file size, and final frame before posting.
Confirmed limitations
This workflow uses code execution rather than Claude Motion. It depends on the tools available in your chat workspace, so run the one-second test first.
In our test, the full render took about 11 minutes across four batches and can take 20 in one. Timing varies with the scene and workspace; review stills and reuse unchanged frames where possible.
Claude can misread brand details or produce rendering errors. Check brand.json, inspect the stills, and play the exported file.
This sound setup creates synthesized effects and music. It doesn't include recorded instruments or a voiceover.
The original guide was checked on October 23, 2026. Model access, plans, and workspace tools may change.
Closing
Start with the Fernway example and review the twelve stills before committing to the full render. Get the colors, cards, and camera framing right, then check the movement and sound in the MP4.
Then bring in your own product and brand files. Keep the timing where it fits, change the shots where it doesn't, and finish with a version framed for the platform you'll post on.
See you in the next one :)