Moving off Chrome’s built-in password save is straightforward if you export a CSV, import into AzAd Vault, spot-check critical logins, then stop saving new passwords only in the browser. This walkthrough covers Android, Windows, and the Chrome extension without drama.
Export from Chrome
In Chrome’s password settings, use the export passwords action (wording varies by OS). Chrome will ask for your OS user password or equivalent confirmation, then produce a CSV. Treat that file as sensitive: it is typically plaintext. Store it briefly on an encrypted disk, import promptly, then delete the CSV from Downloads and Recycle Bin.
Edge and Firefox have similar CSV export flows if you are consolidating browsers. AzAd Vault on Android and Windows also accepts other formats (Bitwarden JSON including encrypted, LastPass CSV, and more). The Chrome extension focuses on CSV and Bitwarden imports.
Import into AzAd Vault
Android / Windows: open the import hub or settings import entry, choose Chrome/CSV, select the file, and confirm. Large vaults may take a moment — wait for completion before quitting.
Chrome extension: use Settings → Vault import, pick CSV or Bitwarden JSON, and restore
into the encrypted local vault. You can also restore from an encrypted .azvault backup on
first run if you already exported from another AzAd Vault install.
Free allows up to 500 items. If Chrome export exceeds that, import the highest-value accounts first or upgrade to Premium via Google Play for unlimited items. Labels and TOTP caps (20 / 10 on Free) also apply.
Verify, then change Chrome behavior
Unlock AzAd Vault and open a few important sites. Confirm usernames and passwords. Add TOTP where you still relied on SMS. Turn off Chrome’s “offer to save passwords” if you want a single source of truth, or leave it on temporarily during transition — just avoid divergent edits.
Enable optional Drive ciphertext sync after a successful encrypted backup. Read extension vs built-in and vault vs browser storage for the “why.”
Cleanup checklist
Delete plaintext CSVs. Confirm Google Account password manager entries if you want them cleared later. Store recovery codes in vault notes. Practice unlocking on a second device. If import counts look wrong, re-export and try again rather than merging blindly.
Import is a one-time project that pays off every week you do not reuse passwords. Chrome export plus AzAd Vault import is the shortest path for most Chromium users on Android, Windows, and the extension.
Handling duplicates and messy titles
Browser exports often include obsolete entries, localhost experiments, and duplicate hostnames. After import, sort or search inside AzAd Vault and archive or delete junk so the 500 Free item cap stays meaningful. Prefer clean data over importing every historical typo.
If a site changed domains, keep the working URL you actually use. Update usernames that still point at old email addresses while you are in cleanup mode — migration is a perfect moment for hygiene.
Windows import hub extras
Windows builds include a broader import hub (browser export discovery and additional formats). Use it when consolidating Edge or Firefox alongside Chrome. Android mirrors major CSV/JSON paths. The Chrome extension covers CSV and Bitwarden for in-browser migrations.
After import: sync and backup order
Recommended order: import → spot-check → encrypted local backup → optional Drive sync → disable redundant browser save if desired. Reversing that order can sync half-imported state or leave plaintext CSVs lingering. Delete exports only after you confirm unlock on a second device or at least a re-import test.
Stuck? Note your app version and email support@azadvault.com. Do not attach the CSV to the ticket.
Edge and Firefox neighbors
If your household split browsers, export each CSV separately and import in turn. Deduplicate afterward. Bitwarden JSON is ideal if you already consolidated there. AzAd Vault does not use an “AzAd Safe JSON” format — stick to documented CSV, Bitwarden, and related imports listed in the FAQ.
After success, celebrate lightly: you now have unique-password infrastructure. Spend the saved anxiety on enabling TOTP for email. That single follow-up outperforms tweaking themes.
Label strategy after import
Create a few labels such as Banking, Work, and Shopping to restore scanability. Free allows 20 labels — enough for structure without taxonomy theater. Attach TOTP where missing while you review each label group.
When Free TOTP slots fill, either upgrade Premium or keep a secondary authenticator for low-value sites. Crown-jewel TOTP belongs in the vault first.
AzAd Vault keeps the same zero-knowledge posture whether you are on Free or Premium: Argon2id and AES-256-GCM on device, optional Google Drive ciphertext sync, and no multi-vault sharing model. Premium via Google Play raises limits and unlocks Chrome passkeys, Archive, and family seats — it does not invent a separate “priority sync” cryptography track. Android does not ship WebAuthn passkey create/sign-in as of September 2026; use Chrome Premium for passkeys. For algorithms and product boundaries, see the security overview and glossary.