How to fix a password CSV before import
A failed password import is usually a schema or row-quality problem, not a mysterious browser failure. Work from the header down, keep password values hidden during review, and fix only a copy of the original.
Start with the header
Google documents url, username and password column names. PortaPass writes Title, URL, Username, Password, Notes and OTPAuth for Apple-format output; Apple’s current Mac import guide does not publish a required column schema. Header names and values must stay aligned, and extra-field support must be verified. Use the header checker on this site for a non-sensitive first pass; enter the header line only.
Check row shape and CSV quoting
Every row should have the same number of fields as the header. Commas, quote marks and line breaks inside a password or note must be escaped using CSV quoting rules. Opening and resaving a password file in a spreadsheet can also alter values, dates or leading characters. A dedicated parser can report inconsistent row lengths without showing the password itself.
Resolve duplicates deliberately
An exact duplicate may be harmless but creates clutter. A conflicting duplicate deserves attention: it uses the same website and username with a different password. Do not automatically keep the newest-looking row unless you know which credential works. PortaPass separates exact duplicates from conflicts and lets you exclude entries before export.
Normalise websites conservatively
A bare domain such as example.com is more likely to import reliably as https://example.com. Existing URLs and non-web identifiers should not be rewritten blindly. PortaPass adds HTTPS only when a value is recognisably a bare domain and preserves other identifiers. Missing passwords remain blocking issues rather than being exported as apparently valid rows.