Why Is My Chromebook Screen Glitching? How to Fix Flickering

You’re in the middle of something (a dozen tabs open, a video call, a doc you haven’t saved) and the screen starts flickering or breaking into strange lines. It’s unsettling, but a glitching Chromebook screen is rarely a sign your machine is dying. Most cases trace back to a stuck tab, a misbehaving extension, or a display connection issue, and Google’s own troubleshooting guidance walks through the same short list of software checks before anything drastic.

This guide covers what actually causes glitching and flickering on a Chromebook, in the order to try fixes, from a simple restart up to Powerwash and Recovery. It also covers the one thing none of those official steps protect: the tabs you had open when the screen started acting up.

Why Is My Chromebook Screen Glitching or Flickering?

Screen glitching on a Chromebook is almost always software, not hardware — a frozen tab, a bad extension, or a driver hiccup after an update, rather than a failing display panel. Google doesn’t publish a page specifically titled “screen flickering” for Chromebooks; instead, every display or system glitch routes through its general Fix hardware and system problems guide, and its universal instruction is to test the Chromebook after each step to see if the problem is fixed.

That single instruction matters more than it sounds. Skipping straight to a factory reset without testing in between means you can’t tell what worked, and you risk erasing local files for a fix a simple restart would have solved. Work through the causes below roughly in order of how common they are.

If your screen isn’t flickering so much as completely dark, that’s a separate problem with its own set of fixes, and the black screen guide above covers it in detail.

What Should I Try First When the Screen Starts Glitching?

Restart the Chromebook. It’s the first official step for nearly every display or system problem, and it costs you nothing but a minute or two.

A restart clears the temporary memory state that causes most glitching — a graphics process that hung, a browser tab stuck mid-render, a driver that got confused during an update. It doesn’t erase files, settings, or your Google Account data, which is exactly why Google lists it before anything else.

Test after each step, not just at the end. If the glitching stops after the restart alone, you’re done. There’s no need to touch extensions, Diagnostics, or anything more invasive. If it comes back, move to the next section, which narrows down whether a specific app or tab is the culprit rather than the whole system.

How Do I Fix Glitching Caused by a Frozen App or Browser Tab?

Open Task Manager with Shift+Esc and end the specific app or tab that’s frozen or eating memory. This is Google’s documented fix for an unresponsive tab or app, and it’s far less disruptive than restarting the whole device.

Task Manager on a Chromebook lists every open tab and app along with how much memory and CPU each one is using. A tab that’s glitching the whole screen is often the one pegged at the top of that list. Select it and click End process — the rest of your browser keeps running normally.

If the problem is contained to a single page rather than the whole browser, a hard refresh is gentler than closing the tab outright, since it keeps your place in the browsing session while forcing the page to reload from scratch instead of from a broken cached state. Press Ctrl+Shift+R on that tab first before deciding to close it.

It’s worth distinguishing a genuinely frozen tab from one that’s just slow. A frozen tab won’t respond to scrolling, clicking, or typing at all. A slow tab responds, just sluggishly. That’s more likely a memory issue across many open tabs, which is a different problem covered in our guide on why a Chromebook feels slow. Don’t reach for Task Manager if the tab is simply loading a heavy page; give it a few more seconds first.

If ending the process fixes the glitching immediately and it doesn’t come back after normal use, you’ve found your cause. If it returns within minutes on a different tab, the next likely suspect is something running in the background — an extension.

Could an Extension or Recently Installed App Be Causing It?

Yes — a poorly coded or conflicting extension is one of the more common software causes of Chrome rendering glitches on a Chromebook. Google’s own troubleshooting path for freezing and system problems explicitly includes checking recently installed apps and extensions, right alongside restarting and closing windows.

Open Chrome menu > More tools > Extensions and look at anything installed or updated around the time the glitching started. Disable it, not just close it, and test. An extension that injects content into every page you visit (an ad blocker, a screenshot tool, a productivity add-on) has the most opportunity to interfere with how a page renders.

• Extensions. The most common software culprit. Disable anything recently installed or updated, one at a time, and test after each.
• Android apps. These run in a separate layer and can occasionally conflict with display rendering. Uninstall a recently added app to test.
• Linux apps. The Linux development environment has no hardware acceleration, so a Linux app pushing graphics can behave oddly. Isolate it before blaming ChromeOS itself.

If you manage several extensions and don’t remember what changed recently, our guide to Chromebook extensions covers how to review, disable, and remove them cleanly. Work through them one at a time rather than disabling everything at once. You want to know which specific extension was responsible, not just that “an extension” was the problem, so you can decide whether to keep it, update it, or drop it for good.

Is It a Hardware Problem? How Do I Run Diagnostics?

Run the built-in Diagnostics tool to rule hardware in or out. Open the launcher and type “Diagnostics,” or go to Settings > About ChromeOS > Diagnostics. It checks battery health, CPU usage, memory, and network connectivity in one place.

Diagnostics won’t specifically test the display panel itself, but it’s still useful here. A memory problem can manifest as visual glitching just as easily as slowdown, especially under heavy tab load, and a CPU running abnormally hot or maxed out can cause similar symptoms. If Diagnostics flags memory or CPU issues that correlate with when the glitching happens, that’s a stronger lead than guessing.

Diagnostics needs a recent ChromeOS version. The Diagnostics tool requires ChromeOS version 90 or later. If your Chromebook is old enough that it’s missing from Settings, check Settings > About ChromeOS > Check for updates first — an outdated build can itself cause display glitches that a current version has already fixed.

If Diagnostics comes back clean across battery, CPU, memory, and connectivity, that’s good news. It means the problem is more likely fixable through software steps rather than a failing screen or motherboard. If a specific test consistently fails, especially memory, that’s worth noting before you consider a repair or replacement, since it changes what a technician needs to look at.

Diagnostics is also a fast way to rule things in or out before you commit to something disruptive like a hard reset. It takes a couple of minutes and changes nothing on the device, so there’s no downside to running it early in the process rather than after you’ve already tried more invasive fixes.

What if the Screen Glitches Only With an External Monitor?

Check the physical connection first — a Chromebook can connect to a monitor or TV via HDMI, DisplayPort, DVI, VGA, or USB-C, and a bad cable is a more common cause of external-display glitching than anything wrong with the Chromebook itself.

Over USB-C specifically, the cable itself has to be fast enough to carry video signal. An unresponsive external monitor or a “Cable may not support displays” message points squarely at the cable, not the Chromebook or the monitor. Swapping to a known-good USB-C cable is worth trying before anything else in this scenario.

If the cable checks out, look at Settings > Device > Displays. From there you can adjust resolution, refresh rate, and orientation on the external display, and confirm “Mirror Built-in Display” is set the way you expect once the monitor is detected. A mismatched refresh rate between the Chromebook’s panel and the external monitor is a common source of flickering that looks like a hardware fault but is really just a settings conflict.

You can also move a window between the built-in screen and the external display quickly with Search + Alt + M (Launcher + Alt + M on newer keyboards) to test whether the glitch follows the window or stays tied to one screen. If it only ever shows up on the external monitor and never on the built-in panel, you’ve confirmed it’s the connection or the monitor, not the Chromebook’s own display. If it happens on the built-in screen too, treat it as a general glitching issue and work through the earlier sections instead.

When Should I Try a Hard Reset?

Try a hard reset only after restarting, checking extensions, and running Diagnostics haven’t fixed the glitching. Google is explicit that a hard reset is a last-resort hardware-level fix, not a first step, and it’s meant for exactly the kind of stubborn display or system problem that a normal restart doesn’t clear.

To do it: hold Refresh and tap Power, then release Refresh once the Chromebook starts up. On a tablet or detachable device, hold Back, Refresh, and Power together for at least 10 seconds. It doesn’t erase any files. It’s closer to pulling the battery on an old laptop than to a factory reset, forcing every running process to stop and restart cleanly.

Because a hard reset stops everything at once, any browser session state that a normal restart might have carried over (open tabs under “Continue where you left off,” for instance) is more likely to be lost. That’s true of a normal restart too if it goes wrong mid-shutdown, but it’s a real risk worth planning for before you force a hard reset.

Should I Powerwash My Chromebook to Fix Glitching?

Powerwash can fix glitching if the cause is a local setting, extension, or corrupted profile that survives a hard reset, but it’s a bigger step than most people need. It’s a full factory reset — worth understanding exactly what it does and doesn’t touch before you trigger it.

