Modify request, response and CORS headers with declarativeNetRequest rules — scoped by site, saved as profiles, switched from the toolbar. One-click ModHeader import brings the rules you already have across.
Already use it? Leave a review — it takes a minute and helps more than you’d think.



01
Request, response and CORS headers — scoped by site, path or resource type. No content scripts, no per-tab injection, no flicker on load.
02
Save rule sets for dev, staging and prod, and switch them from the toolbar. The active profile is always visible on the badge.
03
Drop your ModHeader JSON export and keep working. Rules, profiles and toggles arrive intact — nothing to rewrite by hand.
04
Rules live in local extension storage. No account, no telemetry, no remote config — the store listing’s permissions are the whole story.
Export your ModHeader profiles as JSON, drop the file on the import screen, and everything arrives intact — rules, profiles, toggles, comments. Nothing to rewrite.
Older header tools ran code that had to be awake to catch each request, so the first request after an idle spell could slip through unmodified. Custom Headers registers its rules with the browser itself and they are applied at the network layer — they hold even while the extension is asleep. No dropped headers on the first request of the day.
Yes. Rules are registered with the browser itself and applied at the network layer, so they hold even while the extension is asleep.
Yes — export JSON from ModHeader and import it under Profiles. Rules, profiles and on/off states are preserved.
Chrome allows 30,000 static rules per extension and 5,000 dynamic ones; in practice you will not hit either. The UI warns you long before the browser does.