CacheBuster — Dev Cache Control

Per-site cache control for developers. Force revalidation, strip ETags, version-bust asset requests, and clear cache in one click.

Stop debugging a stale asset. CacheBuster gives you per-site control over browser caching while you develop. Turn it on for localhost, a staging host, or a preview branch — and it does nothing at all on every other site you visit. WHAT IT DOES Enable CacheBuster for a host and, on that host only: - Requests go out with no-cache and no-store, and conditional headers (If-None-Match, If-Modified-Since) are removed, so your server cannot answer with 304 Not Modified. - Responses come back with ETag, Last-Modified and Expires stripped and Cache-Control rewritten, so nothing is written into the HTTP cache for the next load. - fetch() and XMLHttpRequest asset requests can carry a ?_cb= version key, which defeats edge and proxy caches that ignore request headers. You choose whether that applies to .js, .css, both, or every request. - One button clears the HTTP cache and Cache Storage for the current origin and hard reloads the tab. BUILT TO STAY OUT OF YOUR DEV SERVER'S WAY Cache busting that rewrites the wrong URL breaks modern development servers. CacheBuster never rewrites a module URL, so it cannot cause a library to be loaded twice or a code-split bundle to fail. It also leaves these alone: - the internal paths a build tool serves its own runtime and generated assets from - hot-reload payloads, and the requests that deliver them - chunk manifests and router data requests - pre-signed asset URLs, where adding a query parameter would invalidate the signature HOW IT WORKS 1. Open the site you're developing. 2. Click the CacheBuster icon and flip the switch for that host. 3. The toolbar badge reads ON whenever you're on a site it's active for. 4. Use Manage Sites to see every host you've enabled, or pause everything from the header without losing your settings. WHO IT'S FOR Front-end and full-stack developers, QA engineers, and anyone who has reloaded six times wondering why a CSS change refuses to appear. It is a development tool, and it is designed to be enabled only on hosts you are working on.