Browser Specs

This topic provides the basics for developing content for Browser. If you have an experience you would like to feature on the New Tab Page, use the submission process described on New Tab Page Guidelines and Submission to submit for consideration.

This UA string should not be used for feature detection.

An example user-agent (UA) string for Browser is:

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” of the UA string depends on the device model:

Browser allows users to switch into mobile mode, in which case the “VR” token above becomes “Mobile VR”.

For Meta Quest 2, Browser renders both 2D web page content and WebXR at a 90Hz refresh rate. On Quest, Browser uses a 72Hz refresh rate. When watching fullscreen media, Browser optimizes the device refresh rate based on the frame rate of the video.

For 2D websites, users can resize the width of the content anywhere from 500px to 2000px, with a default width of 1280px. The height can be resized from 495px to 1070px, with a default of 670px.

Browser supports both mobile and desktop browsing modes, with desktop as the default. In mobile mode, the Mobile token appears in the UA string and the meta viewport tag is supported. In desktop mode, there is no Mobile token in the UA string and any meta viewport tags are ignored. Developers should test in both modes to ensure compatibility. WebXR content should be made available based on feature detection rather than UA string sniffing.

Browser supports using the Google Chrome (or other Chromium-compatible browsers) developer tools to debug sites on your Meta Quest device. This lets you access all of your familiar tools including the console, timeline, profiler, DOM viewer, etc. You’ll also be able to see a visual snapshot of what’s on screen in the headset right from your computer screen.

To get set up, you’ll need to enable Developer Mode on your headset and connect it to your computer using the Android Platform Tools. See Debugging Your Content for how to get set up. Once set up and connected, your tabs from Browser will appear in the Remote Devices panel of the dev tools. Click Inspect to start debugging a tab in Browser.