Import from BitBrowser

Frenz Browser ships a one-click migrator for BitBrowser users. It pulls every profile, every cookie, and every proxy in a single pass — typically under 10 minutes for 400 profiles.

What gets migrated

• Profile name, group, tags, notes
• OS / device class (re-mapped to Frenz's internal device classes)
• Proxies (deduplicated — one Frenz proxy entry per unique host:port across all imported profiles)
• Cookies — full session continuity for cookie-based logins

What doesn't migrate

• localStorage and IndexedDB (BitBrowser's API doesn't expose these). Sites that store your auth token in localStorage will need a fresh login. Cookie-based logins (the majority) survive.
• Per-profile canvas seed — Frenz generates a fresh, coherent fingerprint targeting the same device class. Cookies are what preserve sessions; the canvas hash doesn't matter for being logged in.
• Firefox profiles — Frenz v1 is Chromium-only. Firefox engine ships in v1.5.

Steps

1. Make sure BitBrowser is running on your machine.
2. Find your BitBrowser API token: BitBrowser → Settings → API → copy.
3. In Frenz Browser, open the Importer tab in the sidebar.
4. Paste the token. Click Test connection — should report "BitBrowser reachable (vX.Y.Z)".
5. Click Load profiles. You'll see a table of every BitBrowser profile with the proposed Frenz name, OS detection, proxy presence, and any warnings.
6. Tick the ones you want to import (or use "Select all" / "Skip name collisions").
7. Click Import N profiles.
8. The summary card shows imported / skipped / failed counts plus a per-item warning log for anything that needs attention.

Verifying the import worked

The fastest sanity check: pick a profile that was logged in to a site (Amazon KDP works well), launch it in Frenz, navigate to that site — you should land on the logged-in page without re-authenticating.