See how a Chromebook sorts its twelve settings groups
Twelve headings and just over six hundred rows is a tight budget for a full desktop system, and the tidiness is deliberate. Where other laptop systems scatter controls across dozens of panels, this one leans on a small set of named groups and a search box. Clicking through the whole thing in a browser takes minutes rather than an afternoon.
At a glance
Pick ChromeOS and a laptop 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.
- 12top-level entries
- 618rows in total
- 5levels deep
- 2versions
| Device family | Computers |
|---|---|
| Frame shown | Laptop |
| Versions | 124, 120 |
| Deepest path | 5 levels below the main list |
| Interface languages | 12, switchable while you browse |
| Account needed | No — it runs entirely in your browser |
How ChromeOS organises Settings
The organising idea is grouping by question rather than by component. Network, Bluetooth and Connected devices answer what am I talking to. Accounts and Kerberos answer who am I. Device gathers everything physical, from Mouse and Touchpad through Keyboard and inputs to Display, Audio, Print and Scan. Wallpaper and style, Privacy and security, Apps and Accessibility each own a clear domain, and System preferences catches the leftovers before About ChromeOS closes the list. Nothing sits at the top level unless it names a category, which is why twelve entries can cover so much ground.
Five levels is shallow for a desktop system, and that shallowness is the trade. You reach almost anything in three clicks, but the middle screens get crowded, and Device in particular is a long scroll rather than a menu. Compared with a traditional laptop control panel, where each device class gets its own icon, this collapses them into one page and relies on headings to break it up. Newcomers most often stall on Connected devices, which sounds like Bluetooth but actually handles phone pairing and Nearby Share, and on System preferences, whose name promises more than it holds.
Three settings worth finding
Settings > Device > TouchpadScroll direction, tap-to-click and sensitivity all live here, and they are the first things people change on a borrowed machine. Knowing the row sits under Device rather than under a pointing-device panel saves a genuinely annoying hunt.
Settings > Network > Known NetworksThis is the list the machine reconnects to automatically. When a laptop keeps rejoining a slow guest network instead of the good one, this screen is where you remove the bad entry rather than fighting it at the connection prompt.
Settings > Connected devices > Nearby ShareIt governs who can send you files without pairing and how visible you are while idle. Worth finding because the default visibility setting surprises people in offices and classrooms where many machines sit within range.
Versions of ChromeOS you can open
2 builds of ChromeOS 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
Settings here began as a page inside the browser, which is why it still behaves like a document with sections rather than a stack of separate windows. As the system grew beyond the browser to handle styluses, Android apps, printers and phone pairing, the page was reorganised into named groups instead of gaining new top-level rows. Because the platform is open source, the titles and nesting can be taken from the source itself. The two builds offered here, 124 and 120, are close neighbours and mostly show wording and regrouping changes.
Who this is useful for
School IT staff who manage carts of identical laptops get the most out of this, since they can rehearse a rollout path and screenshot it for a handout without unboxing anything. Support agents can confirm whether a control lives under Device or System preferences before they say it aloud. Anyone moving from a Windows or Mac laptop can see how much smaller the settings surface really is before committing to the switch.
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 > Device > Touchpad and expect it to match your laptop.
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 laptop, 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 ChromeOS 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. If you are weighing one system against another, put ChromeOS beside a second one and compare the same screen on both. If you already know what the setting is called, the site-wide search will tell you which section hides it here.
Open ChromeOS in the simulatorFree, no account, works offline — 618 settings rows across 2 versions.Key points
- ChromeOS shows 12 top-level entries and 618 rows in total, nested up to 5 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 laptop.
- Device-specific figures on screen are placeholders; the structure around them is not.
Questions about ChromeOS settings
Does this match a real Chromebook exactly?
The menu titles, their order and their nesting come from the open source project, so the structure matches. What cannot match is device state: network names, connected accessories and hardware details are sample values chosen to make the screens readable, and the simulator marks them as samples rather than presenting them as yours.
Why are there only twelve top-level entries?
The design groups by purpose instead of by component, so a single Device entry covers pointing devices, keyboard, display, audio and printing. Fewer headings mean longer pages, and the built-in search on real hardware is meant to carry the load when you already know the name of what you want.
Can I use this to write instructions for other people?
Yes. The step recorder captures the exact click path you take through the tree so it can be replayed or shared, which is quicker than writing out each turn by hand. There is also an embeddable widget if you want the tree to sit inside your own help page.