sodcalculator

10 Tech How-To

Fix Google Chrome Waiting for Cache Error

Guide 10-47663 · Updated · Step by step

If Google Chrome is stuck on “Waiting for cache,” the browser is unable to read or write to its cache folder, usually due to corrupted cache files, permission issues, or interference from antivirus software. The quickest fix is to clear the cache, close all Chrome processes, and restart the browser; if that fails, disable hardware acceleration or reset the cache directory. Below are the detailed steps and background to resolve this error for good.

What “Waiting for Cache” Means

The cache is a local storage area where Chrome saves copies of web page resources (images, scripts, stylesheets) so that returning to a page loads faster. When the status bar shows “Waiting for cache,” Chrome’s network stack is blocked trying to access this folder. This can happen because the cache folder is locked by another process, the disk is full, or the cache files are corrupted. The browser cannot proceed with loading the page until it can read or write to that cache.

Why the Cache Gets Stuck

Several common triggers cause this error:

  • Corrupted cache files: A sudden power loss, crash, or forced shutdown can leave cache entries in an inconsistent state.
  • Permission problems: The Chrome profile folder may have incorrect read/write permissions, especially after moving or syncing the profile.
  • Antivirus or security software: Real-time scanning can lock the cache folder temporarily, causing Chrome to wait indefinitely.
  • Full disk: If the drive where Chrome stores its profile is out of space, the cache cannot be written.
  • Multiple Chrome processes: A hung background process may hold a lock on the cache folder.

How to Fix “Waiting for Cache”

Follow these steps in order. Most users resolve the issue with the first two steps.

  1. Force-close Chrome and restart. Open Task Manager (Ctrl+Shift+Esc on Windows, or Cmd+Option+Esc on Mac), select every Chrome process, and click “End Task.” Then relaunch Chrome.
  2. Clear the cache. Go to Chrome Settings > Privacy and security > Clear browsing data. Choose “Cached images and files” and a time range of “All time,” then click “Clear data.” This deletes the potentially corrupted cache files.
  3. Disable hardware acceleration. Go to Settings > System, turn off “Use hardware acceleration when available,” and restart Chrome. GPU-related glitches can sometimes cause cache access delays.
  4. Check disk space. Ensure the drive where Chrome is installed has at least a few hundred MB free. A full disk prevents cache writes.
  5. Reset the cache directory. Close Chrome, navigate to the profile folder (e.g., %LOCALAPPDATA%\Google\Chrome\User Data on Windows, ~/Library/Application Support/Google/Chrome on Mac), and rename the “Cache” subfolder to “Cache_old.” Chrome will create a new one on restart.
  6. Exclude Chrome from antivirus scanning. If you use third-party security software, add the Chrome profile folder to the exclusion list. This prevents the scanner from locking the cache.

When the Problem Persists

If the error continues after clearing the cache and disabling hardware acceleration, the issue may be with the entire Chrome profile. Try creating a new user profile (Settings > People > Manage profiles > Add profile). If the new profile loads pages normally, the old profile is corrupted. You can migrate bookmarks and passwords by signing in and enabling sync, but you may need to reinstall extensions. As a last resort, uninstall Chrome completely (check “Also delete your browsing data”) and reinstall from the official site. This resets all settings and the cache folder.

Preventing Future Cache Errors

To reduce the chance of recurrence:

  • Keep Chrome updated to the latest version, as cache handling bugs are often fixed in updates.
  • Regularly clear cached files (e.g., monthly) if you notice slowdowns.
  • Avoid force-quitting Chrome; use the normal close button.
  • Maintain at least 10% free space on your system drive.
  • If you use disk cleanup tools, avoid deleting the Chrome cache while the browser is running.

Common Misconceptions

Many believe that “Waiting for cache” means their internet connection is slow. In fact, it is a local issue — the network is fine, but the browser is stuck on disk I/O. Another misconception is that clearing the cache will log you out of websites. Clearing only “Cached images and files” does not affect cookies or site data, so you stay logged in. However, if you choose “Cookies and other site data” as well, you will be signed out.

Frequently Asked Questions

Will clearing the cache delete my passwords?

No. Passwords are stored separately in Chrome’s password manager, not in the cache. Clearing cached images and files will not remove saved passwords or autofill data.

Does this error happen on Mac and Linux too?

Yes. The “Waiting for cache” status appears on all desktop platforms. The fix steps are similar, but the profile folder path differs. On Linux, it is usually ~/.config/google-chrome.

Can I disable the cache entirely to avoid this?

You can run Chrome with the --disk-cache-size=0 flag to disable disk caching, but this will slow down page loads on repeat visits and is not recommended as a permanent solution. It is better to fix the underlying cause.

Why does “Waiting for cache” appear only on some websites?

Websites that use many resources (large images, scripts) require more cache writes. If the cache is partially corrupted, those sites may trigger the error while lighter sites load fine. Clearing the cache usually resolves this.

Is there a way to fix it without losing my browsing history?

Yes. Clearing only “Cached images and files” does not delete your history. History is stored separately and remains intact. If you need to reset the cache folder manually, your history is still preserved.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →