What three.js handles
In its own words, the project aims to create an easy-to-use, lightweight, cross-browser, general-purpose 3D library [1]. Instead of writing buffers and shaders by hand, developers work with objects:
- Scene and scene graph: objects with parents and children.
- Cameras and controls, such as orbit controls.
- Materials, up to physically based ones with clearcoat, glass or fabric.
- Loaders for formats such as glTF/GLB, including Meshopt and Draco compression [2].
- Renderers for WebGL and WebGPU [1][3].
Licence and versions
three.js is released under the MIT licence [1], so it can be used in commercial projects. The library ships in numbered releases (r…) whose interfaces can change, so projects should pin the version and test before updating.
three.js or a ready-made component?
| three.js | Ready-made component (e.g. model-viewer) | |
|---|---|---|
| Freedom | full control over scene, rules and presentation | limited to built-in features |
| Effort | programming required | one HTML element |
| Suits | configurators with logic, variants, exploded views | simple product view, AR |
From our library
Every example configurator in our library is built with three.js, from the spiral stair configurator with parametric geometry to the planetary gearhead with a loaded GLB (fictional products). The renderer reports diagnostics such as draw calls per frame directly [4].
The pillar page 3D configurator explains how we build configurators on this basis.