Movepasswords

Home › Converters › Apple Passwords to Google Chrome

Apple Passwords to Google Chrome converter

Apple Passwords and Google Chrome both use CSV, but Apple Passwords writes 6 columns; Google Chrome expects 5 in a different order — so Chrome rejects a raw Apple export or silently files everything into the wrong fields. Drop your export below and get back a file Chrome accepts.

Convert your Apple Passwords export

Drop your Apple Passwords CSV here or click to choose a file — nothing is uploaded

The conversion runs entirely in this tab using JavaScript. Your file is never sent to a server — you can confirm it by opening your browser's Network tab, or by turning off Wi-Fi before you drop the file in. Prefer not to do this in a browser tab at all? Download the converter and run it from your own disk.

Your export file is plaintext. Both the file Apple Passwords gives you and the one you download here contain every password in readable form. Delete them as soon as the import is verified, and empty your trash.

What's actually different between the two formats

Only 3 of 6 column names match (url, username, password), and they're in a different order — enough for Chrome to accept the file and then put your passwords in the wrong fields.

Apple Passwords columnGoogle Chrome columnWhat happens
Title name Renamed and repositioned
Username username Renamed and repositioned
Password password Renamed and repositioned
URL url Renamed and repositioned
OTPAuth — none — Chrome has no 2fa secret field. Written into notes instead of dropped.
Notes note Renamed and repositioned

What carries over

FieldAppleChromeResult
Item name / title Yes Yes Carried over
Username and password Yes Yes Carried over
Website URL Yes Yes Carried over
Notes Yes Yes Carried over
Folders / groups No No Not in the source file
Two-factor (TOTP) secrets Yes No Written into notes. Re-add them by hand, or keep them in a separate authenticator.
Favorites No No Not in the source file
Custom fields No No Not in the source file
Multiple URLs per entry No No Not in the source file
File attachments No No Not in the source file

Step 1 — Export from Apple Passwords

  1. Open the Passwords app on macOS Sequoia or later (on older macOS: Safari → Settings → Passwords).
  2. Choose File → Export All Passwords… from the menu bar.
  3. Confirm with Touch ID or your Mac login password.
  4. Save Passwords.csv.

Watch out for

Step 2 — Convert it

Drop the file onto the converter above. It parses Apple Passwords's layout, maps each field onto the universal record, then writes Google Chrome's exact expected columns — including the empty ones its importer requires and, where the two differ, the right shape for 2FA secrets. You'll see a preview and a list of anything Chrome can't hold before you download.

Rather not put this file in a browser tab connected to the internet? The same converter is available as a single HTML file you can download and open with your network switched off.

Step 3 — Import into Google Chrome

  1. Go to chrome://password-manager/settings in Chrome.
  2. Select "Select file" next to Import passwords.
  3. Choose the converted CSV and confirm.

Watch out for

Step 4 — Verify and clean up

  1. Open ten entries in Google Chrome at random and check them against Apple Passwords.
  2. Sign in to one real site using Google Chrome to confirm autofill works.
  3. Delete both CSV files and empty your trash. If your Downloads folder syncs to iCloud, OneDrive or Dropbox, confirm the deletion propagated there too.
  4. Only then close your Apple Passwords account — and change any password you suspect was exposed while the plaintext file existed.

Questions

Why won't Google Chrome import my Apple Passwords file directly?

Only 3 of 6 column names match (url, username, password), and they're in a different order — enough for Chrome to accept the file and then put your passwords in the wrong fields. The converter rewrites the file into Google Chrome's exact expected layout, including the column order and any empty columns its importer requires.

Do my passwords get uploaded anywhere?

No. The conversion is JavaScript running in your own browser tab — the file is read with the FileReader API, transformed in memory, and handed back to you as a download. There is no upload, no server-side processing and no analytics attached to the file. You can verify this by disconnecting from the internet before you drop the file in: the conversion still works.

What gets lost moving from Apple Passwords to Google Chrome?

Google Chrome can't natively store: two-factor (totp) secrets. Rather than drop that data, the converter writes it into the notes field where Chrome has one, so you can move it back by hand. Keep your Apple Passwords account active until you've confirmed everything you need made it across.

Can I keep my 2FA codes in Google Chrome?

No — Google Chrome has no field for TOTP secrets at all. The converter puts each secret into the entry's note so it isn't lost, but Chrome won't generate codes from it. Move those to a dedicated authenticator app before you shut down Apple Passwords, or pick a target that supports them.

Is the export file from Apple Passwords encrypted?

No. An Apple Passwords CSV export is plaintext — every password in it is readable by anything that can open the file, including other apps on your machine and anything that syncs your Downloads folder to the cloud. Convert it, import it, then delete both files and empty your trash. If your Downloads folder syncs to iCloud, OneDrive or Dropbox, check that the deletion propagated.

Anything unusual about Apple Passwords's export?

Export and import are Mac-only. There is no way to do either from iPhone or iPad.

Anything unusual about importing into Google Chrome?

Chrome stores no TOTP secrets, no folders and no favorites. Anything in those fields has to go into the note column or be lost.

Related converters

Other routes out of Apple Passwords

Other ways into Google Chrome

Moving the other way? Google Chrome → Apple Passwords · All 210 converters