Make a 3D product ad with Claude Code and headless Blender on an old GPU
by PaperChaseWebb
A 15-second, four-shot product spot rendered on a 2016 graphics card. Claude Code wrote the whole Blender scene in Python, Blender rendered it with no window open, and ffmpeg put the shots, music and overlay together. The builder posted the render times and what broke.
- Price
- Free
- Difficulty
- Intermediate
- Setup
- 30 min
- Format
- .md file
make-a-3d-product-ad-with-claude-code-and-headless-blender-on-an-old-gpu.md · 2 KB · direct download, no signup
What you end up with
Expect several rounds, not one prompt.
What you get
- A plain-language summary of the workflow
- A fill-in prompt template
- What to watch out for
- A link to the original source
Who it is for
Builders who already use AI agents and want a proven workflow they can copy into their own project.
Works with
Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free with the agent plan you already use.
Time to result: One working session
How it works
Write a shot list: duration, camera move and what the viewer should no
Write a shot list: duration, camera move and what the viewer should notice per shot
Expected: Done before you move to the next step.
Ask the agent for one Python scene script and run it with blender -b -
Ask the agent for one Python scene script and run it with blender -b --python
Expected: Done before you move to the next step.
Render three test frames per shot and fix materials before the full re
Render three test frames per shot and fix materials before the full render
Expected: Done before you move to the next step.
Render each shot with one animation call, not a loop over frames
Render each shot with one animation call, not a loop over frames
Expected: Done before you move to the next step.
Join shots, music and text with ffmpeg and keep the render log
Join shots, music and text with ffmpeg and keep the render log
Expected: Done before you move to the next step.
Sample prompt from the pack
Apply this workflow to [your project]: 1. Write a shot list: duration, camera move and what the viewer should notice per shot 2. Ask the agent for one Python scene script and run it with blender -b --python 3. Render three test frames per shot and fix materials before the full render 4. Render each shot with one animation call, not a loop over frames 5. Join shots, music and text with ffmpeg and keep the render log Stop and ask me before anything irreversible: deploys, payments, sends or deletes.
Adapted by PaperChaseWebb. Not the original author's prompt.
Free preview of the file
# Make a 3D product ad with Claude Code and headless Blender on an old GPU PaperChase agent use case (free feed entry), version 1.0. Source: [@0xFizzu on X](https://x.com/0xFizzu/status/2114356857372352630), 2026-10-25. ## What they did 450 frames at 1080x1350 took about 23 minutes on a GTX 1050 Ti, about 3 seconds a frame. The first draft lost the liquid because EEVEE could not refract through two glass layers, and the label floated until it was wrapped onto an invisible cylinder. Rendering the animation in one call instead of a frame-by-frame loop cut test shots from 11.5 to 3.9 seconds per frame. The bottle took four rounds and one shot needed three reframes. They chose plain headless Blender over a Blender MCP because the shot list was fixed. ## Worth knowing Expect several rounds, not one prompt. Render a few test frames per shot before the full pass, and render with a single animation call. A fixed shot list does not need a live MCP link to Blender; a script is simpler.
Worth knowing
- Expect several rounds, not one prompt. Render a few test frames per shot before the full pass, and render with a single animation call. A fixed shot list does not need a live MCP link to Blender; a script is simpler.
- Figures are as reported by the original author and were not re-measured by us.
Questions
Where does this come from?
A public post credited to @0xFizzu on X. Source: https://x.com/0xFizzu/status/2114356857372352630
Is it free?
Yes. Feed entries are free to read and download.
Details
Version 1.0 · Updated Oct 26, 2026 · Markdown version of this page
License: Personal and commercial use. Credit the original source when you share the workflow. Download terms
Related
Video Production with AI Agents: lanes, prompts, skills and render checks
A Markdown playbook for making finished videos with Claude Code or Codex: pick a lane (draw in code, edit footage, script 3D or generate), plan with a shot list, render test frames, and make the agent check every render before you see it.
Check every render before you trust it (free sample)
One rule, one skill and four ffmpeg commands that make Claude Code or Codex look at its own video output (frames, cuts, loudness, captions) before it tells you it is done.