Publishing on the Meta Quest Store: The General Path

You do not need a publisher to put a VR game on the Meta Quest store. An independent developer can create an account, build a store page, meet the platform requirements and submit the app. Most of the work is organization: getting the build right, writing a store page that explains the game and planning for review and updates. This guide covers the general path and ends with a real example from the store.

What do you need before you submit?

Start with the basics that every submission depends on:

• A developer account on Meta's developer platform, with the identity and account details the platform asks for.
• A build that runs cleanly on every headset you plan to list.
• Store page assets: an app icon, screenshots, a trailer if you have one and a clear description.
• Content and age rating answers that match what is actually in the game.

Missing one of these is the most common reason a submission stalls. Gather them all before you open the submission form, not in the middle of it.

How does the store page work?

The store page is the sales pitch and the first test. Players see the icon, a few screenshots and the opening lines of the description, and they decide in seconds whether to keep reading. Spend your effort on the parts they see first.

Store page element	What it needs	Common mistake
Title and icon	A clear name and an icon that reads at small size	Icon text too small to read
Screenshots	The real headset view and the core loop	Menus and loading screens
Description	What the game is, who it is for and what is included	Vague slogans with no detail
Comfort and controls	Which movement and input options exist	Leaving them out

Show real gameplay, not concept art. VR players want to know what their hands will be doing, so put controls and comfort options near the top of the description.

What do quality checks look for?

Quality checks focus on whether the app works for a real player. Expect checks on stability, performance, controls, comfort and content rules. Read the current quality guidelines before you start building, not after. Fixing a comfort problem in the final week costs far more than designing around it from the start.

A short pre-submission checklist helps:

1. Play from a cold start on each target headset.
2. Test pause, quit and resume during the first session.
3. Check that every menu works with the controllers alone.
4. Make sure the content matches the rating answers you gave.
5. Read your store text out loud and cut anything that is not true.

Publisher or self-publishing?

Self-publishing gives you full control over the release, the store page and the timing. You also take on the work a publisher might handle, such as marketing, support and platform communication. A publisher can carry some of that load, but you give up part of the revenue and some decision making. Our guide to self-publishing and using a publisher walks through that trade-off in more detail.

A publisher often handles marketing, localization, platform relationships and sometimes outside quality testing. Some also help with paid promotion and community support. You still supply the game, the build and the answers to store questions, since no publisher can make the product for you.

The choice is not permanent. Many developers self-publish a first game and work with a partner later. Pick the path that matches your budget and how much of the process you want to own.

Should you release in early access?

Early access can help you test the store page, the price and the first reactions before a full launch. It can also make players expect fixes and changes, so be clear about what is finished and what is not. Our early access pros and cons guide covers when it helps and when it hurts.

How does a real release look?

Dixotomia is a useful public example. It is a single-player sci-fi horror shooter made only for VR, and Deep Matrix released it on Steam and on the Meta Quest store. The game left early access on Meta Quest on 9 January 2026 and was released on 22 January 2026. To see how a store page presents a VR shooter, read the Steam store page. For price and store details, the release date, price and store guide is the simplest place to start.

What happens between a finished build and launch day?

Plan the steps before you need them. Run internal testing with people who have not played the game. Finish the store page and check every line for accuracy. Prepare the update plan, the support contact and a launch-day checklist. Then submit, respond quickly to any feedback and schedule the release for a day you can monitor.

What if your submission is rejected?

Rejections are common, especially for first releases. Read the reasons carefully, fix the issue in the build or on the store page and resubmit with a short note about what changed. Keep a record of each round, so the next submission goes faster.

Get the basics right: the account, the build, the store page and the ratings. Then plan review and updates as part of the launch, because they are part of it. The general path is not glamorous, but it becomes predictable once you have done it once.