How to Remove Service Workers and Site Data in Chrome on Windows

What a service worker is — and how it gets stuck

A service worker is a script a website installs in the browser to keep working offline, show notifications and load faster on repeat visits — the technology behind installable web apps. Unlike a normal page script, it runs independently of any tab, survives restarts and intercepts the site's network requests, answering them from its own CacheStorage. That interception is the point — and the failure mode: when a site ships a bad update, the old worker may keep handing out the stale bundle forever.

The classic symptoms are recognizable at a glance: a site stuck showing last month's layout, an endless “new version available — reload” loop, a web app that insists it is offline while everything else loads fine, or disk space quietly eaten by web app data — with heavy PWA use, the Service Worker folder grows into hundreds of megabytes and beyond. Removal is safe. The site simply re-registers a worker the next time you visit, starting clean.

• chrome://serviceworker-internals — the full registry, with Unregister next to every worker
• DevTools (F12) → Application → Service workers → Unregister — while the site is open in a tab
• DevTools → Application → Storage → Clear site data — worker plus cache, cookies, IndexedDB and local storage in one click
• chrome://settings/content/all — search the site, delete its data through Site settings
• Ctrl+Shift+Del with Cookies and other site data plus Cached images and files, set to All time — mass removal

Removing a worker and its storage, step by step

Type chrome://serviceworker-internals into the address bar. The page lists every registration on this profile: origin, worker version, running status. Find the site in question — the browser's page search (Ctrl+F) helps — and click Unregister on its line; a running worker can be stopped with Stop first, though Unregister works either way. Close the site's tabs, reopen the site, and hard-reload with Ctrl+F5: with no worker in place, the page comes straight from the network.

To also clear the disk leftovers, open the site, press F12, go to the Application tab and click Clear site data under Storage — that removes the worker's cache, the site's cookies, IndexedDB and local storage in one stroke. Manual route for a whole profile: close Chrome completely (menu → Exit, since background apps can keep it alive), then delete the contents of %LOCALAPPDATA%\Google\Chrome\User Data\Default\Service Worker. Chrome recreates the folder empty, and sites re-register workers as needed.

When removal is the right fix — and keeping it from recurring

Unregister first, ask questions later, whenever a single site misbehaves in ways a normal reload does not fix. For wholesale resets — a borrowed PC, a browser handed down to a family member — the All-time clear-dialog plus a pass over Site settings removes workers and storage across the board. And keep in mind that every installed PWA brings its own worker and its own storage; the more web apps you install, the more of this data accumulates.

There is no setting that disables service workers globally, and none is needed — they are a normal part of the modern web. What helps is periodic hygiene: the occasional Clear storage on the web apps you actually use, and uninstalling PWAs you no longer open. Kleaner PRO's browser cleanup covers service-worker storage along with the usual caches, so the folder does not quietly regrow toward gigabyte size between manual passes.

Questions and Answers

Read next

All articles · FAQ