Look around the Vision Pro settings list on an ordinary screen
Most settings menus assume a screen you touch and a body that stays still. A headset has to account for where your eyes land, which hand you point with, whether anyone else is in the room and what the room itself looks like. That produces categories with no equivalent anywhere else, and reading them cold is the fastest way to understand what this device actually does.
At a glance
Loading visionOS gives you a headset with the Settings app in front of you. The ordering, the grouping and the nesting are the system's own, not a simplified summary of it. The counts below come from the tree itself, so they move only when the tree does.
- 21top-level entries
- 678rows in total
- 6levels deep
- 2versions
| Device family | Headsets |
|---|---|
| Frame shown | Headset |
| Versions | 1.2, 1.0 |
| Deepest path | 6 levels below the main list |
| Interface languages | 12, switchable while you browse |
| Account needed | No — it runs entirely in your browser |
How visionOS organises Settings
Two entries give the game away immediately. Eyes & Hands collects Re-run Eye Setup, Hand Tracking, Dominant Hand, Pointer Control and Dwell Control, which means the pointing device is your body and it needs calibrating like any other instrument. People holds Persona, EyeSight and Spatial Personas, so how you appear to other humans is treated as a setting rather than an app feature. Around those sit familiar names, Wi-Fi, Bluetooth, Battery, General, Accessibility and Privacy & Security, borrowed wholesale from the phone. The list is a hybrid: half of it is ordinary housekeeping, half of it exists because the device sits on your face.
Twenty-one entries at six levels deep is restrained by Apple standards, and the restraint is deliberate. General still does the heavy lifting, folding About, Software Update, Storage, Language & Region, Date & Time, Keyboard, AirDrop and Reset into one branch so the outer list stays short enough to read while wearing the thing. Where people hesitate is the boundary between Environments, Displays & Brightness and Control Center, since all three affect what you see. Travel Mode and Guest User look like edge cases until you need them, and both are top-level precisely because you reach for them in a hurry.
Three settings worth finding
Settings > Eyes & Hands > Dwell ControlDwell Control lets you select something by resting your gaze on it instead of pinching your fingers. For anyone whose hands tire quickly, or who wants to operate the headset one-handed, this single switch changes how the whole device is driven, and it is not obvious from the outside.
Settings > People > EyeSightEyeSight governs whether the outward-facing display shows a representation of your eyes to people nearby. It is a social setting rather than a technical one, and it sits in a category most operating systems do not have at all, which makes it worth finding deliberately.
Settings > General > StorageStorage shows how space is divided between apps and captured material. Treat the figures here as sample values rather than a reading from a real headset, but the page is useful for seeing how the system categorises what it keeps and where you would go to clear room.
Versions of visionOS you can open
There are 2 builds of visionOS to choose from, which is enough to watch the menu drift over time rather than guess at it.
How this menu got here
This is a young interface with an old spine. It inherits the arrangement of the iPad settings list, then bolts on the categories a spatial computer needs, which is why Wi-Fi, Bluetooth and General look so familiar next to Eyes & Hands and Environments. The two versions here, 1.2 and 1.0, cover the first year of refinement rather than any dramatic reshuffle: entries were tuned and options added under existing branches. Because the system is not open source, the structure shown is reconstructed from the shipping interface.
Who this is useful for
People weighing up an expensive headset before ever trying one get a straight look at what it asks them to configure. Developers planning a spatial app can check which controls the system already owns, so they do not duplicate them. Accessibility specialists benefit most: Eyes & Hands and Accessibility together describe how someone with limited hand movement would actually operate the device, and that is hard to establish from a marketing page.
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 > Eyes & Hands > Dwell Control 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. The simulator fills those in with obvious sample values. Use them to learn where a figure lives; look at your own headset to learn what it says.
Try it yourself
Start at the top of visionOS and open every row once. It takes a few minutes and it is the fastest way to stop guessing which section a given option lives under. When the question is really visionOS 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 visionOS in the simulatorFree, no account, works offline — 678 settings rows across 2 versions.Key points
- visionOS shows 21 top-level entries and 678 rows in total, nested up to 6 levels.
- Menu names and their order come from the settings tree itself, so the paths quoted here match the real headset.
- Anything that belongs to a specific device — names, addresses, build numbers, switch positions — is a marked sample.
Questions about visionOS settings
Do I need a Vision Pro to use this?
No, and that is rather the point. The simulator runs in an ordinary browser on whatever computer or phone you already have, drawing the menus inside a headset-shaped frame. Nothing connects to hardware, and any device name or network name you see is a clearly marked sample rather than real data.
What is the difference between visionOS 1.2 and 1.0?
Both are available in the simulator and you can switch between them on the same screen. The changes across that span were mostly additions and refinements under existing categories rather than a rearranged top level, so the comparison is useful for spotting an option that appeared partway through rather than a menu that moved.
Are the eye and hand settings really that important?
They are how you point and select, so yes. On a phone the equivalent would be the touchscreen driver, which nobody configures. Here calibration, dominant hand and pointer behaviour are all exposed as settings, and walking that branch explains more about using the device than any specification list does.