modheader-export-backup

Export your ModHeader profiles without ModHeader.

npx @requestly/modheader-export-backup

Overview

ModHeader was pulled from the Chrome Web Store and Edge Add-ons in mid-2026, so its Export → Download JSON button is out of reach — you can't export from an extension you can't open.

Your profiles are still sitting in your browser profile on disk. This CLI reads them and writes the exact same export file ModHeader would have, which Requestly imports directly.

How to export

1. Run it

npx @requestly/modheader-export-backup

Needs Node.js 20 or newer. Nothing is installed permanently, and you can leave your browser open — nothing is written to your browser profile.

2. Pick a browser profile

It lists every browser profile on your machine that has ModHeader data. Move with the arrow keys and press enter.

Found 2 ModHeader backups. Which one?

  BROWSER  BROWSER PROFILE  MODHEADER PROFILES IN IT
❯ chrome   Testing          2 profiles: Profile 1, Profile 2
  edge     Person 2         1 profile: Profile 1
  Quit

up/down move · enter select · esc cancel

One row per browser profile: which browser, which of that browser's profiles, and what ModHeader has stored in it.

3. Choose where to save it

Press enter for ~/Downloads, or type another folder.

Export to [/Users/you/Downloads]

It writes modheader-<browser>-<profile>.json and returns to the list with that row marked ✓ exported, so you can repeat steps 2–3 for your other profiles. Choose Done when you have them all.

4. Import into Requestly (optional)

Your profiles are safely exported at this point — that file is yours to keep, or to import wherever you like.

If you're looking for an alternative to ModHeader, Requestly imports these files directly:

app.requestly.io/import-from-modheader

Each ModHeader profile becomes a Requestly group, carrying its request and response headers, cookie and CSP headers, redirects, and URL filters.

Browsers supported

• Chrome — stable, Beta, Dev, Canary
• Chromium
• Edge
• Brave
• Vivaldi
• Opera
• Arc
• Dia

All user profiles of each are scanned, and sideloaded or unpacked copies of ModHeader are picked up too.

Firefox is not supported — it stores extension data in a completely different format.

Nothing found?

• Run it with --list to see every store that was detected.
• If your browser runs with a custom profile location, point at it with --user-data-dir <path>.
• If ModHeader was fully uninstalled a while ago, your browser may have already deleted its storage — in which case there is nothing left to recover.

Scripting it

export does the same thing without prompting, and takes --browser, --profile, --output and friends. Run --help for the full list.

npx @requestly/modheader-export-backup export --browser chrome --profile Testing --output modheader.json

Your exported data

Exported files contain whatever your ModHeader profiles contained, which often means Authorization headers and session cookies. Treat them like credentials, and don't commit them anywhere.

Development

npm install
npm start          # the interactive CLI
npm test           # end-to-end test against the real extension

License

MIT