Hardware acceleration in Chrome moves graphics rendering — animations, video playback, scrolling effects, WebGL — from the CPU to the GPU. On most modern systems, this is a performance improvement. On some specific hardware and driver combinations, it’s the cause of screen flickering, black pages, visual corruption, crashes, or high GPU temperatures. Disabling it is the right call in those situations. You’ll find the complete rundown in our Chrome How-To Guides.
If you’re experiencing any of these visual problems and you’re not sure whether hardware acceleration is responsible: disabling it takes one minute and you’ll know within a few seconds of reopening Chrome whether the problem is resolved.
How to disable hardware acceleration
chrome://settings → System → “Use hardware acceleration when available” → toggle Off → “Relaunch” button appears → click it. Chrome restarts. The setting applies immediately after relaunch.
That’s it for the basic disable. The browser now handles all rendering through software (CPU), which is slower for graphics-intensive tasks but more stable on hardware with GPU driver issues.
Symptoms that suggest hardware acceleration is the cause
Not every visual problem in Chrome is related to hardware acceleration. Signs it’s specifically the culprit:
- Black or white areas appear in Chrome windows while other applications display correctly
- Screen tears or horizontal lines specifically while Chrome is the active window
- Chrome crashes with a GPU-related error in the crash report (chrome://crashes)
- Video playback looks garbled or shows green/pink tint
- Problems started after a GPU driver update or Windows Update that included display drivers
- The issue doesn’t appear in Incognito mode (Incognito disables extensions but not hardware acceleration, so if Incognito is the same: it’s not an extension, might be hardware acceleration)
- Chrome’s GPU diagnostics at chrome://gpu show errors or unexpected status for rendering features
Problems NOT typically caused by hardware acceleration: slow page loading, high CPU usage from JavaScript, slow JavaScript execution, poor text rendering (that’s usually a DPI setting), or crashes that happen regardless of GPU activity.
chrome://gpu — diagnosing the GPU state
Before disabling, it’s worth checking chrome://gpu. This page shows Chrome’s current GPU usage status, which features are hardware-accelerated vs software-rendered, and any problems Chrome has detected. Look for lines marked “Software only, hardware acceleration unavailable” or error messages about specific GPU features.
If chrome://gpu already shows many features as “Software only” or lists a “Driver bug workaround” applied: Chrome has already partially disabled hardware acceleration on your system due to detected driver issues. In this case, fully disabling hardware acceleration often stabilises things that Chrome’s partial workaround didn’t fully address.
Update GPU driver first
Before disabling hardware acceleration permanently: try updating the GPU driver. Driver bugs are the most common cause of hardware acceleration problems, and they’re often fixed in subsequent driver releases. NVIDIA users: download from nvidia.com/drivers. AMD users: download from amd.com/en/support. Intel integrated graphics: from intel.com/content/www/us/en/download-center.
Windows Update doesn’t always have the latest GPU driver. Going directly to the manufacturer’s site often gives you a newer version. After updating: re-enable hardware acceleration in Chrome and test. If the visual problems return: the new driver didn’t fix the specific issue, and disabling remains the better option. If they’re resolved: you’ve fixed the root cause rather than working around it.
Re-enabling hardware acceleration
Disabling hardware acceleration is reversible at any time. chrome://settings → System → toggle “Use hardware acceleration” back On → Relaunch. After re-enabling: test with chrome://gpu to confirm it’s active and check whether the visual problems have returned. Good reasons to re-enable: you updated the GPU driver and want to test the fixed version, you’re testing on a different monitor, or you need to use WebGL-dependent features that only work with hardware acceleration.
Tip: if you regularly switch between hardware acceleration states for testing: keep a tab with chrome://settings#system open so the toggle is one click away rather than requiring navigation each time.
Our guide on Chrome crashes and stability covers GPU-related crashes and other crash types, and our Chrome performance issues covers performance problems that have different causes. For GPU driver updates and Chrome’s hardware requirements, Google’s Chrome system requirements documentation lists supported GPU configurations and known driver compatibility issues.
Performance impact of disabling hardware acceleration
With hardware acceleration off: Chrome handles all rendering through software on the CPU. The practical impact depends heavily on what you do in Chrome:
- Text browsing and forms: no noticeable difference. Software rendering handles static content without issue.
- Video playback: more CPU usage, possible dropped frames on lower-end hardware. 4K video especially will stress the CPU more than it would the GPU.
- WebGL and canvas animations: noticeably slower or may not work at all for complex graphics. Web-based 3D applications, certain games, and data visualisations depend on GPU access.
- Scrolling: sometimes smoother on problematic hardware (because the GPU was causing the jank), sometimes slightly less smooth (because software rendering at high frame rates is harder to achieve).
For most office, browsing, and productivity use: the performance difference is imperceptible. For video-heavy use or browser-based creative tools: hardware acceleration should be on if the hardware supports it without issues.
Hardware acceleration on specific hardware types
Integrated Intel graphics (most laptops): hardware acceleration generally works well on recent Intel generations (Iris Xe and newer). Older Intel HD Graphics occasionally have driver issues with Chrome. If you’re on an older Intel GPU and having problems: try the latest Intel driver before disabling.
NVIDIA discrete GPU: generally stable with hardware acceleration. Issues more commonly arise when using NVIDIA Optimus (dual GPU switching between integrated and discrete) rather than a discrete-only GPU. Some Optimus configurations confuse Chrome about which GPU to use.
AMD: generally stable on recent Radeon drivers. Some older AMD Radeon driver versions had specific Chrome compatibility issues that were fixed in subsequent driver releases. Keeping AMD drivers current is particularly important for Chrome hardware acceleration stability.
External GPUs (eGPU): Chrome sometimes doesn’t switch correctly to an eGPU when connected. chrome://gpu will show which GPU Chrome is using — if it’s showing the integrated GPU when you have a powerful eGPU connected: there’s a GPU selection issue that may need addressing through NVIDIA/AMD control panel settings rather than Chrome’s hardware acceleration toggle.
| Problem | Hardware acceleration likely cause? | First step |
| Black areas in Chrome window | Yes | Disable hardware acceleration |
| Screen flickering in Chrome | Probably | Check chrome://gpu, then disable |
| Chrome crashes after GPU driver update | Yes | Roll back driver or disable acceleration |
| Slow JavaScript execution | No | Check extensions, Task Manager |
| High CPU usage in Chrome | Sometimes (if GPU is failing and CPU compensates) | Check chrome://gpu first |
| Video shows wrong colours | Yes | Disable hardware acceleration or update GPU driver |
Hardware acceleration is one of the first settings to change when Chrome starts behaving visually strangely. The toggle is accessible, the change is immediate after relaunch, and re-enabling is just as easy. When in doubt about whether it’s the cause: disable it, reproduce the scenario, and you’ll know within minutes.
Hardware acceleration and high DPI displays
On 4K or high DPI monitors with non-standard scaling (125%, 150%, fractional scaling): hardware acceleration is particularly important for rendering the browser at the correct resolution. With hardware acceleration disabled on high DPI displays: Chrome may fall back to rendering at a lower resolution and upscaling, which looks blurry. If you disable hardware acceleration and text or UI elements suddenly look blurry on your high-DPI display: this is why. Re-enable it, or if that causes crashes, investigate the GPU driver issue rather than accepting the blurry fallback.
Chrome hardware acceleration vs Windows graphics settings
Windows 11 has its own hardware acceleration setting for graphics apps. Settings → System → Display → Graphics → Default graphics settings → “Hardware-accelerated GPU scheduling” (HAGS). This Windows feature and Chrome’s own hardware acceleration setting are different levels of the same GPU pipeline. Both can affect Chrome’s behaviour.
If Chrome has hardware acceleration enabled but you’ve disabled HAGS at the Windows level: Chrome loses some of the GPU scheduling benefits. If Chrome’s hardware acceleration is disabled: HAGS doesn’t apply to Chrome regardless of Windows settings. For the clearest test of hardware acceleration: ensure both Chrome’s setting and Windows’ HAGS are in the same state (both on or both off) during testing.
Chrome flags related to GPU rendering
Several chrome://flags entries affect hardware acceleration beyond the main settings toggle:
- #ignore-gpu-blocklist: Chrome maintains a list of GPUs known to have driver bugs and disables certain features for them. Enabling this flag ignores the blocklist and forces hardware acceleration even on GPUs in the list. Useful for testing but may cause instability if your GPU is listed for a reason.
- #enable-gpu-rasterization: enables rasterising web content on the GPU rather than CPU. Can improve scrolling performance on pages with complex graphics.
- #enable-zero-copy: allows Chrome to write to the GPU’s memory directly, bypassing the CPU. Can reduce latency for certain rendering operations.
These flags are for advanced testing. If you’ve disabled hardware acceleration via the main Settings toggle: these flags have no effect — the GPU pipeline is already bypassed. They’re relevant only when hardware acceleration is enabled and you’re trying to fine-tune GPU usage.
Multiprocess rendering and the GPU process
Chrome’s GPU process is separate from its browser and renderer processes. You can see it in Chrome’s Task Manager (Shift+Esc) as “GPU Process.” When hardware acceleration is on: this process handles compositing and rendering for all tabs. When hardware acceleration is off: the GPU process still runs but does much less work.
If the GPU process is consuming unusually high memory or CPU: this suggests the GPU is struggling with the rendering workload rather than handling it efficiently. This is a sign that either the content being rendered is very demanding (3D web apps, high-framerate animations on many tabs) or the GPU driver has an efficiency issue. Checking chrome://gpu for error messages and updating the driver are the appropriate responses before disabling acceleration entirely.
Chrome’s hardware acceleration implementation has matured considerably over the years. Most GPU driver issues that plagued it in the 2018-2020 era have been addressed. If you disabled hardware acceleration years ago as a fix: it’s worth trying to re-enable it on a current Chrome and driver version — the problem that prompted the disable may no longer exist, and you’d be missing the rendering improvements that have been added since. Current Chrome with current GPU drivers handles hardware acceleration reliably on most hardware configurations.
Verifying the change took effect
After toggling hardware acceleration and relaunching Chrome: visit chrome://gpu to confirm the change. With hardware acceleration enabled, you’ll see most features listed as “Hardware accelerated.” With it disabled, most show “Software only, hardware acceleration unavailable.” The page updates to reflect the current state immediately after Chrome restarts.
A second verification method: Task Manager (Shift+Esc in Chrome) → watch the GPU Process memory usage while scrolling through a graphics-heavy page. With hardware acceleration on, GPU memory usage increases during rendering. With it off, the GPU Process uses minimal memory because the CPU is handling the rendering work instead.
When problems persist after disabling hardware acceleration
If visual glitches or crashes continue even with hardware acceleration off: the cause is elsewhere. Next steps to investigate:
- Extensions: disable all extensions → test. Some extensions that inject code into pages (screenshot tools, overlay apps) can cause rendering issues independently of GPU settings.
- Chrome profile corruption: create a new Chrome profile → test. Profile-specific problems don’t appear in a clean profile.
- Chrome update: check chrome://settings/help to ensure Chrome is on the latest version. Rendering bugs are regularly fixed in updates.
- Operating system display drivers: beyond the GPU driver, the Windows display driver stack and monitor connection (DisplayPort vs HDMI, cable quality) can affect rendering. Swap the cable, try a different port, or test with a different monitor to isolate hardware-level display issues from software-level ones.
Hardware acceleration is a meaningful diagnostic tool in Chrome troubleshooting because it produces clear, binary results: the problem either persists with it off or it doesn’t. That tells you definitively whether GPU rendering is involved, which determines the next direction for the investigation.
One more point worth knowing: hardware acceleration in Chrome is separate from hardware-accelerated video decoding (H.264, VP9, AV1). Chrome can use hardware video decoding even when the main hardware acceleration toggle is off, depending on your system configuration. chrome://gpu → Media section shows whether hardware video decoding is active. If video performance is your specific concern: check the Media section of chrome://gpu separately from the overall hardware acceleration status — they’re controlled by different paths. You might also run into Chrome Task Manager.
