Three.js scene composition

Use Three.js when depth, camera, lighting, material response, geometry, or spatial animation carries the media idea and a browser-rendered scene is an appropriate production surface. This skill begins after asset requirements and creative intent are known and ends with a reproducible rendered scene package.

It does not teach mesh modeling, retopology, rig authoring, physics simulation, WebXR product design, or game logic. It may consume approved glTF assets, animation clips, textures, environment maps, fonts, data, and audio cues produced elsewhere.

Evidence stance

• Documented fact means behavior specified by official Three.js, Khronos, WebGL, or W3C sources.
• Production heuristic means a useful starting point that must be tested on the actual scene and delivery hardware.
• Empirical observation means a result measured from the scene, frame output, browser, GPU, or encoded deliverable.

Three.js releases frequently and examples/addons may change paths or APIs. Facts and links were checked 2026-07-12. Pin and record the installed revision, check migration notes, and test the exact target browser and renderer before delivery. WebGPU support and renderer parity are especially volatile.

Decide whether Three.js is the right renderer

Use Three.js when the deliverable needs: