Fix Chrome Stuck on Loading or Waiting for Cache

If Google Chrome is stuck on “Loading…” or “Waiting for cache” and pages never finish loading, the problem is often a corrupted cache or a stalled cache-writing process. This guide walks you through the most effective fixes, from clearing the cache to resetting Chrome’s internal data, so you can get back to browsing quickly.

What You’ll Need

• Access to Chrome’s settings (or the ability to delete its profile folder if it won’t open)
• Administrator rights on your computer (for some steps)
• About 10–15 minutes of time

Step-by-Step

1. Force-quit Chrome completely. Close all Chrome windows. On Windows, press Ctrl+Shift+Esc to open Task Manager, look for any “Google Chrome” processes, select them, and click “End Task.” On Mac, press Cmd+Option+Esc, select Chrome, and click “Force Quit.” This clears any stuck processes that might be holding the cache.
2. Clear the cache from the address bar. Reopen Chrome. In the address bar, type chrome://settings/clearBrowserData and press Enter. This opens the “Clear browsing data” panel.
3. Choose the right time range. At the top of the panel, select “All time” from the drop-down. This ensures you clear the entire cache, not just the last hour.
4. Check the boxes for “Cached images and files” and “Cookies and other site data.” You can leave other boxes unchecked if you want to keep your history and passwords. Clearing cookies will sign you out of most websites, so be prepared to log back in.
5. Click “Clear data.” Wait for the confirmation. If Chrome is still stuck, proceed to the next step.
6. Disable hardware acceleration. Go to chrome://settings/system. Turn off the toggle for “Use hardware acceleration when available.” Then click “Relaunch” at the bottom of the page. This often fixes cache-writing stalls caused by graphics driver conflicts.
7. Reset Chrome’s cache folder manually. If Chrome still won’t load, close it again. Then navigate to your user data folder:
   – Windows: C:\Users\[YourUsername]\AppData\Local\Google\Chrome\User Data\Default\Cache
   – Mac: ~/Library/Caches/Google/Chrome/Default/Cache
   Delete the entire Cache folder. Chrome will recreate it on next launch. Do not delete the whole “User Data” folder—only the Cache subfolder.
8. Create a new Chrome profile. If the cache folder deletion didn’t help, the profile itself may be corrupted. Close Chrome, then rename the “Default” folder inside “User Data” to “Default.old.” Relaunch Chrome—it will create a fresh profile. You can later move bookmarks and passwords manually, but this is a last resort.
9. Run Chrome’s built-in cleanup tool. Go to chrome://settings/cleanup and click “Find and remove harmful software.” This removes any extensions or programs that might be interfering with Chrome’s cache.
10. Reinstall Chrome. If nothing else works, uninstall Chrome (keep your bookmarks by signing in and syncing first), then download and install the latest version from the official site. This resets all internal files, including the cache management system.

Common Mistakes

• Only clearing the last hour. If the corruption is old, you need “All time.”
• Not closing Chrome before deleting cache files. If Chrome is running, it will overwrite your changes or lock the files, so the fix appears not to work.
• Deleting the entire “User Data” folder. This wipes your bookmarks, passwords, and extensions. Only delete the “Cache” subfolder or rename “Default.”
• Skipping the hardware acceleration step. Many “Waiting for cache” issues are actually GPU-related, and disabling acceleration solves them instantly.
• Assuming it’s a network problem. If other browsers work fine, it’s almost certainly Chrome’s cache, not your internet connection.

Tips

• Use Chrome’s built-in task manager (chrome://tasks) to see if a specific tab or extension is consuming huge memory—this can cause cache stalls.
• Keep your Chrome version updated. Go to chrome://settings/help and let it update automatically. Older versions have more cache bugs.
• If you use many extensions, try disabling them temporarily via chrome://extensions. A poorly coded extension can block cache writes.
• Consider setting Chrome to “Continue where you left off” instead of restoring all tabs—restoring many tabs at once can trigger cache waiting.
• Periodically clear your cache yourself (every few weeks) to prevent buildup that leads to corruption.

Troubleshooting

If the problem persists after following all steps:

• Check your antivirus or firewall. Some security software intercepts Chrome’s cache writes. Temporarily disable it to test, then add an exception for Chrome.
• Try Chrome’s “Guest mode.” Open a guest window (click your profile icon > Guest). If it loads fine, the issue is profile-specific; use the profile rename trick from Step 8.
• Look for disk errors. On Windows, run chkdsk /f in an elevated Command Prompt. On Mac, run First Aid in Disk Utility. A failing hard drive can cause cache write failures.
• Check for conflicting software. Programs like CCleaner or system optimizers sometimes lock Chrome’s cache. Uninstall them temporarily.
• If Chrome won’t even open to access settings, use the manual cache folder deletion (Step 7) or rename the “Default” folder (Step 8) directly from File Explorer/Finder.
• As a final test, create a brand new Windows user account or Mac user account and try Chrome there. If it works, the issue is tied to your user profile’s permissions, not Chrome itself.

Frequently Asked Questions

Will clearing my cache log me out of websites?

Yes, clearing cookies and cached files will log you out of most sites. Your saved passwords and bookmarks are kept unless you also clear those boxes.

What does “Waiting for cache” actually mean?

It means Chrome is trying to read or write data to its cache folder on your disk, but the operation is hanging—usually due to corruption, a locked file, or a slow disk.

Is it safe to delete the Cache folder manually?

Yes, it’s safe. Chrome will recreate it automatically. You won’t lose bookmarks or passwords, only temporary files that speed up loading.

Why does this happen so often?

Common causes include forced shutdowns while Chrome is running, low disk space, antivirus interference, or outdated graphics drivers. It’s not a sign of a virus.

Will reinstalling Chrome remove my bookmarks?

Only if you don’t sync them. Sign in to Chrome before uninstalling, and they’ll come back automatically. Alternatively, export your bookmarks to an HTML file first.

Does this happen on Chrome for Android or iOS?

Rarely. The “Waiting for cache” error is mostly a desktop issue. On mobile, clearing the app cache from the system settings usually fixes similar problems.

Related

• Fix Windows 10 Will Not Sleep: Complete Guide
• How to Fix Samsung Galaxy J7 That Won’t Activate
• Fix iPhone AssistiveTouch Not Working