Check the headset settings before you put the Quest on
Headset settings are unusual because you configure the room as well as the device. Meta's headset platform gives ten top-level rows, and one of them is about the physical space around you rather than the hardware. Reading that list flat on a monitor, without a headset on your face, is the easiest way to understand what the machine is actually asking you to set up.
At a glance
Pick Meta Quest and a headset appears with its Settings already open. Nothing is a screenshot — every row is a live element you can tap into, and the tree underneath it is the real one. The counts below come from the tree itself, so they move only when the tree does.
- 10top-level entries
- 194rows in total
- 4levels deep
- 2versions
| Device family | Headsets |
|---|---|
| Frame shown | Headset |
| Versions | v74, v72 |
| Deepest path | 4 levels below the main list |
| Interface languages | 12, switchable while you browse |
| Account needed | No — it runs entirely in your browser |
How Meta Quest organises Settings
The list opens like a phone, with Wi-Fi, Bluetooth, Device, Display and Sound, and then turns into something no phone has. Boundary and Movement Tracking are top-level rows because a headset has to know where the walls are and where your hands are before anything else works. Apps, Accounts and System finish the list. Roughly 194 rows sit under those ten headings, so each one carries more than its short name suggests, and Device in particular collects Power, Controllers, Storage, Passthrough and Auto Wake into a single screen.
Four levels of depth is shallow, which suits an interface you operate by pointing at floating panels rather than scrolling with a thumb. The risk is different from a phone's: not that you get lost, but that you skip a row you needed. Boundary is the clearest example, holding Boundary Sensitivity, Passthrough on Boundary, Set Up Boundary and Space Sense, safety features that only make sense once you have stood in the room. Compared with a tablet's settings, the vocabulary is half familiar and half entirely new.
Three settings worth finding
Settings > Boundary > Space SenseThis lets you see outlines of real objects and people through the virtual view, so a pet or a family member walking into the room does not become a collision. It is the setting most worth turning on before handing a headset to someone who has never worn one.
Settings > Device > PassthroughSwitching the outward cameras on lets you see the room without removing the headset, which is how you find a drink, a keyboard or the door. It sits under Device rather than Display, and that placement catches out people who assume it is a screen setting.
Settings > Display > Refresh RateA higher rate makes motion steadier and can reduce the queasy feeling some people get, at the cost of battery. Since comfort in a headset matters more than it does on a phone, this is worth changing early rather than after a bad first session.
Versions of Meta Quest you can open
2 builds of Meta Quest are here. Open two of them and the differences stop being release-note bullet points and become screens you can point at.
How this menu got here
Standalone headsets arrived without an established convention for their settings, so early menus were short and grew as capabilities appeared. Passthrough, room-scale boundaries and hand tracking each added rows, and the platform was eventually given a name of its own to reflect that it had outgrown being an app launcher. The simulator carries v74 and v72, two consecutive software releases; comparing them shows how quickly rows appear on a platform still changing shape. The layout is reconstructed from the shipping interface rather than from source.
Who this is useful for
Someone considering a headset who wants to know what setup involves before spending. Teachers and museum staff who lend headsets to visitors and need a repeatable safety routine. Parents checking what account and app controls exist. It is also useful if you own one already but only ever wear it to play, and have never seen the rows that sit behind the first screen.
What is real and what is sample data
The structure is the real thing: menu names, their order, how they are grouped and what sits inside each one. That is why this article can quote a path such as Settings > Boundary > Space Sense and expect it to match your headset.
The state cannot be. A device name, an address, a build number, a network name, a storage figure, whether a particular switch is on or off — those belong to a physical headset, not to a menu tree. Everywhere the simulator shows a value like that it is clearly-marked sample data: a placeholder that tells you where the number appears, not what any real device would say.
Try it yourself
Open Meta Quest and walk the tree. If you are writing instructions for someone else, turn the step recorder on first: it captures the exact click-path you take, so you can replay or hand over the path instead of typing out tap this, then tap that. When the question is really Meta Quest versus something else, open them side by side rather than reading two separate menus from memory. And if you know the setting but not the section, search for it by name across all 43 systems at once.
Open Meta Quest in the simulatorFree, no account, works offline — 194 settings rows across 2 versions.Key points
- Meta Quest shows 10 top-level entries and 194 rows in total, nested up to 4 levels.
- Nothing in the menu listing above was retyped by hand, which is why a path from this page can be followed on a real headset.
- Device-specific figures on screen are placeholders; the structure around them is not.
Questions about Meta Quest settings
Do I need a headset to use the simulator?
No. It runs in a browser tab and draws a headset-style frame around the menus, so you can read the whole structure on a monitor. Nothing connects to real hardware, and figures like storage or a paired controller name are clearly marked sample values rather than readings taken from a device.
Is this made by Meta?
No, and it is not endorsed by or affiliated with Meta or any other vendor. It is an independent reconstruction of the menu layout, made so people can learn the structure, compare two software versions, and write instructions that match what someone sees when they put the headset on.
Why does the boundary section matter so much?
Because it is the part of the setup that keeps you from walking into furniture. A headset covers your eyes, so the software has to be told where the safe area ends and what to show you when you reach it. Reading those rows before a first session is quicker than learning them mid-game.