Image inspector
100%

0 / 0
← All projects3 min read

Blendlink

Bringing Blender scenes and supported EEVEE materials into Three.js.

Product designer & sole developer2026, public source; development build

  • Blender
  • Python
  • TypeScript

Browser output from the Blender-authored workbench used on an earlier version of this portfolio. The painterly finish belongs to the website.

The workflow

  1. Author the scene, materials, and camera in Blender.
  2. Save the file to rebuild its browser preview and compare the result.
  3. Compile the assets and use typed object bindings for website interactions.

The demo shows the compiled workbench at runtime. Source is public; an installable package release is still pending.

The problem
I wanted to edit this site's desk in Blender and bring those changes into the browser without rebuilding the scene in JavaScript. Blendlink handles the export, asset preparation, and typed scene bindings.
The result
Used for an earlier interactive workbench on this site.
Role
Product designer & sole developer
When
2026, public source; development build
Stack
  • Blender
  • Python
  • TypeScript
  • Three.js
  • React Three Fiber
  • Playwright
In this article

I built Blendlink because getting a Blender scene onto a website meant doing much of the work twice. After making the scene look right, I still had to export its meshes, prepare textures, reconstruct materials, and connect the objects to the page.

Blendlink compiles the scene for Three.js and generates typed references to the objects the website needs to control. I can keep editing in Blender while the website handles navigation, layout, and interaction.

A Blender-authored desk running in the browser
The portfolio workbench, with the website's painterly post-processing.

Keeping the authored appearance#

A mesh export carries the shape, but much of a scene's appearance lives elsewhere. Materials decide how a surface responds to light. Color management changes the displayed result. Compositor effects may soften, recolor, or distort the rendered image.

Blendlink now translates supported EEVEE material channels into live Three.js node materials. These include normal inputs and properties such as coat, transmission, and sheen. The browser evaluates those materials as the scene changes.

When a supported static channel cannot translate directly, Blendlink can bake it into a texture while keeping other channels live. This gives a material a way to travel without flattening its entire appearance into one image. The compiler checks whether that combination is safe and reports unsupported graphs.

Supported display transforms retain their color-management operations and lookup-table data, along with exposure, gamma, and white balance. Compositor support includes color adjustments, selected math and mix operations, Alpha Over, Gaussian Blur, and Glare Bloom. The source camera becomes the default unless the website supplies one.

Checking the result#

Preview Studio opens a browser view of the saved scene. It uses Three's WebGPU renderer with a WebGL2 fallback, which supports the translated node materials. The classic WebGL renderer keeps its existing presentation path and reports features it cannot apply.

A split comparison lets me inspect a Blender render beside the browser view. Difference view helps locate mismatched areas. If an updated shader fails, the last working preview remains available, and retrying a renderer failure does not require another bake.

The aim is a close EEVEE appearance. Lighting, indirect illumination, refraction, and material response can still differ between renderers. The comparison is useful precisely because translating the inputs does not guarantee an identical image.

Connecting a website#

The workflow has three commands:

  1. blendlink preview --blend scene.blend builds a local preview.
  2. blendlink connect [site] --blend scene.blend connects the file to an existing website.
  3. blendlink publish [scene] compiles final assets, verifies them, and runs the website's build. Deployment stays with the website.

Saving the Blender file rebuilds the preview. The compiler reuses valid geometry and UV preparation when it can, and reports its progress during a bake. For development builds, the add-on can point to a local package and preview scenes saved outside the Blendlink checkout.

The desk in this portfolio’s earlier homepage was one integration. Its monitor displayed React content through a generated screen binding. Blendlink handles the scene connection; the page decides what appears on the monitor and how visitors navigate it. That integration used an earlier private build and its own painterly filter.

Current limits#

The Blendlink source is public on GitHub. It remains a development project, with no public installable package release announced. I test it with Blender exports, packaged Three.js and React Three Fiber websites, browser comparisons, and failure-recovery checks.

The EEVEE work covers a defined set of operations. Shader and compositor parameter animation, Bump, additional render-pass inputs, and Glare modes such as Fog Glow remain unfinished. Unsupported compositor branches produce a diagnostic and bypass the graph. Blendlink does not promise universal node translation or pixel-identical Cycles rendering.

Project details

My role
Product designer & sole developer
Tools
Blender · Python · TypeScript · Three.js · React Three Fiber · Playwright
Status / period
2026, public source; development build
More tools & web systems

Have something in mind?

Discuss a similar project

I’m open to full-time, contract, and freelance work.

Email me about Blendlink