Chili3D: a CAD kernel in WebAssembly, now at version 0.8.0
A 3D CAD running entirely in the browser
At a glance
- What is it?
- Chili3D compiles OpenCascade (OCCT) to WebAssembly and drives it through a TypeScript interface layer, which puts solid modelling in a browser tab. The architecture is unusually clean, the licence is AGPL-3.0, and the app version (0.8.0) is now ahead of the document version (0.7.1).
- Who is it for?
- Chili3D fits a browser first CAD workflow: open chili3d.com, or clone and run `npm run dev`, and you get OCCT booleans, fillets and STEP import in a tab with nothing to install. It does not fit a team that needs a frozen file format guarantee or a stable plugin contract, because the package sits at 0.8.0 and the licence is AGPL-3.0.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 14 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
- xiangechen/chili3d4,993 ★ · +136
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| xiangechen/chili3d | 4.9k | 5k |
136 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The kernel is OCCT 8.0.0 compiled to WebAssembly
Chili3D splits geometry from display. The modelling kernel is OpenCascade (OCCT), compiled to WebAssembly, and rendering goes through Three.js. The README claims near-native modeling performance from that pairing, with the application hosted at chili3d.com and a Cloudflare mirror at chili3d.pages.dev.
AppBuilder decides which backends get wired in
The README does not describe how the packages under `packages/` are wired together; `package.json` only shows that `packages/*` and `plugins/*` are workspaces.
Boolean operations and thick solids come off the same kernel
Feature lists for CAD projects are usually marketing. This one is specific enough to check against the kernel. Basic shapes include boxes, spheres, cylinders, cones, pyramids and more. 2D sketches cover lines, arcs, circles, ellipses, conics, splines and text, and the direct-modelling curve tools add Bézier curves, polygons and helices. The advanced set lists boolean union, difference and intersection, extrusion and revolution, sweeping and lofting, offset surfaces and thick solid, linear and circular arrays, plus shape checking and repair.
Editing is where kernels usually fall apart, and this list names the operations instead of implying them: chamfer, fillet, trim, break, split, sew and simplify, then move, rotate, mirror and the two array types, then feature removal, sub-shape manipulation and exploding a compound object into its parts.
Measurement ships with it rather than arriving later. The tools measure angles and lengths, and calculate the sum of length, area and volume.
Shape checking and repair is named, which tells you bad input has an answer.
STEP, IGES, BREP and STL bracket the document model
Documents can be created, opened and saved, and every change lands on a full undo and redo stack with transaction history rather than a flat list of snapshots.
Interchange is where CAD earns its keep, and four formats are named in both directions: STEP, IGES, BREP and STL.
Snapping covers points, edges, faces and the workplane, and tracking follows axes and detected feature points, with visual guides for both.
Plugins load from a URL parameter at runtime
Plugins are workspace members, since `workspaces` lists both `packages/*` and `plugins/*`. A plugin is therefore an npm package in the same tree as the application, and `npm run build` runs `rspack build && node scripts/build-plugins.mjs`, so plugin bundles come out of the same command as the app bundle.
npm install, then npm run dev, and the WASM build is optional
The prerequisites are Node.js and npm. Clone the repository and install:
git clone https://github.com/xiangechen/chili3d.git
cd chili3dnpm installStart the development server:
npm run devRspack is the bundler, since `npm run dev` is `rspack dev`.
You do not need a C++ toolchain for normal work. The prebuilt WebAssembly module is included in the repository, and building it from source is the optional path. `npm run setup:wasm` is a one-time setup that runs `node scripts/setup_wasm_deps.mjs`, and `npm run build:wasm` compiles the C++ in `cpp/` with `cd cpp && cmake --preset release && cmake --build --preset release`.
Production output comes from `npm run build`. Tests come from `npm run test` for Rstest with Happy-DOM, or `npm run testc` for coverage.
Docker copies /app/dist into an nginx image
The Docker path is a two stage image. The builder stage is `node:alpine`, copies the repository in, and runs `npm install && npm run build`. The final stage is `nginx:alpine`, and the only thing carried across is `/app/dist` into `/usr/share/nginx/html`. Nothing from the Node build stage reaches the served image except static files.
`compose.yml` defines one service named `chili3d`, builds it from that `Dockerfile`, restarts it with `restart: unless-stopped`, and maps host port 8080 onto container port 80:
services:
chili3d:
build:
dockerfile: Dockerfile
restart: unless-stopped
ports:
- "8080:80"docker compose up -d # Builds and serves the app at http://localhost:8080Because the WebAssembly module ships prebuilt, that image needs no Emscripten stage.
Biome, an I prefix and a pre-commit hook gate every change
TypeScript, JavaScript, CSS and JSON go through Biome, and C++ goes through clang-format with WebKit style.
The same rules run before a commit leaves your machine. simple-git-hooks installs a pre-commit hook that calls lint-staged, which sends `*.{ts,js,css,json,mjs}` through `npx biome check --write` and `*.{c,h,cxx,hxx,cpp,hpp}` through clang-format. `npm run check` is the same Biome pass across the project. Versions are declared in `package.json`: Biome ^2.4.15, Rspack ^2.0.3, Rstest ^0.10.0, Happy-DOM ^20.9.0.
Licence and cadence are worth reading together. Chili3D is AGPL-3.0, with a `LICENSE` file in the repository root, so a hosted modified build comes with obligations its users can act on. Release v0.8.0 shipped on 2026-10-30, v0.7.1 on 2026-09-19 and v0.7.0 on 2026-08-23, and the last push was on 2026-11-02. In `package.json`, `version` reads 0.8.0 while `documentVersion` stays at 0.7.1, so the document format version is tracked separately from the app version.
Editorial conclusion
Chili3D fits a browser first CAD workflow: open chili3d.com, or clone and run `npm run dev`, and you get OCCT booleans, fillets and STEP import in a tab with nothing to install. It does not fit a team that needs a frozen file format guarantee or a stable plugin contract, because the package sits at 0.8.0 and the licence is AGPL-3.0. Before you adopt it, check two things: whether your own STEP or IGES files survive the shape checking and repair path, and whether hosting a modified copy inside your product stays acceptable under AGPL-3.0.
Frequently asked questions
How much does 3D CAD cost?
Nothing at the point of use for Chili3D: it is open source under AGPL-3.0, hosted at chili3d.com and at chili3d.pages.dev, and none of it requires a local installation. The cost lands on whoever modifies and hosts a copy, because AGPL-3.0 is the licence that governs a network deployment of a changed build.
What is the best free 3D CAD app?
Chili3D is a free option for anyone who wants solid modelling in a browser tab: OpenCascade compiled to WebAssembly for the geometry, Three.js for rendering, boolean operations, fillet and chamfer, and STEP, IGES, BREP and STL import and export.
How do I run Chili3D on my own machine?
Clone https://github.com/xiangechen/chili3d.git, run `npm install`, then `npm run dev`, which runs `rspack dev`. Node.js and npm are the only prerequisites, and the prebuilt WebAssembly module ships in the repository, so no C++ toolchain is required for ordinary development.
Do I have to rebuild the WebAssembly module to work on Chili3D?
No, the prebuilt WASM module is included. Building it from source is optional: `npm run setup:wasm` performs the one-time dependency setup, and `npm run build:wasm` compiles the C++ in `cpp/` using the release cmake presets.
How do I add a plugin or a language to Chili3D?
Plugins live under `plugins/`, which `package.json` lists as a workspace alongside `packages/*`, and `npm run build` runs `node scripts/build-plugins.mjs` after the Rspack build.
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/xiangechen-chili3d)Star history chart for your README
[](https://hysenlabs.com/projects/xiangechen-chili3d)Was this useful?