How I Clear Chrome Extension Context Cache on Mac to Fix Extension Issues Fast

My Grammarly extension stopped working mid-sentence one afternoon. Then my password manager started throwing errors every time I clicked it. I spent about 20 minutes trying everything obvious — toggling the extensions off and on, restarting Chrome — before figuring out the actual issue. The context cache was stale, and Chrome had no idea.

This guide covers what I actually tried, what worked, and in what order. I’m on a Mac running macOS Sonoma with Chrome 125, though these steps work on Ventura and Monterey too.

What Is the Chrome Extension Context Cache, Exactly?

When Chrome runs an extension, it stores temporary data — scripts, service worker state, cached API responses — in what’s called the extension context. Think of it as the extension’s short-term memory. It helps things load faster and lets the extension remember what you were doing.

The problem is that this cache can get corrupted, especially after a Chrome update, a macOS update, or when an extension updates itself without a clean restart. When that happens, Chrome might still think the extension is running fine, but the underlying context is broken. The extension hangs, throws errors, or just silently stops working.

It’s not a bug in the extension itself most of the time. It’s stale cached state that Chrome hasn’t flushed yet.

Symptoms That Point to a Cache Problem

Method 1: Reload the Extension (Quickest Fix)

This is what I try first, every time. It takes about ten seconds and solves roughly 60% of context issues I run into.

Method 2: Clear Cache via Chrome DevTools (Application Tab)

This is the method most guides skip. It directly targets the extension’s cached data — not just its runtime context. I use this when an extension is technically “running” but behaving weirdly, like loading old UI or returning outdated API data.

Method 3: Disable and Re-Enable the Extension

Simpler than DevTools, but slightly more thorough than just reloading. When you disable an extension, Chrome terminates all its processes, releases memory, and tears down the context. Re-enabling it spins everything up fresh.

Method 4: Delete the Extension’s Cached Files via Finder (Mac-Specific)

This is the nuclear option for persistent issues. Chrome stores each extension’s files in a folder on your Mac’s hard drive. Deleting the cache subfolder there forces Chrome to rebuild it from scratch on next launch. I’ve used this twice — both times after Chrome updates broke something that nothing else fixed.

Alternatively, you can run this path directly in Terminal if you’re comfortable with it:

That opens the Extensions directory straight in Finder. Much faster than clicking through folders.

Method 5: Use Terminal to Clear Chrome’s Entire Cache (Last Resort)

When the issue isn’t specific to one extension — when three or four of them are misbehaving after a Chrome update — this approach can save you a lot of time. It clears Chrome’s entire cache directory, which includes cached resources for all extensions.

The Service Worker/CacheStorage folder is where Chrome stores everything related to service workers — which is exactly what Manifest V3 extensions rely on. Clearing it is often more effective than anything in the Chrome UI.

How to Find Your Extension’s ID

You need this for Methods 4 and 5. Here’s where to find it:

Comparison: Which Method Works for What

How Often This Actually Happens (My Experience)

The overwhelming majority of extension issues come down to stale cache or a bad context state — not a fundamental problem with the extension. That’s why these cache-clearing methods fix things so often.

When to Try a Full Extension Reinstall Instead

Cache clearing doesn’t fix everything. If you’ve tried Methods 1 through 3 and the extension still fails, it might be a deeper issue. Reinstall when:

• The extension shows as “corrupted” in chrome://extensions
• You see the error: manifest.json is missing or unreadable
• The extension was installed from outside the Chrome Web Store and has permission errors
• You recently restored your Mac from a backup and extensions don’t match your current Chrome version
• Multiple extensions from the same developer are all failing simultaneously

Reinstalling is simple: go to chrome://extensions, click “Remove” on the broken extension, then reinstall it from the Chrome Web Store. Your settings may or may not be preserved depending on whether the extension syncs its data to your Google account.

Preventing Extension Cache Issues in the Future

A few habits that have genuinely reduced how often I deal with this:

• Restart Chrome fully after macOS updates. Just quitting the window and reopening isn’t enough. Use ⌘ + Q to quit completely, then relaunch.
• Don’t let Chrome run for weeks without a restart. Extension service workers accumulate state over time. A weekly restart clears things out naturally.
• Keep extension count reasonable. Every extension adds to Chrome’s context overhead. I keep mine under 10 active at any time.
• Watch for “suspended” service worker warnings in chrome://extensions. They show up as a yellow indicator. A suspended worker often means the context is about to break.
• Check the Chrome extension error logs regularly if you develop or depend heavily on extensions. Go to chrome://extensions, click “Errors” on any extension to see its logged errors before things break completely.

What About Chrome Profiles?

If you use multiple Chrome profiles (work, personal, etc.), extension cache is stored separately for each profile. The path I showed earlier uses “Default” — that’s your main profile. If you have additional profiles, they’re stored in folders named Profile 1, Profile 2, and so on inside the same Chrome directory.

This matters when an extension works fine in one profile but breaks in another. It’s not a Chrome-wide issue — it’s isolated to that profile’s cached data. Apply the same methods above but navigate to the correct profile folder.

The “Extension Context Invalidated” Error — Specifically

This one deserves its own mention because it’s probably the most Googled Chrome extension error. It shows up in the browser console as:

It happens when a web page’s script tries to communicate with an extension’s background context that no longer exists — usually because the extension updated or was reloaded mid-session. The page still has a reference to the old context, but that context is gone.

The fix is almost always just refreshing the tab. But if refreshing doesn’t help, reload the extension from chrome://extensions and then refresh again. The new context will be fresh and the page can establish a clean connection to it.

If the error keeps coming back on a specific site, it usually means that site’s JavaScript is holding a stale reference and not handling disconnection gracefully. That’s a bug in the website or extension, not your Mac.

Quick Reference Summary

• Start with a simple extension reload from chrome://extensions (Developer Mode on)
• If that fails, use DevTools → Application → Clear site data for targeted cache removal
• Disable and re-enable the extension if the above doesn’t immediately work
• For persistent issues, delete the extension folder from ~/Library/Application Support/Google/Chrome/Default/Extensions/
• For multiple broken extensions, clear the Service Worker CacheStorage via Terminal
• Note the extension ID first — it’s essential for file-level troubleshooting
• Restart Chrome fully (⌘ + Q) after macOS or Chrome updates
• Check chrome://extensions error logs before things get worse

Final Thoughts

Clearing Chrome extension context cache on Mac is one of those things that sounds technical but is actually pretty approachable once you know where Chrome stores stuff. Most of the time, a reload from chrome://extensions or a quick DevTools storage clear is all it takes. The Finder and Terminal methods are there for the stubborn cases, and they’re surprisingly effective.

What tripped me up the longest was not knowing the difference between clearing the context (runtime state) and clearing the cache (stored data). They’re related but different. Both matter. Now you know both.

If this fixed your issue, the one habit that’ll save you from coming back here: restart Chrome with ⌘ + Q once a week. It costs you thirty seconds and prevents most of these cache problems from ever building up.