Chrome quietly leans on your computer’s graphics card to render pages, play videos, and smooth out animations. Most of the time you never notice it happening.
But sometimes that same setting turns into the reason your browser freezes, flickers, or eats up your graphics card for no clear reason.
If you landed here, chances are Chrome has been acting strange lately. Maybe videos stutter, tabs crash without warning, or your screen flashes oddly while scrolling.
The fix is usually simple, but the exact path to it shifts slightly depending on whether you’re on Windows, Mac, Linux, or a Chromebook. This guide walks through each one so you can turn the setting off in under a minute.
What Hardware Acceleration Actually Does in Chrome?
Hardware acceleration means Chrome hands certain jobs to your GPU instead of making your CPU do all the work alone. Rendering video, drawing animations, and handling complex page layouts are the usual tasks it offloads.
Your CPU is built for general tasks. Your GPU is built specifically for visual, repetitive math, the kind that comes up constantly on modern websites.
By splitting the work this way, Chrome can load pages faster and keep scrolling smooth, especially on sites packed with video or graphics. This is why Chrome, along with most other modern browsers, turns hardware acceleration on by default.
The setting exists to help, not to cause trouble. Problems only tend to surface when there’s a mismatch somewhere between your graphics driver, your operating system, and the way Chrome tries to use your GPU.
Why You Might Want to Turn It Off
When hardware acceleration works as intended, you never think about it. When it doesn’t, the symptoms are hard to ignore.
Tabs that crash randomly, especially during video playback, are one of the most common complaints. Screen flickering or brief flashes of black while scrolling point to the same root cause.
Some users notice their GPU usage spikes far higher than it should, even on simple pages with no video at all. This often traces back to a graphics driver that hasn’t kept pace with Chrome’s updates.
Older or budget graphics cards sometimes struggle to keep up with what Chrome asks of them. In these cases, switching the work back to the CPU can actually make things run smoother, not slower.
None of this means hardware acceleration is broken by design. It simply means your particular hardware and driver combination isn’t playing nicely with it right now.
How to Turn Off Hardware Acceleration in Chrome?
The setting itself lives in the same general spot across every desktop version of Chrome: inside Settings, under the System section. What changes slightly is how you get there and how the menu is worded on each device.
On Windows and Mac, the toggle sits under Settings > System and is labeled “Use graphics acceleration when available.” Linux follows the same path, though a handful of distributions add small quirks worth knowing about.
Below is the exact route for each platform, so you don’t have to guess or hunt through menus.
On Windows
Open Chrome and click the three dots in the top right corner of the window. From that menu, select Settings.
Once the Settings tab opens, click System in the left sidebar. You’ll see a toggle labeled “Use graphics acceleration when available.”
Click the toggle to switch it off. A Relaunch button will appear right next to it, so click that to restart Chrome and apply the change.
Save any open work first. Chrome will reopen your tabs after relaunching, but it won’t preserve unsaved form data or drafts sitting inside them.
On Mac
The steps on a Mac closely mirror Windows, with only small wording differences here and there. Click the three dots in the top right of the Chrome window, then choose Settings.
In the left sidebar, click System, the same as you would on Windows. The toggle reads “Use graphics acceleration when available” here too.
Turn the switch off, then click Relaunch when it appears. Chrome will close and reopen with the change applied.
Mac users occasionally run into a macOS permission prompt tied to graphics access, particularly on machines with dedicated GPUs. If that shows up, approving it once is usually enough to avoid repeat prompts.
On Linux
Linux users follow nearly the same click path inside Chrome itself. Open the three-dot menu, choose Settings, then click System in the sidebar and toggle the switch off.
Where Linux differs is under the hood. Many distributions rely on open-source graphics drivers, and these sometimes handle GPU acceleration less predictably than proprietary Windows or Mac drivers.
If toggling the setting off in Chrome doesn’t fully resolve flickering or crashes, some users find it helpful to also disable acceleration through Chrome’s launch flags. This is a more advanced step and isn’t necessary for most people.
On Chromebook
Chromebooks run ChromeOS, which handles GPU rendering at the system level rather than leaving it fully up to the browser. Because of this, you won’t find the same “Use graphics acceleration when available” toggle sitting inside Chrome’s regular System settings on a Chromebook.
Instead, GPU-related controls on ChromeOS mostly live inside chrome://flags, a separate area meant for experimental and advanced settings. Typing that into the address bar and searching for terms like “hardware accelerated” will surface a handful of related toggles, including options for video decoding specifically.
These flags aren’t identical to the desktop toggle, and Google can change or remove them between ChromeOS updates. If you’re troubleshooting a specific glitch on a Chromebook, it’s worth confirming through Chrome’s own support pages which flag applies to your ChromeOS version before changing anything.
Signs Hardware Acceleration Is Actually the Problem
Not every Chrome hiccup traces back to this one setting. Before assuming it’s the culprit, a few symptoms line up closely enough to be worth testing.
- Video stutters or lags specifically during playback, not general browsing
- Chrome crashes tend to happen right when a video or animation loads.
- Brief black flashes or flickers appear while scrolling or resizing windows.
- Task Manager shows unusually high GPU use even on plain, text-heavy pages.
- Visual glitches show up only in Chrome, not in other apps or browsers.
If several of these match what you’re seeing, hardware acceleration is a reasonable first thing to rule out. If your issues look nothing like this list, for instance slow page loads with no graphics involved at all, the cause likely sits elsewhere.
What to Do If Turning It Off Doesn’t Fix the Issue?
Disabling the setting solves the problem for plenty of people, but not everyone. If your symptoms stick around, a few other angles are worth checking.
Outdated graphics drivers are the single most common hidden cause behind Chrome’s GPU-related bugs. Visiting your GPU manufacturer’s site directly, rather than relying on automatic updates, usually gets you the newest stable version.
A cluttered cache can also cause odd rendering behavior that looks similar to a hardware acceleration issue. Clearing it through Settings > Privacy and security > Clear browsing data is worth trying next.
Browser extensions, particularly ones that modify page appearance or inject scripts, sometimes conflict with how Chrome renders content. Disabling extensions one at a time, or all at once through Chrome’s Extensions menu, can help isolate the real cause.
If none of this resolves things, typing chrome://gpu into the address bar shows a detailed breakdown of what your graphics setup is and isn’t doing. Lines marked in yellow or red usually point directly at the feature causing trouble.
How to Turn Hardware Acceleration Back On?
Reversing the change follows the identical path you used to turn it off. Head back into Settings, then System, on Windows, Mac, or Linux.
Flip the “Use graphics acceleration when available” toggle back on, then click Relaunch. Chrome will restart and resume offloading tasks to your GPU as it did before.
On Chromebook, this means returning to chrome://flags and resetting whichever GPU-related flag you changed back to its default state. Most flags list a “Default” option alongside Enabled and Disabled for exactly this reason.
Getting the Most Stable Chrome Experience Going Forward
Hardware acceleration is just one piece of a much larger picture when it comes to how smoothly Chrome runs. Outdated drivers, too many open tabs, and heavy extensions all pull weight too.
Keeping your graphics drivers current matters more than most people realize, since it’s often the true root cause hiding behind acceleration-related glitches. Checking your manufacturer’s site every few months takes little time and prevents a lot of guesswork later.
Google’s own Chrome help documentation stays updated as menu wording and settings shift across versions, so it’s a reliable place to double-check anything that looks different from what’s described here.
If your browser feels sluggish again down the road, don’t assume acceleration is automatically to blame. Check chrome://gpu first, confirm what’s actually happening, and only flip the switch once you know it’s the real cause.