HeadwiseChrome extension
Coming soon

A header editor you don't have to trust blindly.

A Chrome extension that sets HTTP request headers per URL pattern. No network access, no analytics, site access asked one pattern at a time. Imports ModHeader profiles.

See Pro

What it does

Request header rules

Add, change or remove a request header for a URL pattern, each with its own switch, plus a global pause.

See what applies here

The popup lists the rules matching the current tab, and the badge counts them.

One-click ModHeader import

Bring your exported ModHeader profile across as it is.

Export and import

Your rules as a JSON file. That's the sync, with no server.

Profiles Pro

Keep staging and prod debug apart, switch in one click or with a shortcut.

Response headers Pro

For example, force CORS headers while testing locally.

Redirects Pro

Swap one URL for another, like prod JS for localhost.

Coming soon

Free for the core job. Pay once for more.

The core job

Free

No account, no time limit, no card.

  • Request header rules
  • See what applies here
  • One-click ModHeader import
  • Export and import

Pro, pay once

Soon

One payment. No subscription, no account. One license activates on up to 3 browsers.

  • Everything in Free
  • Profiles
  • Response headers
  • Redirects

Checkout opens when Headwise launches.

Checkout by Lemon Squeezy. Lost your key? Email us.

Privacy and permissions

Sends nothing about you

Headwise has no server and no analytics, and it can't read your traffic: Chrome applies the rules. The only request it makes is the Pro license check: when you activate a key, and at most once a week after, it sends the key to Lemon Squeezy (who sells it) to confirm it's still valid. Free use sends nothing at all.

Rules and profiles are kept in Chrome's storage for the extension. Export them as JSON any time.

What it asks Chrome for, and why

  • Site access, one pattern at a time. Asked when you add a rule, only for that rule's pattern. Nothing is granted for all sites at install.
  • Declarative net request. Chrome applies your header rules itself. The extension never reads your requests or pages.
  • Active tab. To show which rules match the tab you're on.
  • Storage. To keep your rules in the browser.

What it can’t do

  • Chrome 121 or later.
  • Chrome itself limits which headers an extension may change and how many rules it can hold.

Questions

Something else? Support has the email, lost keys and refunds.

General

Privacy

Buying