chili3d.com

What is Chili3D?

Chili3D is a browser-based 3D CAD application for online model design and editing. Instead of installing desktop software, you open it in a web browser and work on models there. Its technical foundation is a WebAssembly build of OpenCascade (OCCT) for solid modeling, rendered with Three.js — a combination aimed at giving a web page real CAD geometry rather than just mesh viewing.

What that means in practice

• No installation, cross-platform by default. A student on a Chromebook, a Linux user, or someone on a locked-down work laptop can all reach the same tool through a browser.
• Parametric-style solid modeling. Because OCCT is a B-rep kernel, the intended workflow is precise shapes, booleans and edges — not sculpting or game-asset modeling.
• JavaScript required. The page itself only reports that JavaScript must be enabled to run the app, so treat it as a full client-side application, not a static document.

Who it suits

A useful next step

Open the app and test one small, real task end to end — for example, model a bracket with two holes, then try exporting it in a format your downstream tool accepts (STEP is the usual test for CAD interchange). That single exercise tells you more about whether the kernel, the UI and the export path meet your needs than any feature list.

If you want to compare the web-CAD landscape, look at Onshape for cloud-native parametric CAD with collaboration, and FreeCAD if you would rather keep everything local and open source.

How does Chili3D run 3D CAD in a web browser without installing software?

Chili3D runs in the browser by compiling a CAD kernel to WebAssembly and rendering the scene with WebGL, so the modeling work happens on your machine inside a sandboxed web page rather than on a remote server. The page itself is a JavaScript application shell: its only visible message is a request to enable JavaScript, which confirms there is no server-rendered fallback and no install step to reach the editor.

The stack implied by the project's own keywords explains the split of duties:

• OCCT (OpenCascade) supplies the solid-modeling kernel — the B-rep geometry, booleans, fillets and STEP-style operations that make it CAD rather than a mesh editor.
• WebAssembly is the bridge that lets that C++ kernel execute at near-native speed in the browser tab.
• Three.js handles the viewport: camera, lighting, selection and drawing the resulting geometry through WebGL.

That combination is why a browser tab can host real parametric modeling. A native CAD install ships a compiled kernel plus a graphics layer plus a file system; here the kernel is fetched as a .wasm module, the graphics layer is WebGL, and storage is browser-managed rather than a local folder.

Practical consequences

The trade-off is real: WASM is fast but generally slower than native code for heavy kernel operations, and a browser tab has less memory to work with than a desktop application. Simple parts, quick edits and sharing a model by link are where this approach shines; very large assemblies or long-running computations are where a desktop tool still wins.

A concrete scenario

Suppose a mechanical engineer needs to review a colleague's bracket and tweak a hole diameter before a meeting. On a desktop-only workflow that means installing software on whatever machine is at hand. With Chili3D, the engineer opens the site, imports the model, edits the feature, and exports — no admin rights, no installer. If the model is a 500-part assembly, expect the tab to struggle and plan to move to a desktop kernel.

If you want to evaluate it, open the site with JavaScript enabled and try a small part first: create a sketch, extrude it, then export. That sequence tells you quickly whether the kernel and viewport are responsive enough for your typical work. For comparison with other browser CAD efforts, see Onshape, which takes the opposite architectural route by running the kernel on cloud servers, and three.js for the rendering library underlying this class of tool.

Can I import and export existing CAD files in Chili3D?

Chili3D is described as a browser-based 3D CAD application for online model design and editing, built on WebAssembly and OpenCascade (OCCT) with Three.js for rendering. Its stated purpose is creating and editing 3D models directly in the browser rather than installing desktop software.

Whether you can import and export existing CAD files is not confirmed by the available page information. The page evidence only shows a JavaScript-required notice, with no documentation of supported file formats, import/export menus, or conversion capabilities. So treat file compatibility as unverified rather than assumed.

What to check before relying on it

• Supported formats: Look for STEP, IGES, STL, OBJ or native project formats. STEP/IGES matter for CAD interchange; STL/OBJ matter for 3D printing and mesh workflows.
• Direction: Some browser CAD tools import meshes but cannot export solid B-rep geometry, or vice versa.
• Fidelity: Imported models may lose parametric history, sketches or constraints, leaving you with a "dumb solid" you can only measure or modify directly.
• Browser limits: Large assemblies can strain memory and performance in a WebAssembly app.

