How to run several VR headsets from one tablet
One headset is easy to run by hand, three take effort, ten are impossible. What breaks as your fleet grows, what one control screen has to show, and how to set up the floor around it.
Read →How to manage multiple Meta Quest headsets from one tablet
Meta Quest is built around one person and one phone. The Meta Horizon app pairs with a headset, casts it to your phone and changes its settings — one headset at a time. That is fine at home and painful at a venue with six or ten Quests, where the operator needs to know at a glance which headset is free, which is about to run flat and what each guest is playing. Here is how to set up a Quest fleet so it can be run from a single tablet.
What Meta gives you out of the box
With consumer Quest headsets, your management tools are the headset itself and the Meta Horizon phone app. Between them you can set up a headset, turn on developer mode, cast to the phone and buy apps. What you don't get is a fleet view: there is no screen that shows every headset's status, battery and running game side by side, no remote game launch across the room, and no notion of a paid session.
Meta has offered business programs and managed-device services for companies, but their terms, pricing and availability have changed more than once. If you are considering one, check the current offer directly with Meta — and note that they are designed around training and workplace deployments rather than paying guests.
Step 1: decide how accounts will work
Every Quest needs a Meta account for setup. Before you unbox the fleet, decide which account owns the venue headsets, and keep those credentials with the owner rather than whoever happens to be on shift. Then, on every headset:
- set a purchase PIN, so a guest can't buy anything on the venue's card;
- keep personal accounts, messaging and social apps off venue headsets;
- write down which account each headset is signed into — you'll need it for repairs and resets.
One more rule that surprises new owners: a game bought in the store is licensed for personal use. Showing it to paying guests is commercial use, and each developer sets its own terms for that. Check before a game goes on your menu.
Step 2: prepare every headset the same way
A fleet is manageable when every headset is set up identically. For each Quest:
- Update the system to the current version before anything else.
- Turn on developer mode in the Meta Horizon phone app: Devices → the headset → Headset settings → Developer mode.
- Check for a third-party launcher (LightningLauncher is the usual one) and remove it. It holds its own accessibility service and interferes with the apps you rely on.
- Install your games and venue apps from a computer with SideQuest.
- Set the play boundary and mark the same area on the floor.
- Label the headset and both controllers with the same color or number.
Step 3: put the whole fleet on one screen
This is the part Meta doesn't provide for venues. You need an app on each headset that reports its status and takes commands, plus an operator panel that shows every headset together. The minimum an operator should see without walking over:
| On the panel | Why it matters on a Quest fleet |
|---|---|
| Free / in session / offline | Finding a free headset should take a glance, not a lap of the room |
| Time left | The operator knows which headset frees up next and can queue the next guest |
| Battery and charging | A Quest gives you a couple of hours of play; swap before a session, not during one |
| Storage used | A full headset is a common reason an app or game fails to update |
| Current game | No need to ask the guest or peek at the lenses |
Step 4: launch games remotely
The slowest routine on a Quest floor is putting a headset on to start a game, taking it off and fitting it on the guest. Remote launch removes it: the operator picks a headset and a game on the tablet, the game starts, and the guest puts on a headset that is already running. Switching games mid-session should work the same way, without resetting the paid time.
Step 5: keep guests in the game
The Quest menu button works from any app and can't be switched off in settings. Guest mode protects your account but doesn't hold anyone in a game, and it asks for the boundary to be set again. On a busy floor you want a lock-down that covers the system menu, the store and settings, plus an override code for staff. We cover the options in detail in kiosk mode on Pico 4 and Meta Quest.
Step 6: keep the fleet consistent over time
- Self-updating venue app. Updating ten headsets over USB takes half a day; an app that updates itself over Wi-Fi removes the chore.
- System updates. Quest system updates arrive on Meta's schedule. After one lands, check a headset before the next busy shift.
- Same library per model. Guests should never have to pick a headset based on what is installed on it.
- Mixed Quest 2, 3 and 3S. Workable, but lenses, facial interfaces and performance differ — label the models and keep spares per model.
A reliable network
One tablet can only control the fleet if everything talks over a stable connection. Put the headsets, the tablet and any room TV on the same Wi-Fi network — not a guest network, not a neighbor's with a similar name. A dedicated 5 GHz router in the same room does more for a Quest fleet than any setting.
How UnitVR runs a Quest fleet
UnitVR supports Meta Quest 2, Quest 3 and Quest 3S — and Pico 4 in the same venue. The headset app is installed once with SideQuest and pairs with a six-character code. The operator panel runs in a browser on a tablet, laptop or PC and shows status, time left, battery, storage and the current game for every headset. Games launch with one tap, sessions end on their own, and with no paid session the Quest shows a full-screen "Waiting for a game session" card over the menu. The library is collected from the headsets automatically. See the features or pricing — the free 7-day trial covers up to 20 headsets. For fleet-wide advice that applies to any headset, read how to run several VR headsets from one tablet.
Summary
- Consumer Quest tools manage one headset at a time; a venue needs a fleet view.
- Decide on accounts and purchase PINs before setup, and set every headset up the same way.
- Install venue apps with SideQuest — browser installs on Android 14 can't get Accessibility.
- Remote launch, battery and time left on one screen are what save the operator's time.
- Lock the menu, keep the library identical, and give the fleet its own Wi-Fi.
FAQ
Can the Meta Horizon app manage several Quests at once?
It can hold several headsets on one account, but you work with one headset at a time. There is no shared status view or remote launch across a fleet.
Do I need a PC for each Quest?
No. A computer is needed once per headset to install apps with SideQuest. Day to day the fleet runs from the operator's tablet.
Can I run Quest and Pico headsets together?
Yes, as long as your venue software supports both. The game stores differ, so plan the library per platform.
