A Chromebook scroll bar that vanishes between movements is usually hiding automatically. Enable Always show scrollbars under Settings > Accessibility > Display and magnification. A single app or website can need a separate check.
Start by sliding two fingers vertically across the touchpad. A page that moves needs help with the bar's visibility. The steps also cover a page that won't move and a touchpad that isn't responding.
In this guide
1. Turn on Always show scrollbars
Click the shelf's clock to open the status menu, then select Settings. Choose Accessibility > Display and magnification. Find Always show scrollbars and turn it on.
If the layout has changed, search Settings for scrollbars. Choose the ChromeOS control instead of Chrome's browser appearance settings. The operating system and browser have separate settings areas.

Return to a long webpage and move through it. Check the page's right edge while you're scrolling and after you stop. A short page that fits the window doesn't need a vertical scroll bar, so it won't show you whether this setting worked.
The current ChromeOS settings code includes this switch in the display-and-magnification page. Google's accessibility settings instructions explain how to reach the system's Accessibility controls.
This setting is useful when the disappearing bar is the problem. It doesn't add missing content to a page, repair a mouse, or force every app to use ChromeOS's own scroll-bar design.
If the bar stays visible and the page moves as expected, keep the setting enabled. If one page still has no usable bar, try the window and page checks next rather than changing unrelated accessibility features.
2. Check the window and the part that should scroll
Move the whole window onto the screen, then use its maximize button. Close a temporary menu or dialog, then reload the page. A cropped window edge and a hidden scroll bar can look similar.
Move the pointer over the content you want to scroll before using two fingers. A website can have a scrolling side panel inside a separate scrolling page. Moving over the wrong area can leave the panel unchanged while the outer page moves.
Click once inside the main page's content, away from a text box. Press Space to move through the page and Shift+Space to move back. If those work, the page can scroll even though the bar is difficult to see.
Make sure the cursor isn't in a text box when you try this. Space enters a space in an editor instead of moving the page. That behavior doesn't mean the browser or keyboard is broken.
If the whole interface looks unusually enlarged, check the Chromebook zoom controls. Page zoom and the system magnifier change different things, so undo the control that actually enlarged the screen.
I'd compare another long page before changing more settings. When one page fails and another works in the same window, that comparison points you toward that site instead of a Chromebook reset.
3. Update when the setting is absent or won't stick
Open Settings > About ChromeOS > Check for updates. Let an available update finish and choose Restart when offered. Save your work first, since the restart closes the current session.
After restarting, search Settings for scrollbars again and check the switch. The old Overlay Scrollbars experiment belonged to Chrome's flags page. Experimental flags can disappear, so don't depend on that old route.
If the search finds nothing, don't start changing unrelated flags. Note your version from About ChromeOS. Give it to your administrator or device maker when asking why that build lacks the switch.
A school or employer may manage your Chromebook's settings and updates. Ask its administrator about release availability and accessibility restrictions. Resetting a managed machine isn't a way around its policy.
Reopen the same page after the update. If the switch remains enabled but only that site fails, move to the site comparison. If system windows also lose their scrolling controls, include that distinction in a ChromeOS report.
4. Compare Guest mode for a browser-only problem
Save your work, then sign out of ChromeOS. At the sign-in screen, choose Browse as Guest if that option is available. Open the public page that fails and try moving through the same part of it.
Guest browsing doesn't use your usual account's settings or extensions. If the page works there, return to your own account and check extensions or settings that affect webpage appearance and scrolling.
A page that requires a sign-in may be harder to compare this way. Start with a public page showing the same problem when possible. On a managed Chromebook, the Guest option may be unavailable.
Back in your account, choose Extensions > Manage Extensions from Chrome's menu. Switch off a page-style, accessibility, or scrolling extension, then reload the affected tab. Check each extension separately to see which change helps.

Keep a troublesome extension switched off and send its developer the failing page address. If that page also fails in Guest while others work, report it to the website and identify the panel that won't move.
5. Handle a page that won't move by any method
Slide two fingers up or down together across the touchpad. Try the same gesture in another long page. If it fails everywhere, compare the keyboard scrolling check or an external mouse when available.
If an external mouse scrolls but the touchpad doesn't, use the Chromebook input-device checks. That narrows the work to the touchpad or its settings instead of treating every missing bar as a display problem.
If neither input method moves one tab, reload that tab and reopen the page. When several apps stop responding, save what you can and restart the Chromebook. Recheck a normal page after signing back in.
If scrolling still fails across the system, send feedback with Alt+Shift+I. Include your ChromeOS version, scrollbar-switch state, and Guest result. Ask a managed-device administrator to compare the behavior on that release.
The Short Version
Enable persistent scrollbars in ChromeOS Accessibility settings. Compare a long page and update when needed. A failure limited to one website calls for site or extension checks; widespread scrolling failure needs an input-device check.
Checked November 15, 2026.