Powerwash erases your Downloads folder, installed apps, and local settings. It does not delete Google Drive files or anything on external or USB storage, and your Google Account data (including bookmarks synced to your account) isn’t stored on the device in the first place, so it survives. To run it: from the sign-in screen, hold Ctrl+Alt+Shift+R, select Restart, then choose Powerwash > Continue.

If your Chromebook is managed by a work or school organization, an administrator may have disabled Powerwash entirely, in which case you’ll need to contact IT or your school’s admin instead of running it yourself. On an unmanaged, personal Chromebook, Powerwash is available anytime, but treat it as the step after a hard reset and an extension check, not before.

Because Powerwash erases your local Downloads folder and any locally installed apps, it’s worth moving anything important out of Downloads and into Google Drive before you start, exactly as Google recommends for protecting files from routine storage cleanup too. The same caution applies to your browser tabs. They’re not stored in Downloads, but a Powerwash still closes every window, and nothing in ChromeOS itself remembers what you had open across that kind of reset.

What if Nothing Fixes the Glitching — Recovery or Repair?

If glitching continues after a restart, hard reset, extension check, Diagnostics, and a Powerwash, the cause is more likely hardware, and Recovery or a manufacturer repair is the realistic next step. Recovery is more destructive than Powerwash. It reinstalls ChromeOS entirely and permanently erases everything on the hard drive, including downloaded files.

The Chromebook Recovery Utility installs as a Chrome extension from the Chrome Web Store and builds recovery media on a USB drive. You open the extension, click Get Started, pick your Chromebook’s manufacturer and model, insert a USB drive, select it, and click Create now. To boot into recovery mode on the device itself, hold Esc + Refresh, then press and release Power — some models use Esc + Maximize + Power instead. Our Chromebook Recovery Tool guide walks through what it does to your files in more depth if you’re at this point.

If Diagnostics consistently flags a specific hardware component (memory failing tests, a battery reporting a degraded health status) that’s worth bringing to your Chromebook’s manufacturer or the Chromebook Community Forum, which is where Google directs users when its own connectivity and display troubleshooting doesn’t resolve the issue. A screen that glitches even in recovery mode, before your account or any software you installed is even loaded, is a strong sign the display panel or its cable connection inside the chassis needs physical repair.

It’s also worth checking whether the glitching correlates with freezing or crashing more broadly rather than being purely visual. If your Chromebook is also locking up or restarting unexpectedly, our guides on why a Chromebook keeps freezing and why a Chromebook keeps crashing cover causes that overlap with display glitching and might explain both symptoms at once.

How Do I Make Sure I Don’t Lose My Tabs While Troubleshooting?

Save your open tabs as a session before you touch anything beyond a simple restart, because none of Google’s official troubleshooting steps back up what you had open. A restart can lose unsaved tab state if it doesn’t go cleanly, a hard reset forcibly interrupts everything running, and Powerwash closes every window as a matter of course.

Chrome’s own “Continue where you left off” setting reopens your previous tabs, but it’s not built for troubleshooting a glitching device. It doesn’t survive Powerwash, and it can misbehave on the very display that’s already acting up. It also doesn’t keep any history of what you had open before, so if something goes wrong mid-restart, there’s nothing to fall back on.

1. Install BelayTab from the download page. It works across Chrome, Edge, Brave, and other Chromium-based browsers on a Chromebook.
2. Save your current window as a named session. Click the BelayTab icon or press Ctrl+Shift+S, name it something you’ll recognize, and it’s saved instantly — tab groups, pinned tabs, and order all stay intact.
3. Troubleshoot without worrying about the screen. Restart, hard reset, or Powerwash as needed, then reopen BelayTab and restore the session into a new window when you’re back up and running.

BelayTab also saves a snapshot of every open window on its own every 5 minutes, plus each time a window closes, so even if the glitching catches you mid-session before you think to save manually, there’s still a recent snapshot waiting in the Recovery screen. It’s free, works with no account required, and never reads what’s on your pages. It just remembers which tabs were open. Learn more on the tab restore feature page, or see how automatic snapshots work behind the scenes.

If you’re troubleshooting other Chromebook problems alongside this one, our guide to Chromebook tabs and the full list of Chromebook shortcuts are worth bookmarking for next time — a glitching screen has a way of showing up right when you least expect it.