Moving off ModHeader: keep your header profiles and get rid of the data collection

Denys Koval — Thu, 05 Nov 2026 12:34:57 +0000

ModHeader was removed from the Chrome Web Store in July 2026 after researchers reported a hidden data collector in the store build. Removal from the store does not uninstall it, so check chrome://extensions first.

1. Export before you remove it. In ModHeader, open the menu, choose Export → Export JSON and save the file. Then remove ModHeader.

2. Pick a replacement that cannot phone home. A header editor should not need a network connection at all. In Manifest V3 the browser applies header rules itself through declarativeNetRequest, so a well-built extension never sees your traffic. Check the store's privacy section and the permissions before you install.

3. Import. I built Headwise for this: Settings → Import and export, pick the file. Request and response headers, append mode, URL filters and resource types carry over, and it lists what it could not import.

4. Check the result. Open DevTools → Network on a page your profile covers and confirm the header is on the request.

Headwise is free, with no account, no server and no analytics: https://chromewebstore.google.com/detail/dabjjdbbccnmopoecjegmimifogmddlg?utm_source=devto. The source is on GitHub: https://github.com/KovalDenys1/headwise. Response mocks and redirects are coming as a one-time Pro.

Disclosure: I'm the author.

DEV Community: Denys Koval

Moving off ModHeader: keep your header profiles and get rid of the data collection