Orillusion: a WebGPU 3D engine that calls itself beta
Orillusion is a pure Web3D rendering engine which is fully developed based on the WebGPU standard.
At a glance
- What is it?
- Orillusion ships its core as one npm package that renders through WebGPU, asks for Chrome 113 or Edge 113 or newer, and warns readers off commercial use while the version number sits below 1.0.
- Who is it for?
- Orillusion fits experiments and demo pages where you control the browser, not products with a browser floor you do not control. Before committing, weigh the beta warning against your own release plans and confirm your target browsers appear in the platform table.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 9 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- Orillusion/orillusion5,230 ★ · +11
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| Orillusion/orillusion | 5.2k | 5.2k |
11 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
One package name, three bundler targets
The core engine ships as one npm package, @orillusion/core, at version 0.9.2, and the manifest hands bundlers three different files for the same code. The root export resolves an ES import to orillusion.es.js and a CommonJS require to orillusion.umd.js, while main points at the UMD file and module at the ES file. Types for both shapes resolve to ./dist/types/index.d.ts.
"exports": {
".": {
"types": "./dist/types/index.d.ts",
"import": "./dist/orillusion.es.js",
"require": "./dist/orillusion.umd.js"
},
"./dev": {
"types": "./dist/types/index.d.ts",
"import": "./dist/orillusion.es.max.js",
"require": "./dist/orillusion.umd.max.js"
},
"./dist/*": "./dist/*"
}A third entry, ./dist/*, passes anything under dist through untouched, so samples and tool code can reach internal artifacts without a new export entry. Only dist is published, since files is set to ["dist"], which means nothing from src, samples or test reaches a consumer. The consequence for a reader is that the import specifier alone does not tell you which build you received: the same symbol imported and required lands on two different files, and tree shaking only happens on the ES one.
The dev entry resolves to the max builds
The ./dev entry is the one that catches people out. It resolves to orillusion.es.max.js for an import and orillusion.umd.max.js for a require, so the subpath named dev points at the max builds, which the ./dist/* entry also exposes. Type declarations are identical for both entries, so a project can swap between them without touching its type imports.
"dev": "vite",
"build": "tsc --p tsconfig.build.json && vite build && npm run build:types && npm run minify",
"build:test": "tsc --p tsconfig.build.json && vite build && npm run build:packages",
"build:packages": "npm run build:physics && npm run build:media && npm run build:stats && npm run build:particle && npm run build:graphic && npm run build:geometry"Around that sits a local development loop where npm run dev runs vite, matching the vite.config.js and index.html at the repository root. The build line runs the TypeScript compiler against tsconfig.build.json, then vite build, then build:types, then minify. The test line stops after vite build and swaps minify for build:packages, which fans out into six subpackages: physics, media-extention, stats, particle, graphic and geometry. The consequence is that the unminified entry point is never explained in prose. The exports map is the only place dev is defined, and nothing states when a project should ask for it.
Chrome 113 sets the floor, Android sits behind a flag
The Platform section splits the supported set in two. On Windows, Mac and Linux the named browsers are Chrome 113+ and Edge 113+. Android is the other case: Chrome Canary 113+ and Edge Canary 113+ behind the enable-unsafe-webgpu flag.
Windows/Mac/Linux:
- Chrome 113+
- Edge: 113+
Android (Behind the `enable-unsafe-webgpu` flag):
- Chrome Canary 113+
- Edge Canary 113+Nothing else appears in that list, so no Firefox build and no Safari build is claimed, and no minimum adapter or driver requirement is stated anywhere. The consequence is concrete for anyone shipping pages rather than demos. An application inherits the browser floor of the standard underneath it, and on a machine with no WebGPU adapter the page needs a device it cannot get, with no documented fallback that makes the page degrade instead. On Android the flag is not something an application can set for itself: somebody testing the build has to turn enable-unsafe-webgpu on before any of this code runs.
Engine3D.init() sizes its own canvas to the window
Engine3D.init() called with no arguments creates a canvas the same size as the window, so the drawing surface is decided by the layout of the host page rather than by the code that renders into it. The manual route replaces that with an element you declare yourself: give a canvas an id, fetch it with document.getElementById, and pass it through canvasConfig.
import { Engine3D } from '@orillusion/core';
let canvas = document.getElementById('canvas')
const engine = await Engine3D.init({
canvasConfig: { canvas }
})Each call to Engine3D.init() returns an independent instance, so several engines can sit side by side in the same page, each with its own canvas, and that is the supported shape for anything with more than one viewport.
Installing @orillusion/core and starting the first engine
Install is one command, and the first frame takes three lines. The package is on npm as @orillusion/core, and the documented way to work with it is through a front-end build tool such as Vite or Webpack rather than a bare script page.
npm install @orillusion/core --saveimport { Engine3D, Camera3D } from '@orillusion/core'
Engine3D.init().then((engine) => {
// Next
})Named imports pull individual symbols out of the module, while the global form imports the whole namespace as Orillusion. Engine3D.init() is asynchronous, which is why a promise form and an async form both exist, with async and await advised so the engine reference stays a plain const.
import { Engine3D } from '@orillusion/core'
async function demo(){
const engine = await Engine3D.init();
// Next
}
demo()The consequence for anyone copying the promise form is that everything after init() has to live inside the then callback, where there is no await to be had, so a scene setup routine with a dozen steps ends up nested instead of linear.
Three routes off a CDN, one of them a global object
With no bundler there are three ways to reach the same engine, all pointing at unpkg. The global build is a plain script tag, and every top-level API hangs off a global Orillusion object, so the next line destructures Engine3D and Camera3D from it.
<script src="https://unpkg.com/@orillusion/core/dist/orillusion.umd.js"></script>
<script>
const { Engine3D, Camera3D } = Orillusion
</script>The ES module build is a script with type module importing the same two names from orillusion.es.js, and that is the form pushed for development because browsers load ES modules directly.
<script type="module">
import { Engine3D, Camera3D } from "https://unpkg.com/@orillusion/core/dist/orillusion.es.js"
</script>Import maps are the third route, and they exist so the dependency name stays put while the address behind it can move.
<script type="importmap">
{
"imports": { "@orillusion/core": "https://unpkg.com/@orillusion/core/dist/orillusion.es.js" }
}
</script>
<!-- Customerized names could be imported -->
<script type="module">
import { Engine3D, Camera3D } from "@orillusion/core"
</script>The consequence of the global build is that nothing is resolved on your behalf: no module graph, no tree shaking, and version pinning has to happen by editing the URL inside the script tag.
Samples are filed by subsystem, not by finished scene
The repository keeps examples under samples/, grouped by subsystem rather than by finished scene: alpha, animation, audio, base, benchmark, compute, geometry, gi, graphic, lights, loader, material, navemesh, octree, particle, physics, physics-rapier, pick, post, render, sky, sprite and utils, with samples/index.ts collecting them.
Those names are the fastest way to read the scope of the engine. A compute folder next to gi and navemesh implies more than a forward renderer with one texture, physics-rapier points at Rapier as a physics backend with a separate physics folder beside it, and octree and pick are folders that only matter once a scene is large enough to need spatial queries.
The consequence is that this list is not a documented feature matrix. Nothing ties a folder to a stability promise, nothing states which samples run on which of the supported browsers, and the README does not name a minimum sample for a first run, so an entry point has to be chosen by reading the code.
Beta, MIT, and twenty months between two minor versions
The Need to know block is two words and a warning: beta version, not recommended for any commercial application. That line sits directly below a claim of desktop level rendering effects and complex scenes in the browser, which is the tension to hold on to while reading the rest of the project.
The licence is MIT, and the published version is 0.9.2, a version number below 1.0. Releases are irregular: v0.9.2 on 2026-07-31, v0.8.4 on 2024-11-27 and v0.8.3 on 2024-08-28, so roughly twenty months separated the last two minor steps. The repository kept receiving pushes through that gap, with the most recent one on 2026-10-21.
The consequence is that moving between minor versions is your problem, since code written against v0.8.x can need rework on v0.9.x. The caution about commercial use is a statement from the maintainers rather than something the MIT grant blocks: the permission in the licence is broad, the warning in the readme is about maturity. Contributors are pointed at .github/contributing.md before developing or opening a pull request, and discussion goes to a forum at forum.orillusion.com.
Editorial conclusion
Orillusion fits experiments and demo pages where you control the browser, not products with a browser floor you do not control. Before committing, weigh the beta warning against your own release plans and confirm your target browsers appear in the platform table.
Frequently asked questions
What is replacing WebGL?
WebGPU, as far as Orillusion is concerned: the engine is described as a pure Web3D rendering engine fully developed based on the WebGPU standard, and the project calls WebGPU the latest technology in the web domain. For working with it, the project points at front-end build tools such as Vite or Webpack.
Is WebGPU low level?
The README never characterises the abstraction level of WebGPU itself. What Orillusion publishes is a scene level surface: Engine3D.init() to create an engine, Camera3D imported beside it, a canvasConfig option for the canvas, and sample folders for compute, gi, navemesh and physics-rapier.
Which browsers does Orillusion support?
Chrome 113+ and Edge 113+ on Windows, Mac and Linux. On Android the listed builds are Chrome Canary 113+ and Edge Canary 113+ behind the enable-unsafe-webgpu flag, so the phone path is a flag someone has to turn on before the page runs.
What should I check before shipping an Orillusion page?
Read the beta warning first, then confirm your target browsers sit in the platform table, since only Chrome 113+ and Edge 113+ are named on desktop and Android needs a flag. The published version is 0.9.2 under the MIT licence, and the last release before it, v0.8.4, dates from 2024-11-27.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/orillusion-orillusion)Star history chart for your README
[](https://hysenlabs.com/projects/orillusion-orillusion)Was this useful?