TLDR: I’ll show you simple, browser-specific ways to clear cached files for one website — not your whole browser. You’ll learn quick tricks (hard refresh, dev tools), how to remove site data and unregister service workers, and what to avoid so you don’t lose logins or settings. These steps work in Chrome, Edge, Firefox, Safari, Brave and mobile browsers.
When I first updated a live site and saw stale images and CSS in front of my eyes, I felt that sinking feeling every web maker knows. I refreshed, I hard-refreshed, I even rebooted my machine — and the old styles stubbornly persisted. That forced me to learn how to clear cache for a single website in each browser, so I wouldn’t have to nuke cookies, saved passwords, or other sites’ caches again. I want to share that exact process with you so you can test changes safely and troubleshoot without collateral damage.
How to clear cache for one site: the complete approach
Clearing cache for a single website is about removing only the stored files for that origin: HTML, CSS, JS, images, cookies, localStorage and service workers. That keeps everything else intact and avoids the friction of logging back into every site. Let’s break it down by what it is, why it matters, how to do it in each major browser, and what you should avoid.
What is clearing cache for a single website?
Think of your browser cache as a tiny library of resources saved to speed up repeat visits. When you clear cache for a single site, you tell the browser to remove only the files associated with that domain. You can remove:
- Cached images, scripts, and stylesheets
- Cookies and site data
- localStorage and sessionStorage
- Service workers and application caches
Doing this selectively lets you refresh the site content without affecting your other tabs and accounts.
Why does clearing a single site’s cache matter?
As you know, caching improves page load time and reduces bandwidth. However, when you deploy updates, old cached files can cause layout shifts, broken features, or stale content. Clearing a single site’s cache matters because:
- It verifies your changes quickly without full-browser reset
- It preserves sessions and passwords on other sites
- It isolates debugging to the affected origin (great for developers and site owners)
For example, when you tweak styles to improve Core Web Vitals like LCP, you want to see the real effect immediately rather than waiting for other users’ caches to expire. If you run WordPress, you may still need to clear server or plugin caches too; developers often combine browser steps with plugin purge steps such as clear WordPress cache when debugging page speed issues.
How do you clear cache for a single website: browser-by-browser
I’ll walk through the most reliable methods: site settings, developer tools, and service worker removal. Use the method that fits your comfort level.
Google Chrome (Windows, macOS, Linux)
Chrome gives you several options. For a quick check use a hard refresh; for a complete site purge use the Application panel in DevTools.
- Hard refresh: Open the page, then press Ctrl+F5 (Windows) or Shift+Command+R (macOS). This reloads resources bypassing cache but may not remove stored site data.
- Clear site data via padlock: Click the padlock in the address bar → Site settings → Clear data. This removes cookies and site data for the origin only.
- DevTools full purge: Right-click the page → Inspect (or Ctrl+Shift+I). Go to Application → Storage → Clear site data. You can also check Disable cache while DevTools is open, then reload to force fresh fetches.
- Service workers: In DevTools Application → Service Workers, click Unregister to remove active workers that can serve cached responses.
Use DevTools when you want a surgical, developer-friendly purge. If you’re troubleshooting a staging bug after a CSS update, I often disable cache while DevTools is open and test every page load until I confirm the fix has propagated.
Microsoft Edge
Edge mirrors Chrome’s engine, so steps are very similar.
- Padlock → Cookies and site permissions → Manage and delete cookies and site data for that site.
- DevTools → Application → Clear storage → Clear site data removes cache plus localStorage and IndexedDB for the origin.
- Unregister service workers if a Progressive Web App behaves oddly.
Mozilla Firefox
Firefox gives you friendly UI to remove data per site and developer tools for deeper control.
- Padlock icon → Clear Cookies and Site Data removes cookies and cached files for the domain.
- From the menu: Tools → Web Developer → Storage Inspector. Select the domain and click Delete All to clear cache, IndexedDB, localStorage and cookies for that site.
- If you see content stubbornly returning, check the Service Workers section in about:debugging#/runtime/this-firefox and unregister the worker.
When I was troubleshooting a site that used an aggressive service worker, unregistering it in Firefox solved a problem that a simple refresh didn’t fix.
Safari (macOS and iOS)
Safari doesn’t expose as many developer options by default but you can target a single site.
- Manage Website Data: Safari → Preferences → Privacy → Manage Website Data… Search the domain and Remove to purge cookies and cache for that site.
- On macOS enable Develop menu (Safari → Preferences → Advanced → Show Develop menu). Use Develop → Empty Caches to clear caches globally, but for a single site prefer Manage Website Data or the Web Inspector (Develop → Show Web Inspector → Resources tab) to inspect and remove storage.
- On iOS: Settings → Safari → Advanced → Website Data, find the domain and swipe to delete.
Brave and Opera
Both are Chromium-based so follow Chrome steps: padlock → site settings, or DevTools → Application → Clear storage. Brave’s Shields can cause apparent caching too, so briefly disable Shields when testing to isolate cache issues.
Mobile browsers (Chrome on Android, Safari on iOS)
Mobile browsers limit granularity but still allow origin-specific deletes:
- Chrome Android: Tap padlock → Site settings → Clear and reset. Or use Chrome settings → Site settings → All sites → choose origin → Clear and reset.
- Safari iOS: Settings → Safari → Advanced → Website Data → search and delete domain data.
Other useful techniques (for developers)
- Disable cache in DevTools while testing to force every resource to fetch anew.
- Use query string versioning (cache busting): append ?v=1.2 to assets to force a new fetch.
- Set cache-control headers appropriately on the server to limit how long browsers store files during development.
- Test in an incognito/private window to see a fresh session without stored cookies or cache.
What should you avoid?
There are common mistakes that cause more pain than the cache problem you were trying to fix.
- Don’t clear your entire browser data unless you have to — you’ll lose saved passwords and sign-ins across all sites.
- Avoid telling non-technical users to “clear the whole cache” as a first step; guide them to site-specific steps instead.
- Don’t assume a hard refresh clears service workers; they can keep serving cached responses until unregistered.
- When troubleshooting performance, also check server and CDN caches. For example, if you’ve optimized images or followed advice to improve LCP WordPress, browser cache may still show old assets until you purge CDN or plugin caches.
How to verify the cache is actually cleared
After you clear site data, do these checks:
- Open DevTools Network tab and reload; look for 200 (not 304) responses and Fresh/From Network indicators.
- Check Resources/Storage panels to confirm cookies, IndexedDB and localStorage are gone.
- If your site uses client-side caching or a CMS cache plugin, combine browser steps with server-side cache purges. I often follow a local browser purge with a plugin purge when trying to purge cache WordPress to ensure both layers are clear.
What else should you avoid when fixing site issues?
Beware of ad-hoc changes that mask problems. If your site loads stale content only for some users, test across browsers and networks. If clearing site cache fixes it for you but not others, a CDN or upstream cache likely needs purging. If performance is the reason you’re clearing cache, remember that poorly configured caching headers can harm metrics and you may need to address server settings rather than rely on client-side fixes.
Frequently Asked Questions
Will clearing a single site’s cache log me out?
It depends. Clearing only cached files (images, CSS, JS) usually won’t log you out, but removing cookies and site data will. When you use DevTools → Clear site data, expect cookies and local session data to be removed. If you want to keep your login, use Disable cache in DevTools and hard refresh instead of deleting cookies.
Why is content still old after I cleared cache?
Several causes are possible: an active service worker serving cached responses, CDN or server-side cache that hasn’t been purged, or aggressive cache headers on static assets. Unregister service workers, purge CDN caches, and check your server cache plugin. If you run a WordPress site and the site still shows old files after a browser purge, also purge your plugin cache to fully resolve issues like a fix slow WordPress site.
Is there a way to clear cache programmatically for users?
You can’t force a browser-wide clear for users, but you can control asset versioning (cache-busting query strings or filenames) and set appropriate cache-control headers so browsers fetch fresh versions when you deploy. For critical updates, increment file names or use a build tool that outputs hashed filenames.
How do I handle stubborn service worker cache?
Unregister the service worker from DevTools Application panel. Also implement a lifecycle strategy in your service worker that detects new versions and self-updates, then clears old caches. During development, I frequently unregister service workers manually before testing major client-side changes.
To summarize
Clearing cache for a single website is a small, precise action that saves you from broad resets and lost credentials. Use the padlock site settings for quick deletes, DevTools Application → Clear site data for a full origin purge, and unregister service workers when you suspect offline caches. Combine browser steps with server/CDN cache purges and versioned assets for reliable deployments. If you build or maintain WordPress sites, remember to purge plugin or server caches as part of this flow — I’ve done that many times to finally see performance improvements after I tried to improve LCP WordPress.