On this page
- What problem it solves
- How it works — behavior graphs
- Security model
- Ecommerce constrained mode (Level 0)
- Companion extensions
- Relationship to KHR_materials_variants
- KHR_interactivity vs custom engine scripting
- Confirmed adopters (as-of 2026-07-16)
- Ecommerce use cases
- Platform support (as-of 2026-09-25)
- Contradictions
- Ratification timeline
- Key resources
- Key terms
- Next frontier
KHR_interactivity
KHR_interactivity
A Khronos glTF (GL Transmission Format)|glTF 2.0 extension that embeds portable, self-contained interactive behavior graphs directly inside a 3D asset file — allowing product configurators, animated how-to guides, and variant-switching experiences to work on any compliant viewer without external JavaScript. Submitted for ratification on 2026-07-16 by the 3D Commerce Working Group|Khronos 3D Formats Working Group.
What problem it solves
Per the Khronos public comment release (2024-06-18, Dwight Rodgers, Adobe): content creators previously needed to write JavaScript to add interactivity to glTF (GL Transmission Format)|glTF assets. This approach fails when:
- The asset is deployed on a third-party page where custom JS cannot run
- The target is a headset or mobile app (no browser JS engine)
- Cross-platform consistent behaviour is required across multiple engines
KHR_interactivity embeds the interaction logic inside the asset itself. Neil Trevett (Khronos President, 2026-07-16): "glTF assets are no longer just something you look at: They become experiences you can use, portable across every platform, viewer, and engine that supports glTF."
How it works — behavior graphs
The extension adds a behavior graph: a directed acyclic graph (DAG) of interconnected nodes embedded in the glTF file. Node types (per Khronos blog, 2022-11-03): events, actions, variables, queries, logic, and flow control.
Behavior graphs can read and write glTF properties at runtime via JSON Pointer-based operations (the glTF Asset Object Model), including: node transforms, material properties, morph target weights, and other asset properties (Khronos public comment, 2024-06-18).
The system is inspired by game engine visual scripting: Unreal Blueprint (2013), Unity Visual Scripting, NVIDIA OmniGraph (Khronos blog, 2022-11-03).
Security model
Per Khronos blog (2022-11-03): the behavior graph is Turing-Complete but sandboxed — only explicitly declared, pre-defined node types can execute. Load-time validation checks all nodes before execution. Limits on nodes processed per time-slice prevent infinite loops and denial-of-service.
Arik Barnett (Amazon senior SDM, Khronos blog 2025-05-20): "This exciting extension allows brands to program product demonstrations in a portable fashion across all supporting engines while maintaining Amazon's security standards by eliminating third-party code risks."
Ecommerce constrained mode (Level 0)
Per Khronos blog (2022-11-03): a "continuum of interactivity" scales from constrained ecommerce viewers to rich game-engine experiences. Level 0 constraints for web/ecommerce: all parameter values must be constants; "next" is the only output socket; no interaction without a user-initiated event; overall action count kept small.
Companion extensions
Submitted for ratification alongside KHR_interactivity (Khronos press release, 2026-07-16):
| Extension | Behaviour |
|---|---|
| KHR_node_selectability | Tap to show/hide content |
| KHR_node_hoverability | Hover to animate |
| KHR_node_visibility | Show/hide based on scene state |
| KHR_gaussian_splatting | AI-captured 3D scene format (adjacent, separate use case) |
All unavailable companion extensions degrade gracefully to no-ops (backward-compatible) (Khronos public comment, 2024-06-18).
Relationship to KHR_materials_variants
KHR_materials_variants (2020, authored by Shopify engineers for the 3D Commerce Working Group): a static data structure that bakes multiple material variants sharing the same geometry into a single glTF file, switched by API call from the host viewer. File size efficiency: instead of three separate 5MB files (15MB), one file with shared 4MB geometry + 1MB per variant material (Khronos blog, 2020-11-11).
KHR_interactivity is the execution engine that drives variant switching as a response to user events. Demonstrated (GamesBeat, 2026-07-16): clicking a sofa's fabric triggers a 360-degree rotation; during rotation the material switches to the next available variant.
KHR_interactivity vs custom engine scripting
Synthesised from Khronos sources (2022–2026):
| Dimension | KHR_interactivity | Custom Three.js / Babylon.js code |
|---|---|---|
| Location of logic | Embedded in the glTF file | External JS in the host application |
| Portability | Any KHR_interactivity-compliant viewer | Tied to the specific engine |
| Third-party deployment | Works on any supporting marketplace or AR app | Cannot run on third-party pages |
| Who controls behaviour | Asset creator | Developer with host-page access |
| Security model | Sandboxed — pre-defined node types only | Full JavaScript, unrestricted |
| Authoring | Visual scripting (Unity, Needle Engine) | Hand-written code |
| Offline/headset support | Yes — no browser JS engine required | Browser or runtime-specific |
Confirmed adopters (as-of 2026-07-16)
Per Khronos press release and GamesBeat (2026-07-16):
| Adopter | Status |
|---|---|
| Babylon.js | Full Phase 1 playback support — live |
| Needle UnityGLTF Exporter | Export from Unity Visual Scripting — live; Needle Engine on roadmap |
| Amazon | Functional prototype of interactive glTF authoring tool |
| Magic Leap | Completed Unity runtime playback engine (via UnityGLTF) |
| Google Android XR | KHR_interactivity playback via Jetpack XR SDK — planned |
| UX3D glTF-Sample-Viewer | Full interactivity support added |
David Catuhe (Babylon.js creator, GamesBeat 2026-07-16): "Babylon.js fully supports KHR_interactivity today."
Eva Ma (Meta, glTF Interactivity Chair, 2026-07-16): "The behavior graph model and extensible design we've landed on gives the ecosystem a solid, future-proof foundation."
Ecommerce use cases
Named by Khronos sources across 2024–2026: product configurators, interactive how-to guides, assembly instruction viewers, mini-games, variant-switching colour pickers. Amazon (2025-05-20): "interactive animations, technical diagrams, and assembly instructions."
Snap / Alter Agents: 66% less likely to return after AR engagement; 80% more confident purchasing with AR (survey 2022, 4,028 shoppers across US/UK/France/Saudi Arabia — predates KHR_interactivity; market-demand context only).
3D E-Commerce Global Market sizing (Research and Markets, 2026): $8.53B in 2025 → $10.54B in 2026, 23.6% CAGR (as-of 2026). Covers browser-based 3D broadly; no KHR_interactivity-specific revenue breakdown found.
Platform support (as-of 2026-09-25)
[!unverified] Shopify natively supports glTF (.glb) and USDZ, and contributed to KHR_materials_variants (2020). No source found confirming native KHR_interactivity support in the Shopify storefront viewer.
[!unverified] Google's
<model-viewer>web component (the primary viewer used for Shopify and Google Store product AR) has not been confirmed as supporting KHR_interactivity. Google's involvement is via Android XR / Jetpack XR SDK. Web model-viewer KHR_interactivity support remains unconfirmed as of September 2026.
[!unverified] Three.js was listed as a target viewer in the June 2024 public draft. Three.js support was not confirmed live in the July 2026 ratification announcement (which listed Babylon.js explicitly).
Contradictions
Three.js target vs. absence from ratification announcement: the June 2024 public comment release (Khronos, 2024-06-18) named Three.js, Babylon.js, and model-viewer as targeted viewers. The July 2026 ratification submission announcement (Khronos, 2026-07-16) listed Babylon.js as the confirmed live implementation but did not include Three.js — suggesting Three.js support lagged or was descoped. No source explicitly states Three.js does not support KHR_interactivity; absence from the announcement is the signal.
Ratification timeline
| Date | Event | Source |
|---|---|---|
| 2022-11-03 | Foundational behavior graph design doc | Khronos blog (Dwight Rodgers / Adobe; Ben Houston / Threekit) |
| 2024-06-18 | Spec released for public comment | Khronos blog (Dwight Rodgers, Adobe) |
| 2025-05-20 | Final feedback call / pre-ratification | Khronos blog (Preetish Kakkar + Dwight Rodgers, Adobe) |
| 2026-07-16 | Submitted for ratification | Khronos press release |
| 2026-07-23 | SIGGRAPH glTF Ecosystem forum (in-person + Zoom) | Khronos events page |
| 2026-09-25 | Ratification completion — not yet confirmed | No source found |
Key resources
- Spec (GitHub): https://github.com/KhronosGroup/glTF/blob/main/extensions/2.0/Khronos/KHR_interactivity/Specification.adoc
- Test assets: https://github.com/KhronosGroup/glTF-Test-Assets-Interactivity
- Behavior graph reference library (open source): https://github.com/bhouston/behave-graph
- Authoring tool (WIP): https://github.com/KhronosGroup/glTF-InteractivityGraph-AuthoringTool
Key terms
| Term | Meaning |
|---|---|
| Behavior graph | DAG of interconnected nodes embedded in the glTF file; defines interactive logic |
| glTF Asset Object Model | JSON Pointer-based system by which behavior graph nodes read/write glTF properties at runtime |
| Level 0 (constrained mode) | Ecommerce-safe execution profile: constants only, small node count, user-initiated events only |
| KHR_materials_variants | Static companion extension; pre-bakes material variants into file; KHR_interactivity drives the switching |
| Companion extension | KHR_node_selectability / hoverability / visibility — granular interaction triggers submitted together with KHR_interactivity |
Next frontier
- KHR_materials_variants (referenced here; page may already exist — cross-check)
- Babylon.js (entity page; confirmed first major adopter)
- Object Capture (Apple photogrammetry pipeline — adjacent 3D asset creation)
- Reality Composer Pro (Apple authoring tool — adjacent)
- OpenUSD / AOUSD (standards body — parallel track to Khronos/glTF)
- Android Scene Viewer (Google's Android AR counterpart to AR Quick Look; complements KHR_interactivity on Android)