See how a watch fits seventeen menus on a small screen
A watch screen cannot hold much, so Google's wearable platform splits its settings into seventeen short lists rather than one long scroll. Roughly 218 rows sit across four levels of depth, and most decisions are a single toggle. Reading that structure on a desktop, where you can see several levels at once, is far easier than thumbing it on a circular display.
At a glance
Wear OS runs here as a working watch. You navigate it the way you would the physical thing: tap a row, land on its screen, go back, take a different branch. The figures below are counted from the menu tree the site ships, not estimated.
- 17top-level entries
- 218rows in total
- 4levels deep
- 2versions
| Device family | Watches |
|---|---|
| Frame shown | Watch |
| Versions | 4, 3 |
| 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 Wear OS organises Settings
Everything here is shaped by the size of the panel. Connectivity gathers Bluetooth, Wi-Fi, Mobile, NFC, Airplane mode and Cast into one row so the top list stays short. Display and Gestures are separate even though both govern when the screen lights up, because Tilt-to-wake and Touch-to-wake are things you do with your arm rather than things you set. Apps & notifications, Sound & vibration, Battery, Google, Accessibility and System fill out the rest. There are seventeen entries in total, and none of them expects more than a few flicks of a finger to reach the end.
Four levels is shallow by phone standards, and that is deliberate: a watch cannot afford a menu you get lost in. The cost is duplication. Notifications appears as its own top-level row and again inside Apps & notifications as App notifications, and wake behaviour turns up under both Display and Gestures. Newcomers usually hunt for Do Not Disturb at the top level and find it filed under Apps & notifications instead. Compared with the phone Settings app it mirrors, this is the same vocabulary with two-thirds of the branches pruned away.
Three settings worth finding
Settings > Display > Always-on screenKeeping the face dimly lit costs battery but saves you the flick of the wrist every time you want the time. It is the one setting that changes how the watch feels more than any other, and it sits near the top of Display.
Settings > Gestures > Wrist gesturesFlicking your wrist to scroll a list is the closest a watch gets to one-handed use, which matters when the other hand is holding a dog lead or a coffee. Many owners never learn it exists because Gestures is a short row easily scrolled past.
Settings > Apps & notifications > Bedtime modeThis silences the watch and dims the screen overnight so a sleep-tracking band does not light up the bedroom at three in the morning. Filing it beside app notifications rather than under Display is the reason people go looking in the wrong place.
Versions of Wear OS you can open
You can load 2 builds of Wear OS. That matters when you are writing instructions for someone whose device is a release or two behind yours.
How this menu got here
Early smartwatch software borrowed phone menus wholesale and they did not fit. Successive releases cut items, merged related rows and moved most per-app control to the paired phone, leaving the watch with the switches you actually need on your wrist. The simulator offers versions 4 and 3, which sit either side of that consolidation and show how much was folded into fewer rows. The wearable layer is not open source, so what you navigate here is reconstructed from the shipping interface rather than lifted from code.
Who this is useful for
Someone shopping for a first smartwatch can judge how much fiddling it will demand before spending the money. Retail staff can demonstrate a feature without pairing a display unit. Accessibility advisers can check what the platform offers without borrowing a device from a client. And if you have already got one on your wrist, finding a row on a big screen first saves a lot of squinting.
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 > Display > Always-on screen and expect it to match your watch.
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 watch, 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 watch to learn what it says.
Try it yourself
Give yourself a task — change a language, find a privacy switch, locate a build number — and do it in Wear OS here first. The step recorder will keep the route for you. If you are weighing one system against another, put Wear OS beside a second one and compare the same screen on both. The search will also work backwards: give it a setting name and it reports where every system files it.
Open Wear OS in the simulatorFree, no account, works offline — 218 settings rows across 2 versions.Key points
- Wear OS shows 17 top-level entries and 218 rows in total, nested up to 4 levels.
- The labels and their ordering are the system's own, not a tidied-up approximation.
- Anything that belongs to a specific device — names, addresses, build numbers, switch positions — is a marked sample.
Questions about Wear OS settings
Does the simulator show my watch's battery level?
No. Battery percentage, paired device names and network names belong to a physical watch, not to a menu structure, so they appear as clearly marked sample values. What is accurate is the shape of the tree: which rows exist, what order they sit in, and how many taps separate the top of the list from the switch you want.
Why are there two versions to choose from?
Wear OS 4 and 3 lay their menus out slightly differently, and switching between them in the simulator makes the differences visible without owning both. That helps when a guide written for one release sends you to a row that has since moved, or when you are deciding whether an update is worth the effort.
Can I record the steps to send to someone else?
Yes. A step recorder captures the click-path you take through the menus so it can be replayed or handed to another person. That is quicker than writing out four taps in a message, and the recipient sees the same rows in the same order rather than guessing at your description.