Practical next step

Open the app and test with a small, non-critical file first. If you need to move models between tools, confirm both the import and export path work before committing a real project to it. For desktop-grade interchange, established options include FreeCAD and Onshape, which document their format support openly.

If you mainly need quick browser-based viewing or light editing rather than full CAD translation, Chili3D may still be worth trying — just verify format support against your actual files.

What CAD modeling operations can I perform in Chili3D?

Chili3D is a browser-based 3D CAD application, so the modeling operations you can perform are those typical of a solid and surface modeler built on OCCT (OpenCascade) and rendered with Three.js. In practice this means you can create and edit models directly in the browser without installing desktop software, then export the result.

Typical operations you can expect in a web CAD tool like this:

• Sketching and 2D profiles — draw lines, arcs, circles and constraints as the basis for 3D features.
• Solid modeling — extrude, revolve, loft, sweep and shell profiles into 3D bodies.
• Boolean operations — union, subtract and intersect between solids.
• Feature editing — fillet, chamfer, draft and pattern (linear/circular) on edges and faces.
• Assembly and transforms — move, rotate and position parts relative to each other.
• Import/export — bring in standard CAD formats and export your finished model for downstream use.

Because it runs on WebAssembly, the heavy geometry kernel executes in your browser, which keeps the workflow self-contained but means performance depends on your device and model complexity.

A practical next step: open the app in a Chromium-based browser, create a simple part (sketch a rectangle, extrude it, then subtract a cylinder), and save or export it. That exercise will quickly show you which of the operations above are exposed in the current interface and how the feature tree behaves.

If you need to compare options, other browser-accessible CAD tools include Onshape and Autodesk's web offerings, though their operation sets and collaboration models differ from a lightweight in-browser modeler like Chili3D.

Does Chili3D work on mobile devices or only desktop browsers?

Chili3D is designed as a browser-based 3D CAD application, so its reach depends less on desktop versus mobile and more on whether the browser can run the required JavaScript and WebAssembly. The page itself provides little detail beyond a note that JavaScript must be enabled, so there is no confirmed mobile-specific interface or touch-optimized workflow described.

In practice, that means:

• Desktop browsers are the safer choice for serious modeling. CAD work involves precise selection, keyboard shortcuts, and often a mouse or trackpad for orbiting and panning.
• Mobile browsers may load a WebAssembly-based app, but the experience can be limited by small screens, touch gestures, and reduced performance for complex models.
• Tablets can sometimes bridge the gap, especially with a stylus, but a mobile browser is not the same as a native mobile CAD app.

If you want to test it on a phone or tablet, open the site in a modern browser such as Chrome or Safari and try a simple model first — a cube or a basic sketch — before attempting anything detailed. If the interface is hard to control or the model lags, switch to a desktop browser.

For a practical decision: use desktop for design and editing, and treat mobile as a way to view or make small adjustments only if the app proves usable on your device.

How does Chili3D compare to desktop CAD applications for online model design?

Chili3D is a browser-based 3D CAD application built on WebAssembly and OCCT, so it targets a different working style than installed desktop CAD. It is best understood as a lightweight, zero-install option for online model design and editing rather than a full replacement for a professional desktop suite.

Where the browser approach wins

• No installation, no license server, no local GPU driver setup: if the browser runs WebAssembly, the app can start.
• Models live in a shareable web context, which suits quick reviews, teaching, or handing a link to a colleague.
• Cross-platform by default — the same session works on Windows, macOS, Linux or a Chromebook.

Where desktop CAD still leads

• Heavy assemblies, large part counts and complex surfacing generally need native memory management and multithreading.
• Parametric feature trees, drawing generation, simulation and CAM integration are typically deeper in mature desktop packages.
• Offline work, local file-system control and enterprise data management are native to desktop installs.

A practical test Take one real task you do weekly — say, a bracket with a few fillets and an exported STEP file. Run it in Chili3D first, then in your desktop tool. If the browser version covers the geometry and export you need, it can serve as your quick-edit layer while desktop CAD handles production work.

For broader context on what web CAD can do, see Onshape and Autodesk; both document the trade-offs between cloud and installed workflows.