Home › Converters › Apple Passwords to Safari
Moving passwords from Apple Passwords to Safari
Good news: there is nothing to convert. Apple Passwords and Safari write and read the identical CSV layout, so the file Apple gives you imports into Safari unchanged. The tool below will confirm your export parses cleanly and show you what's in it before you commit — but you do not need it.
Check your Apple Passwords export
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.
Why there's nothing to convert
Both use the same 6-column layout (Title, URL, Username, Password, Notes, OTPAuth) because they share the same underlying password store. A file exported from one imports into the other with no edits at all — any tool claiming to "convert" between them is reformatting a file that already fits.
| Apple Passwords column | Safari column | What happens |
|---|---|---|
Title | Title | Identical — nothing changes |
Username | Username | Identical — nothing changes |
Password | Password | Identical — nothing changes |
URL | URL | Identical — nothing changes |
OTPAuth | OTPAuth | Identical — nothing changes |
Notes | Notes | Identical — nothing changes |
What carries over
| Field | Apple | Safari | Result |
|---|---|---|---|
| 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 | Yes | Carried over |
| 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
- Open the Passwords app on macOS Sequoia or later (on older macOS: Safari → Settings → Passwords).
- Choose File → Export All Passwords… from the menu bar.
- Confirm with Touch ID or your Mac login password.
- Save Passwords.csv.
Watch out for
- Export and import are Mac-only. There is no way to do either from iPhone or iPad.
- Apple keeps TOTP codes in the OTPAuth column as full otpauth:// URIs, not bare secrets. Bare secrets will not be recognized.
Step 2 — Check the file (optional)
You can skip this. The file Apple Passwords gave you is already in the layout Safari reads, so you can go straight to step 3. If you want to be sure before importing, drop it on the tool above — it will show you how many entries it found and flag anything malformed, and hand the file back unchanged.
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 Safari
- Open the Passwords app (or Safari → Settings → Passwords on older macOS).
- Choose File → Import Passwords…
- Select the converted CSV.
Watch out for
- Safari and the Passwords app share one iCloud Keychain store and one CSV layout — importing to either lands in the same place.
- There is no folder structure in iCloud Keychain, so groups from the source have to go into notes.
Step 4 — Verify and clean up
- Open ten entries in Safari at random and check them against Apple Passwords.
- Generate a 2FA code for one account in Safari and confirm it matches Apple. A TOTP secret that imported wrong fails silently until you're locked out.
- Sign in to one real site using Safari to confirm autofill works.
- Delete both CSV files and empty your trash. If your Downloads folder syncs to iCloud, OneDrive or Dropbox, confirm the deletion propagated there too.
- Only then close your Apple Passwords account — and change any password you suspect was exposed while the plaintext file existed.
Questions
Do I need to convert anything to go from Apple Passwords to Safari?
No. Both use the same 6-column layout (Title, URL, Username, Password, Notes, OTPAuth) because they share the same underlying password store. A file exported from one imports into the other with no edits at all — any tool claiming to "convert" between them is reformatting a file that already fits. Export from Apple Passwords, then import that same file into Safari. The tool on this page is only here to check the file parses and show you what's in it.
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.
Does anything get lost moving from Apple Passwords to Safari?
Safari supports every field Apple Passwords exports, so a standard login entry survives intact — name, username, password, URL, notes, folder and 2FA secret. File attachments are the exception: no CSV export from any manager includes them, so download those separately before you close your Apple Passwords account.
Will my two-factor codes still work after the move?
Yes, as long as Apple Passwords exported the secrets. Apple Passwords and Safari store them in different shapes — one uses a bare Base32 secret, the other a full otpauth:// URI — and the converter translates between them, which is the step most manual migrations get wrong. Check a couple of codes against your old vault before you delete it, since a TOTP secret that fails to import is silent until you're locked out.
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 Safari?
Safari and the Passwords app share one iCloud Keychain store and one CSV layout — importing to either lands in the same place.
Related converters
Other routes out of Apple Passwords
- Apple Passwords → 1Password
- Apple Passwords → Bitwarden
- Apple Passwords → Dashlane
- Apple Passwords → Enpass
- Apple Passwords → Google Chrome
- Apple Passwords → KeePassXC
- Apple Passwords → Keeper
- Apple Passwords → LastPass
- Apple Passwords → Microsoft Edge
- Apple Passwords → Mozilla Firefox
- Apple Passwords → NordPass
- Apple Passwords → Proton Pass
- Apple Passwords → RoboForm
Other ways into Safari
- 1Password → Safari
- Bitwarden → Safari
- Dashlane → Safari
- Enpass → Safari
- Google Chrome → Safari
- KeePassXC → Safari
- Keeper → Safari
- LastPass → Safari
- Microsoft Edge → Safari
- Mozilla Firefox → Safari
- NordPass → Safari
- Proton Pass → Safari
- RoboForm → Safari
Moving the other way? Safari → Apple Passwords · All 210 converters