Fang Studio · 3D development
A 3D scene rendered live in the browser, right inside the page: a product to turn around, a place to explore, an abstract idea made tangible.
Purpose
3D puts visitors in control of what they look at: they turn, zoom in, explore, and understand an object or a space as they would in real life.
Two concerns come up whenever 3D on a website is mentioned: that it slows the site down, and that it feels like a gimmick. Slow 3D is badly made 3D: overly detailed models, lighting recomputed on every frame, a scene still running off screen. Used with restraint, it stays discreet: a material that reacts to the mouse, a background with depth, an animated detail in the corner of a page.
I rule out both pitfalls at the design stage. Each model is lightened in Blender wherever the eye can't tell the difference, lighting is computed once and baked into the textures, and the scene pauses as soon as it leaves the screen. Each scene is also given a role before it is modelled: showing a product, guiding the reading, making an idea concrete. Before launch, I test it on an entry-level phone. During the visit, the experience comes first: if the device slows down, the scene lowers its resolution and effects, down to a still image if needed.
I follow closely how 3D in the browser is evolving, in particular WebGPU, the successor to WebGL: richer effects on recent devices, the same scene displayed on the others.
Steps
- Use case : I first check that 3D serves your point, whether that means showing a product from every angle or making the abstract concrete. If an image is enough, I tell you. I then define what the scene must make clear and where it sits: opening the page, alongside a section, or as a small detail. That choice sets its budget, in weight as well as development time.
- Modelling : Objects are modelled in Blender, from your 3D files if they exist (design files, plans), or from photos and measurements. I simplify them wherever the eye cannot tell the difference, size geometry and textures for the web, then compress everything to weigh as little as possible.
- Light and materials : When the scene allows it, lighting and shadows are computed once and for all ahead of time (this is called “baking”), then locked into the textures. The scene keeps the quality of a rendered image while staying light to display. Materials are tuned to react to light like their real counterparts: metal, glass, fabric, stone.
- Integration : The scene is built with Three.js inside the React site. It runs on WebGPU when the browser allows it and on WebGL otherwise, with effects written once for both. Tied to scrolling or the mouse and animated with GSAP, it follows the visitor's gestures smoothly.
- Performance and fallback : The scene loads after the main content, so the page text can be read straight away. Rendering pauses as soon as it leaves the screen, and a still image replaces it on mobile and for visitors who limit animations. I then measure its cost on modest devices and adapt the quality to the power of each one.
In practice
- A product to show from every angle : The visitor turns it themselves. A photo gallery would only show a few views.
- An entry-level phone : An image replaces the scene: the page stays fast and the message complete.
- A browser that does not support WebGPU yet : The same scene is shown in WebGL. There is only one version to build, so only one piece of work to fund.
- A visitor who limits animations : Their system setting is respected: the scene stays still and moves only with their gestures.
- This website : The home page and the Contact page show my 3D work: modelling, baked lighting, scroll integration.
FAQ
Is 3D essential?
No. It still suits any kind of site. On a site that must inform first, it comes down to a detail (a material, a background, an object) that accompanies reading.
What does WebGPU add compared to WebGL?
WebGPU is the new generation of 3D in the browser. It makes better use of the graphics chip and allows richer scenes (particles, materials, light) for the same effort from the device. My effects are written for both, and are shown in WebGL wherever WebGPU is not available yet.
Does it slow the site down?
It has a cost, and I measure it. The scene loads after the main content and stops off screen, so the page text can be read before it appears.
How long, and how much?
From 20,000 €, on quote after a first conversation. The cost depends on the scene: modelling, interactions, number of objects.
Get started
Contact: contact@fangstudio.fr · /en/contact