Develop

New Tab Page Guidelines and Submission

Meta is looking for great WebXR content to feature on the Browser’s New Tab Page.

WebXR Submission Form

If you have an experience you would like to feature on the New Tab Page, use our WebXR Submission form⁠ to submit your feature for consideration.

This page contains the general criteria we’ll apply when determining which experiences to feature on the New Tab Page. We change or rotate what content we feature to ensure we’re showing fresh, relevant, and diverse content for Browser users. Meeting the technical criteria below is not a guarantee your experience will be featured.

Submission and Review Process

After you submit your experience through the WebXR Submission form⁠, it goes through a multi-step review pipeline:

Submission: You complete the submission form with details about your immersive web experience and basic contact information.

Initial Review: Your submitted experience is tested to assess whether it meets a minimum quality bar.

Detailed Review: If the initial review is positive, your experience undergoes three area-specific reviews:

QA Review — Your experience is loaded on all currently supported Quest devices. Reviewers assess overall quality, any issues encountered during testing, and basic functionality.

Content Review — Evaluates interaction design, user comfort, and whether the content is suitable for display on the NTP.

Technical Review — Evaluates performance, rendering consistency, and technical quality of the experience across supported devices.

Developer Iteration: You may receive feedback and have the opportunity to iterate on your experience before a final decision is made.

Curation: If all reviews reach a positive consensus, your experience is added to the curated NTP content. An existing experience may be rotated out to make room.

Rejection: If consensus is not reached during the review process, the submission is not accepted. You are welcome to resubmit after addressing any feedback provided.

Initial Promotion and Ranking

Once your experience is accepted, it will be promoted to the top of the NTP shelf for an initial period of 4 weeks. After this initial promotion period, your experience will be ranked alongside all other WebXR titles based on monthly user traffic.

What reviewers look for during QA

Overall quality and polish of the experience

Whether users can access and use the site’s basic functionality

Issues encountered during testing across supported devices

A positive recommendation generally occurs when no major issues are found during testing. Minor cosmetic issues or low-priority bugs are acceptable. A negative recommendation may occur if high-priority issues are found, too many inconsistent issues arise, or users cannot complete basic interactions.

New Tab Page Content Guidelines

Content Guidelines

We only feature content that adheres to our Content Guidelines

We only feature direct links to individual VR experiences, as opposed to directories of VR experiences.

You must own or otherwise have rights to the content/experience you are submitting, and have the authority to grant Meta permission to feature the experience, including any assets or descriptions you provide to Meta. Your content/experience must not infringe upon or violate the rights of any third party.

We prefer experiences that provide unique or differentiated value to users. We generally do not feature tech demos that don’t provide meaningful entertainment or utility.

Content should be appropriate for all ages 13 and older.

Hand tracking-enabled experiences should provide an easily discoverable UI option to exit WebXR to return to the browser.

If an exit option is not made available in the experience’s UI, then the experience must render a full hand model (e.g., including fingers and all joints) such that users can easily see their hands to perform the system gesture to exit WebXR.

Technical Requirements

Meeting the following selection of Quest Virtual Reality Check (VRC) Guidelines is strongly encouraged and failing to meet these will likely result in not being featured on the New Tab Page:

VRC.Quest.Performance.1 - The experience must run at 60Hz or faster on Quest 1 and 2 (recommended 72Hz on Quest 1, 72Hz+ on Quest 2).

VRC.Quest.Performance.3 - The experience must be responsive within 4 seconds of entering VR or show a loading indicator.

VRC.Quest.Functional.1 - The experience runs without crashes, freezes, or extended unresponsive states.

VRC.Quest.Functional.3 - The experience must not leave the user stuck at any point in the experience.

VRC.Quest.Functional.5 - The experience must respond to the HMD’s positional tracking as well as orientation.

VRC.Quest.Input.3 - In-application hands and controllers should line up with the user’s real-world counterparts in position and orientation as closely as possible.

VRC.Quest.Input.8 - For applications that support hand tracking, the system gesture is reserved, and should not trigger any other actions within the application.

Technical Recommendations

Meeting the following VRCs are also recommended as best practices:

VRC.Quest.Audio.1 - The experience should support spatial 3D audio.

VRC.Quest.Functional.2 - The experience must pause when the user removes the HMD or opens Universal Menu.

VRC.Quest.Functional.9 - In experiences using a Local tracking space, the user must be able to reset their forward orientation.

VRC.Quest.Functional.10 - Headlocked menus and UI elements are generally uncomfortable for the user and should be avoided.

VRC.Quest.Input.2 - When picking up objects within the app, use the touch controller’s grip button rather than the trigger button.

VRC.Quest.Input.5 - For applications that support hand tracking, hands must render in the correct position and orientation, and must animate properly.

VRC.Quest.Input.6 - For applications that support hand tracking, hands must be hidden if they are not being tracked or if tracking confidence is low.

VRC.Quest.Accessibility - All VRCs.