Google Three-Live: Run AI-Generated 3D and AR in 50 KB Google released Three-Live on November 3, an Apache 2.0 library and on-device Rust compiler that converts AI-generated Three.js code into production-safe 3D and AR for web, Android, and iOS in roughly 50 KB gzipped. Three-Live treats LLM-written Three.js as untrusted input, running it inside a sandboxed Rust VM powered by the Boa ECMAScript engine and serializing the scene graph to binary glTF 2.0 (.glb) or USDZ in 2–5 milliseconds, so the script never executes in a user's browser or device. Google cites that around 40% of LLM-generated code carries measurable security vulnerabilities, and the sandbox removes network and storage globals, freezes Object.prototype, and enforces CPU instruction fuel limits and geometry quotas capping vertices, triangles, meshes, and procedural textures. Google shipped Three-Live https://opensource.googleblog.com/2026/11/introducing-three-live-ai-generated-3d-ar-webxr.html on November 3 — an Apache 2.0 library and on-device Rust compiler that takes AI-written Three.js code and turns it into production-safe 3D and AR across web, Android, and iOS in roughly 50 KB. The reason it exists is worth pausing on: LLMs are now good enough at writing Three.js to be useful, but Google does not trust that output to run directly in front of users. So they built a compiler instead. The Problem With AI-Generated Three.js Ask a modern LLM to build a 3D product configurator or an AR try-on scene in Three.js https://threejs.org/ , and you will get working code most of the time. The problem surfaces when that code runs in production. Around 40% of LLM-generated code carries measurable security vulnerabilities. For Three.js specifically, the failure modes are concrete: stale API calls that break on current versions, loops that generate runaway geometry and freeze the browser, scripts that try to fetch remote assets, and in some cases imports from libraries that do not exist. Manual review helps, but it does not scale. Three-Live’s answer is to treat AI-generated Three.js as untrusted input and compile it before it ever reaches a renderer. How the Compiler Works The pipeline is straightforward. Three-Live takes a Three.js JavaScript string, runs it inside a sandboxed Rust VM powered by the Boa ECMAScript engine, and serializes the resulting scene graph directly into a binary glTF 2.0 .glb or USDZ buffer. The whole process takes 2–5 milliseconds. The AI-generated script never executes in a user’s browser or on their device. The sandbox is strict by design. Network and storage globals are removed so scripts cannot make external requests. Object.prototype is frozen to prevent prototype pollution. CPU instruction fuel limits and geometry quotas — capping vertices, triangles, meshes, and procedural textures — ensure runaway scripts cannot freeze the host application. A script that tries to do too much simply fails during compilation, not at runtime. Using It on the Web On the web, Three-Live ships as a