001A comparison of Earth, planets, stars, and galaxies, zooming out to the observable universe.
02:571:1Silent preview
← All projectsCLAUDE CODE PLUGIN / 3D MOTION
FROM AN IDEA. INTO MOTION.
Prompt
Film.
From the words you write
to scenes that move.
Run in order inside Claude Code
01 / IDEA02 / SCENE03 / FILM
Scroll to explore
WORDS BECOME WORLDSDescribe the film
Describe the film
you have in mind.
PromptFilm is a video production plugin for Claude Code. It researches the subject, plans the scenes, and builds a 3D HTML film for the browser. Review and revise the result, then export to MP4.
Run these in order inside Claude Code.Choose an installation scope, then restart Claude Code or run /reload-plugins.
9:1616:91:14:5HTML + MP4
EXAMPLES
Example videos
Previews play as you scroll into view.
Click to watch the original in full.
001
002A zoom from a data center through a GPU, core, and transistor to silicon atoms.
02:341:1Silent preview
003Based on a film scene about discovering a new element. A model is scanned, broken into particles, and rebuilt as a nucleus.
00:499:16Silent preview
WORKFLOW
Production workflow
The workflow runs from source research
to video export in these steps.
Research
Research the subject and distinguish verified facts from illustration. Choose the aspect ratio, duration, and caption languages.
Storyboard
Plan each scene’s composition, camera movement, and captions. Review the storyboard before production.
Build and review the HTML
Build the scenes and motion with Three.js in an HTML file. Check loop transitions, captions, pacing, and rendering errors.
Revise and export
Comment on frames and adjust playback speed in Studio. Export the reviewed result as MP4. A separate SRT caption file can be produced on request.
PROMPTFILM STUDIO
Leave comments
on the frame.
In Studio, attach revision comments to a time and position in the frame. Claude Code reads those comments and edits the scene.
Frame-pinned commentsTimeline & pace controlMP4 · PNG export
PromptFilm StudioREVIEW MODE
1COMMENT 01 · 02:08
Reduce the zoom speed
in this section.
▶ 02:08 / 02:34Illustrative preview
HOOKEXPLOREKEYRETURN
IN DEPTH
In depth
How a film gets made, what it takes in time and resources, and what keeps the result honest.
A real film, not a slideshow
The output is a real-time Three.js film in a single HTML file: studio lighting, physically based materials and one continuous camera, looping seamlessly. When you want it, it exports a frame-exact 1080p 60 fps MP4. Aspect ratios are 9:16 (Shorts, Reels, TikTok), 16:9, 1:1 or 4:5, with captions in one or two languages.
How one film is made
- Ask — one kickoff question about research depth, aspect, length and caption languages; then it works on its own.
- Research — sourced facts, reference photos and frames from reference videos.
- Storyboard — scene cards with a time budget, opened in the Studio for your approval.
- Build — Claude writes the film on the bundled engine.
- Check — automated QA, a visual review by a separate agent that didn’t build the film, and a final gate; it fixes and re-checks until the gate passes.
- Deliver — every HTML version is kept, plus an MP4 when you want one.
Every number on screen has a source, and anything not public is marked as illustrative. The films page lists the sources and illustrative parts of all three examples.
Time and resources
A film takes hours of agent work and a lot of tokens: research, building and several rounds of checks.
- The only thing to install yourself is Node.js 20+. The first run checks for the rest (script packages, a headless Chrome, ffmpeg) and installs what is missing, with no admin rights and without removing anything.
- 8 GB of memory is enough. Checking a film runs one headless browser (about 1.4 GB, 2.6 GB for a data-heavy film).
- Without a GPU, Chrome falls back to software rendering, which is slow. Developed and tested on macOS (Apple Silicon).
Reviewing in the Studio
A local Studio page opens while the film is being made. Scrub the timeline, click right on the frame to leave a comment, and Claude receives it with a snapshot, fixes it and replies. You can change the pace of any section, and those edits survive rebuilds. The Studio listens only on 127.0.0.1.
FAQ
How do I check my setup?
Ask Claude Code to “run the promptfilm selftest.” In about five minutes it builds the engine’s test films in a temporary folder and runs every check, including ones that must catch planted faults.
Where are films saved?
In your working folder, one folder per film (./film-name/). Your kickoff answers are saved in ./.promptfilm/settings.json and offered first next time.
CLAUDE CODE PLUGIN
Install and get started
Run two commands in Claude Code.
Add the marketplace, then choose a scope in the plugin installation screen. Choose user scope for your own work.
- Add the marketplace
- Install the plugin
- Reload after installing
You can also restart Claude Code. Then run /promptfilm:promptfilm or describe the video you want to make.
Read the full guide on GitHub ↗Install from a terminal in one line
/PROMPTFILM:PROMPTFILM
/promptfilm:promptfilm Create a 3D journey from Earth to the observable universe, comparing objects at their true scale.
Requirements
Claude Code · Node.js 20+ · FFmpeg · Chrome/Chromium · Python 3
FFmpeg is used for MP4 export; Chrome for QA and rendering. Developed and tested on macOS Apple Silicon.
What files does it produce?
Create browser-based 3D HTML, review and revise it in the local Studio, then export MP4 or PNG. Captions are part of the film; SRT is available on request. The autoplay previews are MP4 recordings of the actual HTML; click to view the HTML original.
Where can I use it?
This is a Claude Code plugin. After installation, check that /promptfilm:promptfilm is available. You can list installed plugins with claude plugin list in your terminal.
How do I update it?
Run this in your terminal, then use /reload-plugins in your open Claude Code session or restart it.
How does production work?
Research, scene planning, production, and review run in sequence. Complex scenes take longer. Expect to review the storyboard and revise the result.