Move Chrome passwords to Apple Passwords without CSV surprises
Chrome and Apple Passwords both understand CSV files, but a technically valid file can still hide duplicates, blank values, malformed websites, and one-time-code edge cases. A preflight gives you a readable inventory before you make changes to your destination vault.
1. Export from Google Password Manager
On a computer, open Chrome, then Google Password Manager and Settings. Under Export passwords, download the CSV. Store it only in a temporary location you control. The file is not encrypted; anyone who opens it can see the passwords. Do not email it, put it in a shared folder, or upload it to an online converter.
2. Inspect before importing
Check that the first row contains name, url, username and password fields. Look for blank password cells, invalid website values, exact duplicates and conflicting rows that share a website and username but contain different passwords. PortaPass performs these checks on your device and lets you exclude individual rows. It never uploads the CSV.
3. Preserve Apple-specific data
PortaPass’s Apple-format export includes Title, URL, Username, Password, Notes and OTPAuth. It writes the OTPAuth column rather than silently dropping an available value, but the destination’s acceptance must still be verified. Keep the original Chrome file until you have verified the destination because not every password manager exports the same kinds of data.
4. Import and clean up
On Mac, open Passwords and choose File > Import Passwords from File. Select the converted CSV, import it, and review anything Apple could not accept. On iOS 26, Apple also exposes import under Settings > Apps > Safari > Import. After verification, delete both CSV files and empty Trash or Recently Deleted if applicable.