Browser specifications

Use runtime feature detection for 2D, screen-based 3D, and immersive content in Meta Quest Browser. Browser uses the Chromium rendering engine, but both products change over time.

Do not use the user-agent string for feature detection. Check each web API or mode before you show a feature that needs it.

For immersive content, detect WebXR support before you offer an immersive session. See the WebXR overview for the 3D path and related standards.

The following user-agent string is an example, not a feature contract. Browser and Chromium version numbers change over time.

Mozilla/5.0 (X11; Linux x86_64; Quest 3)
AppleWebKit/537.36 (KHTML, like Gecko)
OculusBrowser/39.2.0.0.56.754450099
Chrome/136.0.7103.177
VR
Safari/537.36

The device token in a user-agent string can vary by device:

Use these values only to understand or troubleshoot an observed user-agent string. Use feature detection to control site behavior.

Browser supports desktop and mobile modes. Desktop mode is the default. In mobile mode, the user-agent string includes the Mobile VR token and Browser applies the meta viewport tag. In desktop mode, the token is absent and Browser ignores meta viewport tags.

The following documented window dimensions are useful test cases for 2D and screen-based 3D content. Treat them as examples rather than a fixed feature contract.

Users can resize the Browser window. Test both browsing modes and multiple window sizes instead of relying on one user-agent string or viewport size.

Test hosted content in Meta Quest Browser on a headset. Browser supports remote inspection with Chrome DevTools, including the console, profiler, and DOM inspector.

Follow Debug Browser content to connect a headset and inspect an open Browser tab.