Chrome freezing — the whole window going unresponsive, a tab hanging with a spinning cursor, or the browser crashing entirely — is usually caused by one of a handful of identifiable problems. Most fixes take under two minutes. Work through these in order from fastest to most involved.
Fix 1: Use Chrome’s Built-In Task Manager
Before anything else, find out what’s actually causing the freeze.
Press Shift+Esc to open Chrome’s Task Manager. It shows every open tab, extension, and Chrome internal process alongside its Memory Footprint and CPU usage.
Look for:
- A tab using unusually high CPU (above 50-100% for an extended period)
- An extension using large amounts of memory
- A GPU process consuming excessive resources
Click the problem item and click End Process. This closes just that tab or extension without affecting the rest of Chrome.
If Chrome is already completely frozen and Shift+Esc doesn’t open the Task Manager, see Fix 11 below.
Fix 2: Close Tabs You Aren’t Using
Chrome processes each tab as a separate process, and each one uses memory. Thirty tabs with complex pages open simultaneously can push even a capable machine to its limits.
Close tabs you’re not actively using. If you want to save them for later without them consuming memory:
- Bookmark all tabs: right-click any tab → Bookmark all tabs → choose a folder
- Use Chrome’s Reading List (accessible from the address bar’s bookmark icon) for pages you plan to return to
- Or use the Memory Saver setting described below
Fix 3: Disable Hardware Acceleration
Hardware acceleration offloads rendering to your GPU. On systems with outdated or conflicting GPU drivers, this causes more problems than it solves — including freezes, white screens, and visual corruption.
To disable it:
- Click the three-dot menu → Settings
- Click System in the left sidebar
- Toggle off Use graphics acceleration when available
- Click Relaunch
A driver conflict between Chrome 146+ and certain Windows 11 GPU driver versions was responsible for widespread freezing in 2026 on unpatched setups. Disabling hardware acceleration is the first thing to try if Chrome started freezing after an update.
Fix 4: Test Extensions in Incognito Mode
Extensions are one of the most common causes of Chrome freezes — they run in Chrome’s process space and a single poorly coded one can lock up the browser.
Quick test:
- Press Ctrl+Shift+N to open a new Incognito window
- Extensions are disabled in Incognito by default
- Browse for a few minutes — if Chrome doesn’t freeze in Incognito, an extension is the culprit
To isolate which extension:
- Go to chrome://extensions
- Toggle extensions off one at a time
- Reload Chrome after each toggle
- When the freezing stops, the last extension you disabled is the problem
Common offenders: ad blockers with large filter lists, screenshot tools, password managers with sync issues, and tab management extensions.
Fix 5: Clear Cache and Cookies
A corrupted cache can cause Chrome to freeze on specific sites or behave erratically. Clearing it is harmless — it removes temporary files, not bookmarks or passwords.
- Press Ctrl+Shift+Delete (Cmd+Shift+Delete on Mac)
- Set the time range to All time
- Check Cached images and files (you can also check Cookies if a specific site is the problem)
- Click Clear data
- Relaunch Chrome
See How to Clear Cache in Chrome for a full walkthrough with screenshots.
Fix 6: Update Chrome
Chrome updates frequently include fixes for specific bugs, including memory leaks and crash-causing regressions. If you’ve been dismissing the update prompt (the three-dot icon turns green, orange, or red when an update is pending), now is a good time.
- Click the three-dot menu → Help → About Google Chrome
- Chrome checks for updates and installs them automatically
- Click Relaunch to complete the update
Chrome 127 patched a memory leak in the Tab Groups feature. Chrome 130 and later fixed WebRTC-related freezes that affected video call pages. If you’re behind on updates, catching up often resolves intermittent freezing.
Fix 7: Enable Memory Saver
Memory Saver puts inactive tabs to sleep, releasing the memory they were holding. When you click a sleeping tab, it reloads. The trade-off — a brief reload on return — is worth it for people who keep many tabs open.
- Click the three-dot menu → Settings → Performance
- Toggle on Memory Saver
- You can add exceptions for specific sites you always want to keep active
Memory Saver is most effective when Chrome’s Task Manager shows high total memory use spread across many tabs rather than one specific tab being the problem.
Fix 8: Check for Malware
Adware and browser-hijacking software can inject scripts into pages or run background processes that cause freezing. This is more common on Windows than Mac.
Chrome used to include a Windows cleanup tool for this, but Google retired it in Chrome 111 (March 2023). Instead:
- Run a full scan with Windows Security (Microsoft Defender), Malwarebytes, or a similar reputable scanner
- Remove any programs you don’t recognise from your installed apps list
- Open
chrome://extensionsand remove extensions you didn’t install yourself - Reset Chrome’s settings at Settings → Reset settings → Restore settings to their original defaults
Signs that malware might be the cause: Chrome redirecting searches to unfamiliar search engines, unusual new extensions appearing that you didn’t install, excessive ads on sites that don’t normally show many, or Chrome freezing specifically when you try to open certain pages.
Fix 9: Disable or Update GPU Drivers
If disabling hardware acceleration (Fix 3) made the freezing stop, the underlying problem is a GPU driver issue. Disabling hardware acceleration is a workaround, not a fix — the proper resolution is updating your GPU driver.
On Windows:
- Right-click Start → Device Manager
- Expand Display adapters
- Right-click your GPU → Update driver → Search automatically for drivers
Or visit your GPU manufacturer’s website directly: NVIDIA (nvidia.com/drivers), AMD (amd.com/support), or Intel (intel.com/content/www/us/en/download-center).
After updating, re-enable hardware acceleration in Chrome and test.
Fix 10: Create a New Chrome Profile
If Chrome freezes consistently on your profile but works for other users on the same machine, your profile data may have become corrupted.
- Click the account circle in the top-right corner of Chrome → Add
- Create a new local profile (no sign-in required for testing)
- Open the same sites and tabs you normally use
If the new profile doesn’t freeze, your original profile data (preferences, extension states, cached settings) is likely corrupted. You can transfer bookmarks by exporting from the old profile and importing into the new one — see How to Export Chrome Bookmarks.
Fix 11: Force-Quit Chrome When It’s Completely Frozen
If Chrome is fully unresponsive and nothing works from within it:
On Windows:
- Press Ctrl+Shift+Esc to open Task Manager
- Find Google Chrome or chrome.exe in the list
- Right-click → End task
Multiple chrome.exe processes are normal. End the one using the most CPU or RAM, or right-click the top-level Google Chrome process and select End task to close all Chrome processes at once.
On Mac:
- Press Cmd+Option+Esc
- Select Google Chrome
- Click Force Quit
When Chrome reopens, it will offer to restore your previous tabs.
Chrome Freezing on Startup
If Chrome becomes unresponsive before any tabs fully load — the window appears but nothing renders, or Chrome crashes within a few seconds of opening — the cause is usually different from a mid-session freeze.
Session restore is loading a bad tab. Chrome restores your last session by default. If a tab from that session was running a heavy script, autoplaying video, or had a memory leak when you closed Chrome, it may freeze the browser on restoration. Fix:
- Go to Settings > On startup
- Change the setting from “Continue where you left off” to “Open the New Tab page”
- This prevents the problematic session from being restored automatically
If you want to keep session restore but test whether it’s the cause: the next time Chrome starts, quickly click the X on tabs as they appear before they fully load. If Chrome stops freezing after you close a specific tab, that tab was the culprit.
A new-tab page extension is crashing. Extensions that replace Chrome’s new-tab page load immediately on startup. If such an extension has a bug or is broken, Chrome may freeze as soon as a new tab opens. Start Chrome in Incognito mode (Ctrl+Shift+N, or right-click the desktop shortcut > New Incognito Window) — extensions are disabled in Incognito by default. If Chrome does not freeze in Incognito, a new-tab extension is the cause.
Too many pinned tabs. Pinned tabs reload automatically when Chrome starts. If you have a large number of pinned tabs, especially ones with heavy scripts or autoplaying content, Chrome can become temporarily unresponsive on launch. Reduce pinned tabs to the sites you genuinely open every day.
Chrome Freezing on Mac: Platform-Specific Notes
A few freeze scenarios that occur more commonly on macOS than Windows:
After a macOS update: A macOS system update can temporarily create GPU driver inconsistencies that cause Chrome to freeze or render incorrectly until Chrome itself updates to match the new system. If Chrome started freezing immediately after a macOS update, check for a Chrome update first: three-dot menu > Help > About Google Chrome. The Chrome update and the macOS update may need to land together to resolve the conflict.
Large Chrome profile on older storage: On Macs with older or slower SSDs, a large Chrome profile — accumulated over years, with many extensions and stored data — can cause Chrome to hang on startup while reading the profile from disk. Chrome’s profile folder lives at ~/Library/Application Support/Google/Chrome/Default. If the profile is very large (check with Finder: Go > Go to Folder > paste the path > check folder size), clearing the cache (Ctrl+Shift+Delete) reduces the read burden at startup.
System Integrity Protection and extensions: On macOS, certain enterprise or third-party security tools intercept Chrome’s startup process, causing delays that manifest as freezing. If Chrome freezes specifically on launch but not after it’s running, check your security software settings for Chrome exceptions.
A Note on Bookmarks and Freezing
If Chrome is freezing when you open the Bookmark Manager specifically, a very large bookmark collection (tens of thousands of bookmarks) can cause the chrome://bookmarks page to render slowly or hang. This is a rendering performance issue. Organizing bookmarks into more folders, removing duplicates, and clearing out dead links can reduce the load.
Bookmend can identify duplicate bookmarks and dead links in bulk, which reduces the overall count and makes the Bookmark Manager more responsive. It’s a side benefit if you’re doing a cleanup for other reasons.
Frequently asked questions
Press Shift+Esc while Chrome is open. The Task Manager shows every open tab, extension, and Chrome process with its memory footprint and CPU usage. Find the tab or extension using the most resources and click End Process to close it.
A single tab can cause a freeze if it contains a runaway script, an autoplaying video with high decode requirements, or WebRTC (video call) content. Check Chrome's Task Manager (Shift+Esc) to see which tab is using disproportionate CPU or memory. Extensions can also cause freezing even with few tabs open — check those in the Task Manager as well.
Often yes — it's one of the most reliable fixes, particularly on systems where the GPU driver hasn't been updated recently. Hardware acceleration offloads rendering to the GPU. If there's a driver conflict, it causes visual stutters or full freezes. Go to Settings → System → Use graphics acceleration when available, toggle it off, and relaunch Chrome.
Press Ctrl+Shift+Delete (Cmd+Shift+Delete on Mac). A dialog opens — set the time range to All time, check Cached images and files, and click Clear data. This does not delete your bookmarks or passwords, only temporary cached files.
Yes. A single poorly coded or resource-intensive extension can freeze Chrome completely. To test, open a Chrome window in Incognito mode (Ctrl+Shift+N) — by default, extensions are disabled in Incognito. If Chrome runs fine in Incognito, an extension is likely responsible. Go to chrome://extensions and disable extensions one by one to isolate the culprit.
If Chrome is completely unresponsive, open your operating system's Task Manager (Ctrl+Shift+Esc on Windows, Activity Monitor on Mac) and force-quit the chrome.exe / Google Chrome process. On Windows, there may be multiple chrome.exe processes — end the one using the most CPU or RAM, or end all of them. Chrome will then restart with a crash recovery prompt.
Chrome uses memory for each tab and extension as separate processes, which is a deliberate architectural decision to prevent one crashed tab from taking down the whole browser. Chrome also has a Memory Saver feature (in Settings) that automatically frees memory from inactive tabs. If total RAM is the issue, Memory Saver and limiting simultaneous tabs are the most direct responses.
Yes. Adware and browser-hijacking malware can inject scripts into pages, intercept network requests, or run background processes that consume resources and cause freezes. Chrome's old built-in cleanup tool was retired in Chrome 111 (March 2023), so run a full scan with Microsoft Defender or another reputable malware scanner, then reset Chrome's settings.
If a profile has accumulated corrupted data, preferences, or cached extension states, creating a new profile and seeing if it freezes helps isolate whether the profile data is the problem. Go to chrome://settings/manageProfile, add a new profile, and test. If the new profile doesn't freeze, your original profile data may be corrupted.
Click the three-dot menu → Help → About Google Chrome. Chrome will check for updates and install them automatically. You'll see a Relaunch button when an update is ready. Chrome updates sometimes contain fixes for specific crash or freeze bugs.
Memory Saver is a Chrome feature (in Settings → Performance) that puts inactive tabs to sleep, freeing the memory they were using. When you click an inactive tab, it reloads. It's a good option if you habitually keep 20+ tabs open and experience slowdowns.

