3D productionpipeline
Bringing a systems approach to creative production: a repeatable path from a script to a rendered 3D episode.

Fact sheet
- Engine
- three.js inside Remotion
- My work
- Pipeline automation
- Output
- Vertical 1080×1920, up to 4K
- Domain
- 3D animation
01The problem
A rendered episode is the result of many linked decisions: the script, scene, camera, animation and output. Repeating those steps by hand makes production harder to maintain and reproduce.
02The engineering
I built automation for a pipeline using three.js inside Remotion. The workflow connects plain-text scripts to 3D scenes and rendered episodes, treating the production process as software that can be reused and improved.
01Plain-text script
02three.js scene
03Remotion render
04Episode1080×1920, up to 4K
Interactive model · sample data
01 / Script
scene coffee_shop {
character: developer
camera: close_up
action: raise_eyebrow
}A repeatable starting point.03 / RenderReady for the next frame.
ReadyPlain-text script in
03The outcome
Plain-text scripts in.Rendered episodes out.
Vertical 1080×1920, up to 4K