Blendlink

Make the scene in Blender. Ship it beautifully in Three.js.

A warm, illustrated Blender-authored workbench scene running as the portfolio site's interactive Three.js hero
The portfolio workbench is Blendlink's flagship dogfood scene: authored in Blender, compiled for Three.js, and installed inside this site's existing React Three Fiber Canvas.
Role
Product designer & sole developer
When
2026 — beta release candidate
Stack
  • Blender
  • Python
  • TypeScript
  • Three.js
  • React Three Fiber
  • Playwright

A scene can look finished in Blender and still become a second, manual project on the web. Export settings, baked lighting, texture delivery, loading, renderer lifecycle, and deployment paths all sit between the artist's intent and the pixels a visitor sees. Blendlink treats that seam as a compiler problem.

“Make the scene in Blender. Ship it beautifully in Three.js.”

Three responsibilities, one scene

The product stays useful by being strict about ownership. Blender is not reduced to a mesh editor, and the website is not reduced to a deployment target.

Blender owns

Geometry, materials, lighting, camera intent, hierarchy, animation, and artist-authored component markers. When Eevee is selected, its visible result is the source of truth.

Blendlink owns

Export, baking and optimization, stable scene identities, typed bindings, atomic installation, lifecycle cleanup, and verification that the compiled result is loadable.

The website owns

Its route, Canvas, layout, loading presentation, analytics, framework, CDN policy, and deployment. Application behavior remains ordinary application code.

The path from save to site

The same compact workflow is available from Blender and from the command line.

blendlink preview --blend scene.blend compiles a private preview without asking the artist to scaffold a web project first.
blendlink connect [site] --blend scene.blend links the authored file to an existing website. Saving in Blender drives connected Preview builds.
blendlink publish [scene]compiles Final, verifies the scene, runs the website's own build script, and verifies the emitted artifacts again.
The generated binding stays small. Application code decides what ready, progress, retry, hover, focus, and other interface states should mean.

The site is the test

This workbench is not a separate marketing demo. It is the scene at the top of the site, with the same responsive framing, loading constraints, interaction states, and production build that a real Blendlink user has to live with. The source scene stays editable in Blender; the surrounding React application keeps control of the page.

That dogfood loop keeps the product boundary honest: deep package-owned modules handle export and renderer complexity, while tiny generated bindings leave application behavior in application code.

A Blender-authored screen, controlled by the site

The monitor is ordinary scene geometry with a stable Website Surface identity authored in Blender. The generated TypeScript binding lets this site supply its own Canvas, so hovering or keyboard-focusing Web, 3D, and About changes the physical screen inside the scene.

Blendlink isolates the receiver material, preserves the artist's UVs, invalidates demand rendering when pixels change, and restores owned resources on cleanup. The application still owns the content, accessibility, interaction policy, route, and React Three Fiber Canvas.

Try it on the homepage: hover or focus each discipline.

Release evidence, stated plainly

At the time this article was added, Blendlink's 0.8 line is a local beta release candidate—not a claim that npm, GitHub release, or Blender Extensions publication is complete.

The release gate exercises the TypeScript package, real Blender and KTX tooling, packed Vanilla and React Three Fiber consumer builds, and headless add-on installation and archive checks.
Baked appearance and lighting are checked in a browser, not inferred from a manifest or a unit seam.
The dogfood gate publishes this workbench, runs a production Next.js build, checks TypeScript, and verifies the scene with Playwright.
Registry and hosted deployment checks remain public-release gates. Until they pass, this page says “release candidate.”

What it is—and is not

Blendlink is an artist-first compiler and Blender add-on for solo developers and small teams. It is not a cloud service, proprietary renderer, complete website generator, or visual scripting platform.

The public repository link will appear here when the GitHub, registry, and hosted-deployment release gates are complete. This site currently builds from a content-identified local release candidate rather than pretending an unpublished URL is live.