Three-Live 3D, CAD & Spatial XR Compiler

Disclaimer: This is not an officially supported Google product.

Three-Live

AI-First Native 3D, CAD & Spatial Computing: On-device JIT compiler turning live, AI-generated Three.js into native Android (Google Filament & Jetpack XR), iOS & visionOS (Apple RealityKit), and WebXR.

[⚡ Quickstarts (Android • iOS • CLI • Web)](#quickstarts) • [📦 Install (JitPack • SwiftPM • Cargo • npm)](#install-packages-and-bundles) • [▶ Live 3D Studio](https://google.github.io/three-live/three/) • [🥽 Live Spatial XR Studio](https://google.github.io/three-live/xr/) • [📚 Docs](#documentation-guide)

LLMs and developers excel at writing concise Three.js code—not hundreds of lines of platform-specific native 3D, shader, and AR boilerplate. Three-Live compiles standard Three.js (THREE.Mesh, THREE.CSG, userData.xr, KHR_interactivity) on-device in a sandboxed Rust VM and renders natively in Google Filament and Jetpack XR SceneCore on Android, Apple RealityKit and Quick Look on iOS and visionOS, headless 4-up PNG contact sheets (`three-live-cli`) for AI coding agents, and WebGL2 / WebXR on the Web.

---

Quickstarts

1. Run Three.js natively on Android (Google Filament & Jetpack XR SceneCore)

Compile standard Three.js code over zero-copy JNI and drive native Google Filament rendering, 60 Hz physics, and Jetpack XR SceneCore spatial entities:

import com.google.threelive.FilamentHelper

import com.google.threelive.XRLiveRuntimeSession import com.google.threelive.XRLiveSceneCoreHelper

val threeJsCode = """ const core = new THREE.Mesh( new THREE.IcosahedronGeometry(0.55, 3), new THREE.MeshStandardMaterial({ color: 0x38bdf8, metalness: 0.85, roughness: 0.15 }) ); core.userData.xr = { grab: '2-hand', orbit: { speed: -0.4 } }; scene.add(core); """.trimIndent()

// Compile Three.js to a zero-copy GLB ByteBuffer and load directly into Google Filament val holder = FilamentHelper.loadModelZeroCopy(threeJsCode) { buffer -> assetLoader.createAssetFromBinary(buffer) }

// Step live KHR_interactivity graphs, 60 Hz rigid-body physics, and spatial traits per frame val runtime = XRLiveRuntimeSession.fromGlb(holder.byteBuffer) runtime.step(dtSeconds = 1.0 / 60.0)

// Or attach interactive spatial traits (grab, scale, billboard, anchor) in Android XR SceneCore XRLiveSceneCoreHelper.attachTraitsFromGlb(xrSession, entity, holder.byteBuffer)

2. Run Three.js natively on iOS, macOS, and visionOS (Apple RealityKit)

Compile the exact same Three.js code into Apple RealityKit (ARView / RealityView) or .usdz:

import ThreeLiveCompiler

import RealityKit

@MainActor func loadSpatialScene(from threeJsCode: String, into arView: ARView) async throws -> XRLiveRealityKitSession? { let glb = try ThreeCompiler.compileToGLB(script: threeJsCode) let entity = try await RealityKitHelper.loadEntity(fromGLB: glb) XRLiveRealityKit.installTraits(on: entity, in: arView)

// Bind live KHR_interactivity, 60 Hz physics, and spatial traits to RealityKit SceneEvents.Update let session = XRLiveRealityKitSession(glbData: glb, root: entity) session?.installInputTargets() session?.start() return session }

3. Verify & compile Three.js headlessly for AI agents (three-live-cli & MCP server)

Render a 4-up orthographic/camera contact sheet (zero GPU required), run the spatial linter for JSON frustum/overlap telemetry, compile scene.js to .glb / .usdz, or attach three-live-cli mcp as a zero-dependency Model Context Protocol (MCP) stdio server (three_live_validate, three_live_render, three_live_convert, three_live_sim) in Claude Code, Cursor, Gemini CLI, or Windsurf:

$ npx three-live-cli render scene.js --view=quad --grid --annotations -o contact_sheet.png

$ npx three-live-cli validate scene.js --json $ npx three-live-cli convert scene.js -o model.usdz

Or register the built-in MCP server for closed-loop visual + spatial AI verification:

$ claude mcp add three-live -- npx -y -p three-live three-live-cli mcp

4. Run on the Web ( and )

On the web, (< 30 KB gz viewer, < 70 KB gz with the live Three.js compiler) and (< 82 KB gz) render the same Three.js scenes in WebGL2 and 6DoF WebXR with 1-tap mobile AR handoff:

// Standard Three.js scene (runs identically in Android, iOS, CLI, and Web)

const mesh = new THREE.Mesh( new THREE.TorusKnotGeometry(0.4, 0.14, 64, 16), new THREE.MeshStandardMaterial({ color: 0x38bdf8, metalness: 0.8, roughness: 0.15 }) ); mesh.userData.xr = { grab: '1-hand', billboard: 'capsule' }; scene.add(mesh);

---

Install packages and bundles

Package installation

• 1. Android (JitPack, GitHub Packages Maven, prebuilt release AAR, or source):

• JitPack (`https://jitpack.io`, no authentication required): Add maven("https://jitpack.io") to settings.gradle.kts, then add:

kotlin dependencies { implementation("com.github.google.three-live:compiler:v1.3.1") // Optional adapters: :filament, :firebase-ai, :detect-mlkit, :hands-androidxr, :hands-mediapipe }

• GitHub Packages Maven (`https://maven.pkg.github.com/google/three-live`): Configure the repository in settings.gradle.kts and add implementation("com.google.threelive:compiler:1.3.1") (plus optional :filament, :firebase-ai, :detect-mlkit, :hands-androidxr, :hands-mediapipe).
• Prebuilt AAR: Download three-live-compiler-release.aar (includes arm64-v8a, armeabi-v7a, and x86_64 JNI .so libraries) and optional adapter AARs (three-live-filament-release.aar, etc.) from [GitHub Releases](https://github.com/google/three-live/releases) into app/libs/ and add implementation(files("libs/three-live-compiler-release.aar")).
• Maven Local (`com.google.threelive:compiler:1.3.1`): Run ./gradlew :mobile:android:publishReleasePublicationToMavenLocal and add implementation("com.google.threelive:compiler:1.3.1").
• From source: Run make android (or bash scripts/build_android_aar.sh).
• 2. iOS, macOS, and visionOS (Swift Package Manager):

swift .package(url: "https://github.com/google/three-live.git", from: "1.0.0")

Swift Package Manager automatically resolves the prebuilt, checksum-pinned ThreeLiveCompiler.xcframework.zip archive from GitHub Releases—no local Rust or Node.js toolchain is required.

• 3. Rust CLI (`three-live-cli`) and library crate (`Crates.io`, prebuilt binaries, or source):

• Crates.io (library & CLI):

`bash cargo add three-live-compiler

Or install the standalone CLI binary from Crates.io:

cargo install three-live-compiler --bin three-live-cli `

• Prebuilt binaries: Download standalone binaries for macOS (arm64 and x86_64), Linux (x86_64 and aarch64), and Windows (x86_64.exe) from [GitHub Releases](https://github.com/google/three-live/releases).
• From source: Run make rust (npm run build && cargo build --manifest-path compiler/Cargo.toml --release --bin three-live-cli).
• 4. Web (npm, CDN, prebuilt release, or source):

• npm:

bash npm install three-live xr-live

• Hosted ES module (`jsDelivr` or GitHub Pages CDN): Load https://cdn.jsdelivr.net/npm/three-live/dist/three-live.min.js or https://google.github.io/three-live/dist/three-live.min.js.
• Prebuilt bundle archive: Download three-live-web-dist.zip from [GitHub Releases](https://github.com/google/three-live/releases).
• From source: Run git clone https://github.com/google/three-live.git && cd three-live && npm install && npm run build.

---

Why Three-Live and XR-Live

Native mobile and headset AR/XR from Three.js

In practice, browser WebXR (navigator.xr) only covers part of the device landscape:

• Android System `WebView`, iOS Safari, and iOS `WKWebView` don't support WebXR. A WebXR-only app can't run inside an embedded WebView or WKWebView in a native Android or iOS app, and can't enter AR in Safari on iPhone or iPad.
• Static OS handoffs (`Scene Viewer` and `AR Quick Look`) strip interactivity. Exporting a static .glb or .usdz file to the OS previewer works for viewing a model, but drops Three.js animate() loops, 60 Hz physics, custom state, and interactive plugins.
• Browser WebXR doesn't use native spatial compositors. On Android, browser WebXR renders WebGL2 in the browser process rather than using Google Filament or Jetpack XR SceneCore's HomeSpace shared space. On visionOS, browser WebXR runs in an isolated fullscreen VR session without camera passthrough or SwiftUI Shared Space integration.

Three-Live solves this by compiling the same Three.js code on-device and running it natively on each platform's own engine:

Compare and

The following table compares the two runtime tiers across Android, iOS, and Web:

| Capability | three-live (Core 3D, CAD & Ani