The Khronos candidate extension incorporates behavior graphs into the 3D asset. Understand the potential for web, XR, and cross-platform configurators.
Direct answer
On July 16, 2026, Khronos submitted the glTF 2.0 KHR_interactivity extension for ratification. It allows describing interactive behaviors in graphs within the 3D asset itself, reducing the need to reprogram the same logic for each runtime. The benefit depends on ratification, real support of the tools and careful definition of what should remain in the asset or application.
From portable model to portable behavior
glTF already carries geometry, materials and animations. The extension adds graphs that relate events, variables and operations, allowing part of the interaction to follow the asset between tools and platforms.
Where can this reduce rework
Configurators, 3D instructions, digital twins, and XR experiences repeat selection, animation, and state logic. Standardized behavior can slow down specific implementations, especially when the same asset appears across web, mobile, and headset.
What should not be placed in assets
Authentication, pricing, sensitive rules, and enterprise integrations continue to belong to the application or backend. The graph must contain portable and secure behavior, without exposing secrets or replacing business control.
Ratification does not guarantee universal support
Before relying on the extension, confirm which exporters, viewers, and engines interpret it, which nodes are supported, and how the runtime reacts to unknown resources. Keep fallback to the main task.
Nexus Reading
Standardized interactivity can make 3D more reusable and reduce the cost of multiple channels. The real gain will come from pipelines that validate the asset once and preserve consistent behavior at every touchpoint.
FAQ
Is KHR_interactivity already ratified?
The announcement states that the extension has been submitted for ratification; the status must be confirmed before treating it as final.
Does the extension replace application code?
No. It carries portable behaviors, while business, data and security rules remain in application.
What is the main benefit?
Reuse part of the interactive logic of the same 3D asset in different tools and runtimes.
Essential guides to delve deeper into the decision
This editorial analysis was produced by Nexus from the official sources below, consulted on September 11, 2026. The text is original and interprets practical implications for companies.
- Khronos Group — glTF Interactivity Extension Submitted for Ratification: status, purpose, and initial adoption of the extension.
- KhronosGroup glTF — KHR_interactivity specification: technical specification and official structure of the candidate extension.
Date reported by the main source: July 16, 2026.