null3d-engine/null3d

null3D

A browser 3D engine for games and heavy 3D apps. Its Rust core runs on worker threads, it draws with WebGPU or WebGL2, and you write your 3D scenes in TypeScript with three.js-style names.

Pre-alpha: null3D has no release yet. Nothing is on npm yet.

Quickstart · Features · How it works · Where it runs · Docs · Porting from three.js · Roadmap

⭐ If you want to see this engine built, a star helps other people find it.

Benchmark scene S1: 100,000 boxes that sketch code moves every frame, drawn by null3D with WebGPU.

What is null3D?

null3D is a browser 3D engine that aims to replace three.js where CPU time limits a scene. That happens with many moving objects, deep scene graphs, animation and culling. The engine’s core is Rust compiled to WebAssembly, and it runs on worker threads, so the page’s main thread stays free.

It draws with WebGPU, and with WebGL2 where WebGPU is missing, from the same sketch code. That matters most on phones, where many devices still have no WebGPU. Where the GPU is the limit, null3D aims to match three.js, because both engines use the same browser graphics APIs.

Quickstart

The first release, 0.1.0, puts the packages on npm. Until then, run the demos from a clone of this repository.

Install the engine from npm and import it, as you would three:

bun add @null3d/engine
bun add -d vite @null3d/vite-plugin

The Vite plugin sends the headers that worker threads need, builds the sketch worker, and compiles your WGSL for WebGPU and WebGL2:

// vite.config.ts