Move Apple Passwords to Chrome safely
The core login fields move cleanly when their headers and values are valid. The two details most likely to catch people out are Google’s 3,000-row limit and Apple’s OTPAuth column, which Google’s password CSV does not import.
1. Make a temporary Apple export
On iOS 26, open Settings > Apps > Safari, tap Export below History and Website Data, select Passwords only, then save the file to Downloads. On Mac, use the Passwords app export command. Apple warns that the resulting file is readable plain text, so use a private temporary location.
2. Keep one-time codes accounted for
Apple exports may include OTPAuth values used for verification codes. The Google password CSV expects website, username and password fields and does not document OTPAuth as an import field. PortaPass flags how many one-time-code values will not be included in a Google file. Keep the original Apple export and confirm those accounts separately rather than assuming the codes moved.
3. Stay below 3,000 rows per import
Google currently allows 3,000 passwords in one import and up to 10,000 stored passwords in an account. If your vault is larger, create and import smaller batches. PortaPass blocks a Google export above 3,000 selected rows so the failure is caught before you create another sensitive file.
4. Import, verify, delete
In Chrome, open Google Password Manager > Settings. Under Import passwords, choose Select file and follow the on-screen result. Search for a few important websites, check warnings, and only then delete the original and converted files. Google specifically recommends deleting the CSV because anyone with device access can read it.