Start
ThreeNative compared
How ThreeNative differs from Three.js alone, Godot, Unity and Unreal, and when a Three.js and TypeScript team picks each one.
How ThreeNative compares with plain Three.js, traditional visual engines (Godot, Unity, Unreal Engine) and hosted AI game makers across source ownership, MCP tooling, world creation and shipping targets.
| Capability | ThreeNative | Three.js | Godot | Unity | Unreal Engine | AI Makers |
|---|---|---|---|---|---|---|
| Architecture & ownership | ||||||
| Programming model | Plain TypeScript + real THREE.Scene & WebGPURenderer | Plain JS / TS, low-level 3D API only | GDScript or C# inside Godot nodes | C# MonoBehaviours & DOTS | C++ & Blueprint visual graphs | Prompt wrapper; code hidden or paywalled |
| Scene format & git diffs | 100% readable TS/JSON source diffs — no opaque editor state | 100% source code | .tscn text scenes + editor-owned resources | YAML scenes / prefabs with GUID churn | Binary .uasset & .umap files | Hosted cloud state; code export gated on Pro/Max |
| Source ownership & license | MIT end to end, including native C++ runtime | MIT | MIT | Proprietary + seat / runtime fees | Source available + 5% royalty over threshold | Proprietary runtime; credit burn & host lock-in |
| AI agent toolchain | ||||||
| Built-in MCP servers | 6 wired servers (115 tools) for Claude, Codex, Cursor & more | None | Community / fork plugins | Beta assistant & external MCPs | External / community editor MCPs | Proprietary chat only (no external MCP) |
| Offline API discovery | 622 engine APIs + classic 3D mechanic cards | Relies on LLM training weights | Class docs via search | API docs via search | Large surface, version drift common | Closed prompt internals |
| Automated verification | Fail-closed JSON playtests, screenshots & perf budgets | Roll your own test harness | Unit tests; headless QA custom | PlayMode tests require editor setup | Gauntlet / Functional tests, heavy setup | Opaque QA claims without replayable proof |
| Build-time animation & sculpt gates | Foot-skate checks, Pose Lab, 8-pass sculpt & rig parity gates | None | Manual editor inspection | Manual editor inspection | Manual editor inspection | Single-shot generation; prone to regressions |
| Worlds, assets & content | ||||||
| Procedural asset library | 200+ trees, cliffs, 75 city modules, biomes & 49 dungeon pieces | Bring your own models | Bring your own models | Asset Store / third-party | Quixel / Fab integrations | Limited low-poly props or generated meshes |
| Live terrain editor | Collaborative Strata GUI + agent MCP over SSE (409 rev-safe) | Write your own heightfield code | Addons required (Terrain3D) | Built-in editor terrain tools | Landscape tools & World Partition | No collaborative seeded terrain pipeline |
| External pack import | Unreal (.uasset/.umap) & Unity (.unitypackage) → GLB + report | glTF / FBX loaders only | glTF / FBX / Blend; no .uasset | Unity packs native; no Unreal | Unreal packs native; no Unity | Custom upload or platform catalog only |
| Rendering & targets | ||||||
| Default look | Unreal 5.8.3 tone curve, sky, GI & shadows in src/render/ | Blank black canvas; manual lights & tone | Forward+ / SDFGI / Volumetric fog | URP / HDRP presets | Lumen & Nanite flagship defaults | Varies wildly per prompt |
| Physics & HUD | Godot-shaped Rapier physics + React 19 / Tailwind HUD | Wire physics & DOM manually | Godot Physics / Jolt + Control UI | PhysX / Havok + UI Toolkit | Chaos Physics + UMG / CommonUI | Basic JS physics & generated HTML overlays |
| Web target | First-class WebGPU + automatic WebGL2 fallback | First-class WebGPU & WebGL2 | WASM export (~20–40 MB, thread caveats) | Heavy WebGL / WebGPU WASM builds | Web export deprecated / unsupported | Hosted browser preview |
| Native desktop & mobile | C++ V8 + wgpu-native (Desktop & Android; iOS experimental) | Requires Electron / WebView wrapper | Desktop, Android & iOS | Desktop, Android, iOS & consoles | Desktop, Android, iOS & consoles | Cloud export or thin WebView wrappers |
| Visual scene editor | Code-first by design (+ live Studio & Terrain Editor) | None (third-party editors) | Full node/scene editor & inspector | Full mature scene & prefab editor | Full AAA world & Sequencer editor | Chat prompt + basic viewport preview |
At a glance
ThreeNative is a game framework on top of Three.js. You write TypeScript in your own editor and keep Three.js materials, cameras, meshes and loaders. ThreeNative adds the game loop, input, physics, asset builds, UI bindings, playtests and a native runtime.
| ThreeNative | Three.js | Godot | Unity | Unreal Engine | |
|---|---|---|---|---|---|
| What it is | Game framework on Three.js | 3D rendering library | Open-source engine and editor | Engine and editor | Engine and editor |
| You write | TypeScript in your editor | JavaScript or TypeScript | GDScript or C# in the editor, C/C++ via GDExtension | C# in the editor | Blueprints and C++ in the editor |
| Rendering | Three.js, with the render setup as project source | Three.js | Godot renderer | Unity renderer | Unreal renderer |
| Game systems | Loop, input, Rapier physics, UI hooks, playtests | Bring your own | Built in | Built in | Built in |
| Desktop and mobile | Native runtime for Windows, macOS, Linux, Android | Needs a separate native host | Engine export | Build profiles and platform modules | Engine packaging |
Pick ThreeNative when
- Your game already runs on Three.js, or your team knows it well.
- You want game code in plain TypeScript files, reviewed and versioned like any other code, with npm packages available.
- You want one
src/game.tsfor the browser, desktop and Android. See Native runtime for platform support. - You want to edit lighting, materials and post effects as source files in the project.
- You want a React HUD and automated playtests against the running game.
Pick something else when
- Three.js alone: you are building a 3D scene or visualisation, not a game, and ship only to the web.
- Godot: you want an integrated scene editor with its own scripting. ThreeNative physics borrows
Godot names such as
CharacterBody3DandRigidBody3D, but has no editor. - Unity: your team works in C# and relies on the Unity editor and its platform tooling.
- Unreal Engine: you want its world-building and content tools, Blueprints and C++.
- Any of the three engines: you need to ship on iOS. ThreeNative does not support it yet.
Vendor documentation
- ThreeNative README
- Three.js: creating a scene
- Godot scripting languages
- Unity platform development
- Unreal tools and editors
Measured numbers and a side-by-side table are on the compare page.