One-click browser data cleaner for developers.
Sweep away cookies, localStorage, sessionStorage, IndexedDB, and CacheStorage — instantly.
As developers, we constantly deal with stale cached data during development. Manually going to DevTools → Application → Clear Storage every single time is tedious and breaks your flow.
CacheFlux gives you a single-click broom icon in your toolbar that instantly wipes all site data for your active tab — so you can focus on building, not cleaning.
- 🖱️ One-Click Clean: Click the broom icon → clears all selected site data for the active tab instantly.
- ⚙️ Granular Cleanup Settings: Choose exactly what data categories to wipe (Cookies, LocalStorage, SessionStorage, CacheStorage, IndexedDB) in the Options page.
- 🔄 Automatic Tab Reload: Toggle automatic tab refreshing in settings to immediately apply cleanup changes.
- 🛡️ Exception List: Protect specific keys (e.g.,
auth_token,theme) from being deleted during standard cleanups. - 💥 Force Clean: Right-click the extension icon → "Force Clean" ignores all exceptions and clears all selected storage categories.
- 🟢 Visual Feedback: A beautiful page-injected toast notification shows a real-time progress wheel and cycles through cleaning stages.
- 🔒 Privacy First: Works strictly on the active tab's domain and parent domains. No tracking, no external data storage.
- ✅
localStorage - ✅
sessionStorage - ✅
Cookies(including HttpOnly via Chrome API) - ✅
IndexedDBdatabases - ✅
CacheStorage(Service Worker caches)
Installing from the official stores is the easiest way to get CacheFlux and ensure it stays updated automatically.
⚠️ Chrome, Edge, Opera versions on the way — review in progress
- 🦊 Firefox: Download from Firefox Add-ons
If you want to test the latest features or contribute to the project, you can install the extension manually.
git clone https://github.com/albertolicea00/CacheFlux.gitBefore loading the extension, switch to the appropriate manifest version for your target browser:
- For Google Chrome / Chromium (Manifest V3):
make chrome
- For Mozilla Firefox (Manifest V2):
make firefox
This copies the correct manifest template to the ignored manifest.json file.
- 🌐 Open your browser and go to
chrome://extensions/(oredge://extensions/). - 🔓 Enable "Developer mode" in the top right corner.
- 📂 Click "Load unpacked" and select the extension folder.
- 🦊 Open Firefox and go to
about:debugging#/runtime/this-firefox. - 📂 Click "Load Temporary Add-on...".
- 📄 Select the
manifest.jsonfile in the extension folder.
If you need to generate the production .zip files locally for manual distribution or testing, you can run:
make buildThis reads the current version from manifest.v3.json and creates a dist/[VERSION]/ directory containing the cache-flux-manifest-v3.zip and cache-flux-manifest-v2.zip packages. You can clean this up at any time with make clean.
Simply left-click the 🧹 broom icon on the toolbar.
- Clears all site data for the current tab
- Respects your configured exceptions
- Shows a toast notification listing the cleared items after a brief progress animation
- Right-click the extension icon → Options
- Add the exact key names you want to protect (e.g.,
auth_token,user_preferences) - These keys will be preserved during standard cleans
- Right-click the extension icon
- Select "Force Clean (Ignore Exceptions)"
- This will delete everything regardless of exceptions
- Shows a "Force Clean Completed" toast notification listing the cleared items
CacheFlux/
├── manifest.json # Extension config (Manifest V3)
├── background.js # Service Worker — handles click, context menu & cleanup logic
├── options.html # Settings UI — manage exception keys
├── options.js # Options page logic — save/load exceptions via chrome.storage
├── icons/ # Extension icons (16, 32, 48, 64, 128)
│ ├── icon16.png
│ ├── icon32.png
│ ├── icon48.png
│ ├── icon64.png
│ └── icon128.png
├── LICENSE # MIT License
└── README.md # You are here!
| Permission | Why it's needed |
|---|---|
activeTab |
Access the currently active tab to run cleanup scripts |
scripting |
Inject cleanup code into the page context |
cookies |
Delete HttpOnly cookies that JavaScript can't access |
storage |
Persist your exceptions list and cleanup configurations |
contextMenus |
Add the "Force Clean" context menu item to the icon |
<all_urls> |
Required by Chrome Cookies API to match active tab site URL |
⚠️ No data is ever collected, transmitted, or stored externally. Everything runs locally in your browser.
This project uses fully automated GitHub Actions to package and publish the extension to Chrome, Edge, Firefox, and Opera.
To trigger a new release, you must create and push a version tag. The CI/CD pipeline is configured to only build and generate the .zip packages when a tag is pushed. It will not generate zips on regular pushes to main.
To automatically read the version from manifest.v3.json, create a tag, and push a new version:
- Bump the
"version"field in bothmanifest.v3.jsonandmanifest.v2.json. - Commit your changes.
- Run the publish command:
make publishThis command automatically runs git tag v[VERSION] and git push origin v[VERSION] for you.
Once pushed, GitHub Actions will automatically:
- Build the
.zipfiles for Chrome/Edge/Opera (Manifest V3) and Firefox (Manifest V2). - Create a GitHub Release with the
.zipfiles attached. - Upload and publish the extension to all supported browser stores.
Contributions are welcome! Please read the CONTRIBUTING.md guide before submitting a pull request or opening an issue.
This project is licensed under the MIT License — see the LICENSE file for details.
Alberto Licea — @albertolicea00
Made with ❤️ for developers who are tired of clearing cache manually.