Three.js / Industries
Three.js by industry
The same library, six different jobs. What gets built in each industry, the examples worth studying, the tools that do the heavy lifting, and where Three.js is the wrong answer.
- 01Real production examples
- 02The stack per industry
- 03Honest alternatives
- 04What fails on mobile
Where Three.js earns its place
Most Three.js material is organised by technique: shaders, physics, loaders. That is useful once you are building. These pages are organised by what the business is trying to do, with the techniques underneath where they belong.
3D product visualization
Product viewers, configurators, 360 views and virtual try-on, running on the storefront rather than in a hosted viewer.
Read more →
3D car configurator
Real-time paint, wheel and trim changes, interior views and AR placement, at a file size a phone will load.
In progress
Virtual apartment tours
Walkthroughs and interactive floor plans built from models rather than photos, so unbuilt units can be shown too.
In progress
Digital twin software
Browser-based digital twins, CAD viewers and BIM models, with the pipeline from STEP or IFC to the web explained.
In progress
3D data visualization
Globes, geospatial maps, point clouds and network graphs, rendered on the GPU so they stay explorable.
In progress
3D medical visualization
Anatomy viewers, DICOM and volume rendering, device visualization and patient education.
In progressNot sure which applies to you?
Tell me what the project has to do and I will say which of these it actually is, and whether Three.js is the right tool for it.
Talk it through →Working at an agency?
The same work, white-label: builds under your brand, rescue for stuck projects, senior review before delivery.
For agencies →