Ray tracing and rasterisation
There are two basic ways to produce a 3D image:
| Rasterisation | Ray tracing / path tracing | |
|---|---|---|
| Principle | triangles are projected onto the screen and shaded | light paths are traced through the scene |
| Strength | very fast, real time | reflections, glass, soft shadows, indirect light |
| Typical use | browser configurators, games | catalogue images, animation, advertising |
| Example in Blender | EEVEE [2] | Cycles [1] |
Blender describes Cycles as a physically based path tracer for production rendering [1] and EEVEE as a real-time engine based on rasterisation that is explicitly not a path tracer [2].
Ray tracing in the browser?
It is possible, but rarely the first choice for configurators. A clean path-traced image needs many passes per pixel; it takes time to become noise-free, and every change starts again. That sits badly with a model visitors constantly rotate and rebuild. WebGPU opens new options with general-purpose computation on the GPU [3], but the basic cost hardly changes.
What this means for you
- Catalogue, advertising, marketplaces: pre-rendered images with path tracing, as realistic as needed.
- Configurator and 3D view: real-time rendering with PBR materials, environment light and, where useful, baked detail.
- Both from one model: a well-prepared model can serve both routes; materials then need tuning for each engine.
For configurators the usual split is therefore: ray tracing for images, rasterisation for interaction.
Our example configurators render in real time with rasterisation; they do not use ray tracing. The 3D product viewer page covers the real-time route.