Migration

Switch from Chrome to HexVault

3 min · Export from Chrome, import to HexVault

Moving your passwords out of Chrome into HexVault takes about five minutes. Export a CSV, import it, then turn off Chrome’s built-in saving so the two don’t drift apart.

Where to import: open your HexVault vault and go to Settings → Data → Import Passwords, choose Chrome, and drop in the file you export below.

Step 1 — Export from Chrome

  • Go to chrome://password-manager/settings in Chrome.
  • Click Download file and save the .csv.
  • Works on any Chromium browser — Brave, Arc, Vivaldi — at the same URL.

Handle the export file carefully. It is unencrypted plaintext — anyone who opens it has your passwords. Keep it only as long as the import takes, then delete it and empty your trash.

Step 2 — Import into HexVault

  • Open HexVault and go to Settings → Data → Import Passwords.
  • Choose Chrome as the source.
  • Drop in the CSV file you just exported. HexVault parses it and re-encrypts every entry in your browser with your master password before anything is sent — we only ever receive ciphertext.
  • Review the preview and confirm.

Why move off the browser

A browser password store is convenient but limited: it is tied to one browser, its encryption is generally bound to your device login rather than a separate zero-knowledge master password, and it does not travel cleanly across ecosystems. A dedicated zero-knowledge manager gives you cross-browser access, breach monitoring, and a vault only you can decrypt. After importing, turn off Chrome’s Offer to save passwords so new logins land in HexVault instead.

Step 3 — After you import

  • Delete the export file and empty your trash — it is plaintext.
  • Run a security check. HexVault flags reused, weak, and breached passwords so you can fix the worst first.
  • Turn on two-factor for your HexVault account.

Import happens in your browser: your file is parsed and re-encrypted locally with your master password before anything is sent. Your key is derived with Argon2id and entries are sealed with AES-256-GCM. How the encryption works →  ·  All import sources →