Claude · 9 min read
3D animation with Claude Fable 5.2: Three.js, Blender and frame-perfect renders
A practical workflow to turn Claude Fable 5.2 code into 3D animation MP4s: deterministic Three.js with renderAt(t), Playwright capture, ffmpeg, and headless Blender.
By Claude Video Team ·
Claude Fable 5.2 can write impressive 3D scenes, but a scene that looks good in a browser is not a video yet. The difference between a choppy screen recording and a clean MP4 is one rule: every frame must be computed from time, not from the clock. This guide shows the setup that makes Fable 5.2 output render perfectly, every time.
Rule 1: ask for a deterministic scene
A browser animation normally advances with requestAnimationFrame and the wall clock, so a slow frame means a dropped frame. For video you want the opposite: a function that draws exactly the frame at time t. Put this requirement in your prompt.
Make a single self-contained three.js HTML page that renders a 12-second animation
at 1280x720, 30 fps. It must be deterministic: no requestAnimationFrame clock,
no Math.random without a fixed seed. Expose window.renderAt(t) that renders the
exact frame at t seconds. Create the WebGLRenderer with preserveDrawingBuffer: true.
Scene: [describe your scene, camera move and lighting].Rule 2: capture frames, then encode
With renderAt(t) in place, a short script loads the page in a headless browser, renders each frame and saves it as an image. ffmpeg then turns the frames into an MP4.
// capture.mjs (npm i playwright, then: npx playwright install chromium; mkdir frames)
import { chromium } from 'playwright';
const fps = 30, seconds = 12;
const browser = await chromium.launch();
const page = await browser.newPage({ viewport: { width: 1280, height: 720 } });
await page.goto(`file://${process.cwd()}/scene.html`);
for (let i = 0; i < fps * seconds; i++) {
await page.evaluate((t) => window.renderAt(t), i / fps);
await page.screenshot({ path: `frames/${String(i).padStart(5, '0')}.png` });
}
await browser.close();ffmpeg -framerate 30 -i frames/%05d.png -c:v libx264 -pix_fmt yuv420p -crf 18 out.mp4Because each frame is rendered on demand, the result is smooth regardless of how heavy the scene is; heavy scenes just take longer to capture.
Rule 3: for physically lit 3D, use Blender headless
When you need real lighting, materials and depth of field, ask Fable 5.2 for a Blender Python script that builds the scene, sets the camera and render settings, and renders the animation. Run it in the background with Blender’s command line.
blender -b -P build_and_render.py- Ask the script to set the output path, resolution, frame range and render engine (Eevee for speed, Cycles for realism).
- Render a single test frame first, check it, then render the full range.
- Long Blender pieces can take hours to render; creators report runs of several hours for complex shots.
Prompting tips that make the difference
- Specify duration, resolution and frame rate up front.
- Describe the camera: one move per shot, slow push-ins and gentle orbits read as premium.
- Name the materials and lighting (chrome, glass, studio three-point light) instead of “make it look good”.
- Ask it to review its own rendered frames and fix what reads badly. Fable 5.2 has improved vision.
- Lower the effort for simple pieces: thinking is always on with Fable models and counts as output tokens.
Known limits
Code-based 3D is excellent at structure, typography, camera work and timing. Realistic human faces and skin remain hard; that is still the territory of generative video models.
Skip the pipeline
If you do not want to maintain capture scripts, Claude Video does the rendering for you: pick Claude Fable 5.2 as the director, ask for 3D titles, device shots, particle morphs or custom scene code, and export MP4 up to 4K with music.