Exported Passwords from Chrome or Opera? Here's How to Remove Duplicates Before Importing

You exported your passwords. Now you have 700 rows when you expected maybe 200.

Browser password managers save credentials per URL — not per site. So if you've logged into Google via /signin/v2/challenge/pwd, /v3/signin/identifier, /AddSession, and three other paths, you have six Google entries. Same credentials, six rows. Multiply that across every site you've ever logged into and you end up with a bloated, repetitive file before you've imported a single password.

If you import it as-is, you'll carry all of that into your new password manager. Most handle it fine, but your vault ends up cluttered with dozens of near-identical entries that are annoying to manage and hard to audit.

Cleaning it first is worth 5 minutes.

What you're dealing with

Browser exports save a new row every time you authenticate via a new URL path. This means the same site — same username, same password — can appear 10, 20, or 30 times in your export, just with slightly different URLs.

The duplicate types you'll find:

• Same site, same credentials, different URL paths — the most common. Google, Facebook, and any site with complex login flows are the worst offenders.
• Same site, different usernames — two accounts on the same platform (personal and work, for example). These are real separate entries and should be kept.
• http vs https versions of the same URL — technically different, practically identical.
• Mobile app entries — apps saved as android://... or ios-app://... alongside the web version.

How to clean it up

Step 1. Export your passwords.

• Chrome: Settings → Passwords → click the ⋮ menu → Export passwords → save as CSV
• Opera: Settings → Advanced → Autofill → Passwords → click the ⋮ menu → Export passwords → save as CSV
• Edge / Brave / Vivaldi: same path as Chrome, same format

Step 2. Upload the file to Clean by Similarity API.

Step 3. Select your matching columns carefully.

This is the important part. Select:

• Name — fuzzy match (catches google.com and accounts.google.com)
• Username — include
• Password — include

Do not include the URL column. URL is the field causing the problem — matching on it will prevent the tool from grouping entries that belong together.

Step 4. Review the clusters.

The cluster view groups entries the tool thinks are duplicates. Check that the username and password match before accepting — if two entries have the same site name but different credentials, they're separate accounts and should both be kept.

Step 5. Download the deduplicated file and import it into your password manager.

Most password managers accept the standard Chrome export format directly:

• Bitwarden: Tools → Import → Chrome CSV
• 1Password: File → Import → Chrome
• Dashlane, NordPass, Keeper: check their import docs for the correct format

A note on data safety

You're uploading a file containing every password you own. That is worth thinking about before using any tool.

Clean processes your file entirely in your browser. Nothing is uploaded to a server, nothing is stored, and the file is cleared from memory as soon as your session ends. You can verify this in the privacy policy.

If you're not comfortable uploading the file at all, the manual approach is to open it in Excel or Google Sheets and use Remove Duplicates on the Name + Username + Password columns. That handles exact duplicates only — it won't catch google.com vs accounts.google.com — but it removes the most obvious clutter.

Free for most exports

Most browser exports are under 500 rows, which means deduplication is completely free — no account needed.

Clean up your password export →

FAQ