Modern web applications like Twitter, Spotify, and Gmail use a background browser technology called a “Service Worker.” This script sits between Google Chrome and the internet, intercepting network requests and caching heavy assets (like images and Javascript) directly on your hard drive. This is what allows these web apps to load instantly and even function offline.
However, if a website developer pushes a bad update, the Service Worker can cache a broken version of the site. Even if you hold Shift and click Refresh, or manually clear your standard browser cache, the website will remain completely broken because the Service Worker intercepts the refresh command and continues feeding Chrome the broken offline files. To fix this, you must bypass the standard settings and forcefully unregister the specific Service Worker.
How to Safely Delete a Chrome Service Worker Cache
You must use the Chrome Developer Tools panel to manually unregister the background script.
- Open the Google Chrome browser and navigate to the website that is broken (e.g., twitter.com).
- Right-click anywhere on the blank webpage and select Inspect (or press F12 on your keyboard). This opens the Developer Tools panel.
- Look at the top menu bar of the Developer Tools panel. You will see tabs like Elements, Console, and Sources. Click on the Application tab. (If you do not see it, click the
>>arrow icon to reveal hidden tabs). - In the left-hand sidebar of the Application tab, look under the “Application” header and click on Service Workers.
- In the main panel, you will see a green dot indicating that a Service Worker is actively running for this specific website.
- Click the blue Unregister button located to the right of the active script.
- Next, look at the left sidebar again. Under the “Application” header, click on Storage.
- Scroll down to the bottom of the main panel and click the Clear site data button.
Close the Developer Tools panel and press F5 to refresh the webpage. Because the rogue Service Worker and its offline cache have been completely obliterated, Chrome is forced to fetch a brand-new, pristine version of the web application directly from the internet, instantly resolving the broken layout.