Move your headers to VibeHeader

Back up and inventory the current Profiles

Use ModHeader’s export action to download the Profiles as JSON. VibeHeader cannot import that file natively yet, but it gives you a reference for a manual migration—or an input you can redact before asking a coding agent to create VibeHeader import links.

{
  "v": 2,
  "n": "Staging API",
  "h": [
    [
      "X-Environment",
      "__REPLACE_LOCALLY__"
    ],
    [
      "Authorization",
      "__REPLACE_LOCALLY__"
    ]
  ],
  "f": [
    [
      "api.example.com",
      true
    ],
    [
      "^https://api\\.example\\.com/v[12]/",
      true
    ]
  ]
}

I have attached a REDACTED ModHeader JSON export. Convert every compatible Profile into a VibeHeader v2 share link.

For each Profile, build exactly this payload:
{
  "v": 2,
  "n": "Profile name",
  "h": [["Header-Name", "value"]],
  "f": [["request filter expression", true]]
}

Rules:
- h: include enabled request headers only. Preserve names, values, order, and placeholders exactly.
- f: include supported Request URL filters only. Preserve each expression and enabled boolean.
- Create one payload and one link per Profile.
- Build each link with:
  "https://www.vibeheader.com/s#c=" + encodeURIComponent(JSON.stringify(payload))
- Do not convert response headers, cookies, CSP, redirects, Exclude URL filters, tab or tab-domain filters, window filters, or resource-type filters.
- Do not guess or invent an equivalent for unsupported rules.
- Do not change or reconstruct any redacted value.

Output:
1. One complete VibeHeader link per compatible Profile.
2. A "Not converted" list naming every skipped rule and why it was skipped.

Recreate each project or environment as a Profile

Create names that make the active scope obvious—such as Local Debug, Staging API, or Checkout QA. Profiles keep their own headers and Request Filters, and more than one can be active at the same time.

Copy the enabled request headers

Add each request header to its matching Profile and preserve the enabled state. Work from one Profile at a time so similarly named environments do not inherit the wrong token or flag.

Sensitive value? Keep it local, avoid screenshots, and rotate it if it may have been exposed through an old extension or shared link.

Rebuild and test the Request URL scope

VibeHeader Filters match the target URL of each supported request—not simply the page in the address bar. Choose the simplest expression that describes the intended traffic, then test a real API or asset URL before relying on it.

Share the finished Profile—not a list of setup steps

A VibeHeader link can include one Profile’s suggested name, enabled valid headers, and valid Request Filters. The recipient previews the setup before importing it as a new Profile.

Verify the request, then test the boundary

Do not stop at a positive match.A negative test catches filters that are broader than the original ModHeader scope.

Remove ModHeader only after the checklist passes

Keep ModHeader until every supported Profile has passed both positive and negative tests. If you used the version Google flagged as malware (v7.0.18), follow the cleanup and self-check guide to remove leftover storage and rotate secrets that may have been exposed.