How to Enable Developer Mode on Meta Quest (USB/ADB)

To be detected by a PC, a Meta Quest headset must first be switched to Developer Mode, then authorize USB debugging (ADB). This guide covers headsets linked to a personal Meta account (Quest 2, Quest 3, Quest 3S and Quest Pro), step by step: developer account, Meta Horizon app, check in the headset and first USB connection. It also explains what to do on Pico and HTC Vive headsets, and how to fix the most common blocking points.

In short: 1) create a free developer organization on developers.meta.com with your Meta account, 2) turn on Developer Mode in the Meta Horizon mobile app, 3) check Settings > System > Developer in the headset, 4) plug the headset into the PC and choose "Always allow from this computer". You only do this once per headset.

Is your headset managed by an MDM? If your Meta Quest headsets are enrolled in Meta Horizon Managed Services or another MDM, the procedure is different: see How to Enable Developer Mode on Meta Quest Managed by an MDM.

Video: enable Developer Mode and USB debugging

Video: enable Developer Mode and ADB on a Meta Quest headset

Before you start: what you need

The Meta account the headset is linked to.
A smartphone with the Meta Horizon app (formerly Meta Quest app), paired with the headset.
A USB-C cable that carries data (many charging-only cables do not), and the Windows PC where OmnicastVR is or will be installed.

Step 1: Create a Meta developer organization

Meta only unlocks Developer Mode for accounts registered as developers. It is free and takes a few minutes.

Go to developers.meta.com/horizon and sign in with the Meta account linked to the headset.
Create an organization. Any name works (for example "MyCompany-VR").
Verify your account when Meta asks for it, usually by adding a payment method or confirming a phone number by SMS. This step is mandatory: without it, the Developer Mode switch stays unavailable.
Accept the developer terms if they are displayed.

Step 2: Turn on Developer Mode in the Meta Horizon app

Switch on the headset and open the Meta Horizon app on your phone. Check that the headset shows as connected.
Open the Devices menu (or Headset settings) and select your headset.
Tap Developer Mode (sometimes under Advanced settings) and turn the switch on.
Restart the headset so the change is applied.

Put on the headset and go to Settings > System > Developer. If this menu is there, Developer Mode is active. Check that USB debugging is turned on and that the MTP notification option is visible.

Step 4: First USB connection to the OmnicastVR PC

This one-time step links the headset to your PC. After that, it is recognized automatically at every session.

Plug the headset into the PC with the data USB-C cable.
Put on the headset: a window asks you to Allow USB debugging.
Tick "Always allow from this computer", then press "Allow".

The headset is now visible to OmnicastVR. For the first stream, follow our ADB connection and first stream tutorial.

Pico and HTC Vive headsets

On Pico and HTC Vive headsets, there is no developer account or mobile app to use: everything happens in the headset.

Open the system settings and go to the About section (device or software information).
Tap the build number (or software version) 7 times in a row: a Developer menu appears.
In this menu, turn on USB debugging.
Plug the headset into the PC and allow debugging, as in step 4.

OmnicastVR controls mixed fleets: see how to manage Meta Quest, Pico and HTC headsets from one interface.

Troubleshooting: Developer Mode or USB debugging won't appear

No Developer Mode option in the Meta Horizon app: the developer organization is missing or the account is not verified yet (step 1). Also check that you are signed in with the Meta account linked to the headset.
The app says Developer Mode is only available to device owners: you are not signed in with the owner account, or the headset is managed by your organization. In that case, follow the MDM guide.
No "Developer" menu in the headset: restart the headset after turning on Developer Mode in the app, then check again.
The "Allow USB debugging" window does not show up: use a USB-C cable that carries data, put the headset on before plugging it in, then unplug and plug it back in. Restarting OmnicastVR also brings the prompt back.
The window was dismissed by mistake: unplug the cable, check in Settings > System > Developer that USB debugging is still on, then plug the headset back in and tick "Always allow".
The headset is still not detected: see our VR headset streaming troubleshooting guide.

Next steps with OmnicastVR

Once Developer Mode is on, OmnicastVR lets the trainer see every headset screen, launch apps on all headsets at once and switch them off with one click, over a local Wi-Fi network. Nothing to install on the headsets.

Frequently Asked Questions

Is the Meta developer account free?

Yes. Creating a developer organization on developers.meta.com is free. Meta only asks you to verify your account, usually by adding a payment method or confirming a phone number by SMS. Nothing is charged.

Can I enable Developer Mode without a phone?

The standard method uses the Meta Horizon mobile app. Meta also offers Meta Quest Developer Hub, a PC and Mac app that can manage a connected headset, but some users report that it fails to enable Developer Mode. The most reliable option is to borrow a phone once: you only need to turn on Developer Mode one time per headset.

Do I have to allow USB debugging again before every session?

No. If you tick "Always allow from this computer" during the first connection, the headset remembers your PC and is recognized automatically in later sessions. You only need to authorize it again with a different computer or after a factory reset.

Which headsets does this guide cover?

The Meta Quest steps apply to Quest 2, Quest 3, Quest 3S and Quest Pro linked to a personal Meta account. Pico and HTC Vive headsets use the build number method described above. For Meta Quest headsets managed by an MDM, see our dedicated MDM guide.

How to Enable Developer Mode on Meta Quest via USB (No MDM)