OpenXR for Spatial Displays

Write once. Run on any spatial display. DisplayXR is the OpenXR extensions spatial displays need, an open-source reference runtime, Unity and Unreal plug-ins, and a browser for 3D on the web. Portable across engines, graphics APIs and display makers, and agent-ready, with MCP built into the runtime.

Why it exists

Write once, for every spatial display

Today every spatial display ships its own SDK, so an app is written again for each one, or not at all. OpenXR already solved this for headsets: one standard, any device.

DisplayXR builds on OpenXR rather than starting over. It is an open-source OpenXR runtime that runs the official Khronos conformance suite, plus the XR_DXR_* extensions OpenXR needs for spatial displays. Displays, trackers and 2D-to-3D models plug in underneath as components; apps never see the difference.

Without a standard, one app needs a separate SDK integration per display; with DisplayXR, the same app hits one OpenXR target and runs on any display.

Where a display differs from a headset

OpenXR was written for headsets, which are worn and own the whole view. A display sits on a desk and shares its screen with 2D. Four examples of what the extensions add:

Where the display is

Headset: A headset moves with your head, so OpenXR hands the app a symmetric field of view.

DisplayXR adds: The panel's size and position in metres, the tracked eye positions and the rendering modes, so each eye gets the right off-axis view. A 10 cm cube renders 10 cm.

Many windows, not one screen

Headset: A headset session is exclusive: it owns the whole display, because on a headset that is the whole world.

DisplayXR adds: Window binding: the app hands the runtime its own window, and each window keeps its 3D while it moves.

2D and 3D in the same window

Headset: Core OpenXR's layers (projection, quad, cube, cylinder) describe a world, not a 3D region inside a 2D window.

DisplayXR adds: 2D/3D zones: 3D inside, a flat page around it. This is the same capability a 3D object inside a web page uses.

3D over the desktop, when you want it

Headset: In a headset there is no desktop: one compositor draws everything the eyes see.

DisplayXR adds: Transparent presentation and a depth budget, so 3D content can live on top of the desktop without taking it over.

What is a spatial display? →

Pick your path

Start where you are

DisplayXR Browser

Same web page. Now in 3D.

A Chromium-based browser for spatial displays: a page's 3D products, movies, photos and calls appear in depth, right in the page, and every other site works as usual.

Shop

See the product, not a photo of it.

Watch

3D movies, right in the page.

Call

Face to face, in depth.

Runs on

  • Windows
  • macOS
  • Linux
  • Android
  • Unity
  • Unreal
  • The web

Things you can check

Zero

vendor identifiers in the shipped runtime

Neutrality is enforced in the binary: the runtime never weaves, the vendor's plug-in always does, and CI fails any change that puts a vendor symbol in the runtime's link line.

Every release

runs the official Khronos OpenXR conformance suite

A smoke subset on pull requests, and the full non-interactive suite nightly and on every release tag, hardware-free, against the simulated display.

No hardware

needed to build for a spatial display

The runtime ships a simulated display in an ordinary window, with the viewer's eyes on the mouse and keyboard: the same driver the conformance suite runs against.