Khronos added middleware data to the extensions matrix to show where features actually reach the application. See how to use it in architecture.
Direct answer
On April 7, 2026, Khronos extended the OpenXR Extension Matrix with self-declared data from middleware such as Godot, LÖVR, StereoKit, Unity, and Unreal. The matrix differentiates what the runtime and hardware implement from what the engine or framework exposes to the application. This helps plan portability, but it is not middleware certification: each combination of engine, plug-in, runtime and device still needs its own testing.
Compliance does not mean all extensions
A runtime can conform to OpenXR without implementing every optional feature. Core portability does not guarantee passthrough, hands, composition or specific tracking.
Middleware is another compatibility layer
The engine calls the runtime and chooses which extensions to expose. A feature present in the headset may remain unavailable due to version, plug-in or abstraction.
Matrix guides discovery, do not accept
Middleware data is self-declared and does not equate to Khronos certification. Use the matrix to select combinations to test, not to dispense with validation.
Architecture must declare degradation
Separate essential, optional and exclusive capabilities. When an extension is missing, the application needs to disable the feature, change the interaction or clearly prevent its use.
Nexus Reading
The matrix transforms invisible fragmentation into product decisions. It helps you estimate support cost and choose the smallest set of extensions that delivers value across all target devices.
FAQ
Does OpenXR guarantee all features in any headset?
No. The standard defines a core and extensions, support for which varies across runtimes, devices, and middleware.
Does Khronos certify Unity and Unreal in this matrix?
No. The page states that middleware data is self-declared and not verified or endorsed by Khronos.
How to use the matrix in a project?
Map essential features, filter candidate combinations, and perform regression on the exact engine, plug-in, runtime, and hardware version.
Essential guides to delve deeper into the decision
This editorial analysis was produced by Nexus from the official sources below, consulted on September 16, 2026. The text is original and interprets practical implications for companies.
- Khronos — Adds Middleware Insights to the OpenXR Extension Matrix: announcement, distinction between runtime and middleware, and initial list of participants.
- Khronos — OpenXR Extension Support Matrix: Current support matrices by runtime and middleware, with warning about self-declared data.
Date reported by the main source: April 7, 2026.