Distribution Options
Updated: Mar 25, 2025
Meta Platforms Technologies provides several options for selling and distributing apps on our platform. Review them to find the distribution options that best meets your needs.
Distribution Option | Description | Discovery | Meta Quest | Oculus Rift |
---|
Meta Horizon Store | Comprehensive app review. | App discoverable in Meta Horizon Store catalog across all supported platforms: VR, mobile, and web. | ✓ | |
Link PC VR Store | Comprehensive app review. | App discoverable in Link PC VR Store catalog across all supported platforms: VR, mobile, desktop app, and web. | | ✓ |
Apps in the Meta Horizon Store and Link PC VR Store also include:
- the ability to distribute a limited number of private builds such as for alpha or beta testing by way of release channels.
- the ability to generate limited Meta Platforms Technologies Keys (described below) that can be redeemed for a copy of your app.
For more information on creating apps in the Developer Center and get started, see
Create Apps.
Meta Horizon Store apps showcase the best Meta Quest apps VR has to offer. The Meta Horizon Store provides an easily discoverable method of public distribution with a high quality bar and standards for distributions. From July 31st, 2024 on, all Quest apps must be submitted to the Meta Horizon Store.
The Link PC VR Store is where Rift apps are available publicly for download. It provides an easily discoverable method of distribution for Rift apps, but requires a thorough review of your app by Meta Platforms Technologies. To distribute an app in this form, you upload your app to the Developer Center and submit it for review by our Store team. They review your app to ensure it meets the technical and content criteria outlined in
Store Review Policies. Once your app passes this review, it will appear in the Link PC VR Store in one of the following sections:
- Apps: utility applications such as video players and creativity tools.
- Games: interactive content with rules where the player can either win or lose.
- Entertainment: narrative-driven experiences that may be minimally or fully interactive, but lack the ruleset and win/lose state of a game.
- Early Access: content that is interesting, playable, and well on its way to being finished. This category provides a means for developers to charge for their work-in-progress, while giving early users the chance to be a part of the development process.
Meta Platforms Technologies Keys (Keys) are 25 character alphanumeric codes that you can generate as needed after your app has been approved. Once you are granted the ability to generate Keys, generating and distributing the Key allows users to download your app or in-app purchase items by entering the Key into the Redeem Code section in the Meta Quest app. Keys can be useful for giving review copies to the media, for example. You may generate 500 Keys every 6 months, but you should only generate as many Keys as reasonably needed.
After you have obtained Keys for your app, you can distribute Keys yourself or through other websites. You must follow the App Policies on
Promotional Mechanisms when distributing Keys.
To create Keys:
- Go to the Meta Quest Developer Dashboard.
- Select your app.
- In the left-side navigation, click Distribution > Keys. \
If the app has been reviewed by Meta Platforms Technologies and approved for release or Key generation, the Meta Platforms Technologies Keys page appears, with Create and Create Bulk at the top of the page.
- Click Create.
- Provide a Campaign Name to identify this set of keys.
- (Optional) To create a key for an in-app purchase (IAP) item, provide the SKU for the IAP. For instructions on how to define and implement IAP for your app, see In-App Purchase.
- Choose the number of keys to generate, up to 250. Note that if you need to generate more keys, up to 500 in total, you will need to click the Create Bulk button to go to the bulk request page. Bulk requests are reviewed by Meta Platform Technologies. We may occasionally grant more Keys in limited circumstances for free distribution at our discretion. Your key allocation will refresh every six months.
- Click Submit when finished. If you’ve generated 250 keys or fewer, you’ll see a file downloaded from your browser with the name meta_keys_mm_dd_yy.txt.
- Save the key(s) in a safe place as you cannot retrieve them after you exit this page.
Release Channels are another form of limited distribution and useful while your app is in development.
When you upload your app to the Developer Dashboard, you are given the choice of uploading into several “channels”: Production, ALPHA, BETA, and RC. With the exception of the Production channel, you can grant or revoke user-level access to each by adding or removing a test user’s email address (tied to their Meta account ID) to or from specific channels.
Note: Production is a special channel which should be used only when submitting your app for review.
Each Release Channel can have up to 200 users assigned to them. Since distribution through release channels do not require review, it comes in handy for testing or closed beta. That said, all apps hosted in a Release Channel must still comply with our Content Guidelines, Platform Abuse Policy, and App Policies. Developers are also responsible for ensuring their end users abide by the
Code of Conduct for Virtual Experiences. We reserve the right to take down any app that violates our applicable terms.
When your app is ready for distribution to the general public, you copy it to the Production release channel and submit it to us for consideration.
You can distribute your app outside the platform by a method known as
sideloading. To run sideloaded apps, users must enable Unknown Sources in the Settings menu of the Meta Horizon app. For more information, see
Games and Apps From Unknown Sources.
Sideloaded apps are not updated through our platform. They do not appear in anyone’s Quest Home Library or have access to any other Horizon features or services.
Important
Enabling Developer Mode and sideloading is not intended for piracy. For more information, see the Platform Abuse Policy.Note: Off-platform builds must still meet our SDK license requirements. In particular, all reserved functions called out in the SDK license, such as home button functionality and menu operation, must be respected.