Importing a CSV file into the Mac Passwords app should be straightforward, but small formatting problems can stop the process with vague errors or missing entries. Because password CSV files contain highly sensitive data, the safest approach is to fix the file carefully, avoid online converters, and delete unencrypted copies as soon as the import is complete.
TLDR: Most Passwords app CSV import errors on Mac are caused by incorrect column names, broken formatting, unsupported characters, duplicate entries, or a CSV file exported in a format Apple does not fully recognize. Open the file in Numbers, Excel, or a trusted plain text editor, check the header row, remove empty or malformed rows, and save it as a standard UTF 8 CSV. If the file still fails, import a smaller test file first, then split the CSV into batches to identify the problematic record.
Understand what the Passwords app expects
The macOS Passwords app is designed to import login credentials from a structured CSV file. A CSV is a plain text table where each row represents one login and each column represents a field such as the website, username, and password. If the columns are mislabeled, shifted, or corrupted, the app may reject the file or import only part of it.
Although exported password files vary by browser and password manager, a clean file usually includes columns similar to:
- Title or name — the name of the account or website.
- URL — the website address, preferably beginning with https://.
- Username — the login name or email address.
- Password — the saved password.
- Notes — optional additional information.
If your CSV came from a third party password manager, the column names may be different. The Passwords app may still understand some common formats, but it is safer to normalize the headers before importing.
Image not found in postmeta
Check the CSV header row first
The first row of the CSV is the header row, and it is one of the most common causes of import failure. If the header row is missing, duplicated, misspelled, or mixed with actual password data, the import may fail.
Open the file in Numbers, Microsoft Excel, LibreOffice Calc, or a trusted plain text editor. Confirm that the first row contains only labels, not real login data. Then make sure each column has a clear purpose. For example, a practical header row may look like this:
Title, URL, Username, Password, Notes
If your file uses different labels such as name, login_uri, login_username, or secret, rename them to simpler terms. Keep the structure consistent and avoid adding unnecessary columns unless you know the Passwords app supports them.
Fix broken rows and shifted columns
A CSV import often fails because one row contains an extra comma, a line break inside a field, or an unclosed quotation mark. This can shift data into the wrong columns. For example, a note like personal, old account may be treated as two separate fields if it is not correctly enclosed in quotation marks.
Look for rows where the website appears under the username column, or where the password appears under notes. These are signs that the CSV structure is broken. In a spreadsheet app, every row should have the same number of columns. Delete empty rows, remove accidental header rows in the middle of the file, and correct any visibly shifted data.
If a note contains commas, quotation marks, or multiple lines, simplify it temporarily. You can add detailed notes back later inside the Passwords app after the import succeeds.
Save the file in the correct CSV format
After editing, export or save the file again as a standard CSV. When possible, choose CSV UTF 8. Encoding problems can cause import errors, especially if your file contains accented characters, non Latin scripts, smart quotes, or special symbols.
Avoid saving the file as:
- .xlsx or .numbers, because those are spreadsheet formats, not CSV files.
- Tab separated text, unless the Passwords app specifically accepts it.
- CSV with unusual regional separators, such as semicolons instead of commas.
If your Mac uses a region where spreadsheets export semicolon separated CSV files, check the file in a plain text editor. A valid comma separated file should separate fields with commas, not semicolons. If needed, change the export settings or use a spreadsheet app that lets you choose the delimiter.
Image not found in postmeta
Remove unsupported or unnecessary data
Some password managers export more than simple website logins. Your CSV may include secure notes, software licenses, identities, credit cards, one time password seeds, archived items, or passkeys. The Passwords app may not import these entries from CSV, or it may ignore unsupported columns.
Before importing, create a copy of the CSV and keep only standard login records. Remove rows that do not have at least a website, username, and password. Also remove columns that are clearly unrelated to logins, such as:
- Folder names or vault names
- Credit card numbers
- Identity profiles
- Attachment names
- Internal item IDs
- Deleted or archived status fields
This does not mean you should permanently discard that information. Keep the original export in a secure location until you have confirmed that all important data has been transferred. However, the file used for import should be as simple and predictable as possible.
Test with a small CSV file
If the full import fails, do not keep retrying the same large file. Instead, create a small test CSV with three to five entries. Use records that look clean and complete. If the small file imports correctly, the Passwords app is working and the problem is inside the larger CSV.
Next, split the original file into smaller batches. For example, import 100 entries at a time. When a batch fails, split that batch again until you find the specific row causing the issue. This method is slower, but it is reliable and avoids guesswork.
Common problem entries include very long notes, blank passwords, URLs without domains, duplicate rows, or passwords containing unusual control characters copied from another system.
Handle duplicate entries carefully
Duplicates can also create confusion during import. The Passwords app may skip identical entries or create multiple saved logins for the same website. Before importing, sort the CSV by URL and username. This makes duplicates easier to spot.
If two rows contain the same website and username but different passwords, do not delete one automatically. One may be old and one may be current. Check the source password manager or test the login before deciding which entry to keep.
After importing, open the Passwords app and review the Security or recommendations sections if available. macOS may flag reused, weak, or compromised passwords, but it cannot always tell which duplicate is the valid one.
Confirm permissions, iCloud, and macOS status
Sometimes the CSV is not the only issue. Make sure your Mac is running a current version of macOS that includes the Passwords app and that you are signed in to the correct Apple Account. If you use iCloud Keychain, confirm that password syncing is enabled and stable before importing a large file.
Restarting the Mac can help if the Passwords app is unresponsive or if the import window does not appear. Also confirm that the CSV file is stored locally, such as in your Downloads folder or Desktop, rather than inside a disconnected external drive or a cloud folder that has not fully downloaded.
Image not found in postmeta
Protect the CSV after the import
A password CSV is unencrypted plain text. Anyone who can open the file can read your accounts and passwords. Once the import is complete and verified, securely delete temporary copies. Check the Desktop, Downloads folder, Recents, cloud storage folders, and Trash.
If you need to keep a backup for a short time, store it in an encrypted disk image or another secure encrypted location. Do not email it to yourself, upload it to an online repair tool, or paste it into an untrusted website for formatting.
Final checklist
- Confirm the first row contains clear headers such as Title, URL, Username, Password, Notes.
- Remove broken, blank, unsupported, or unrelated rows.
- Check that every row has the same number of columns.
- Save the file as a standard UTF 8 CSV.
- Import a small test file before importing the full list.
- Split large files into batches to locate bad records.
- Delete unencrypted CSV copies after confirming the import.
Most Passwords app CSV import errors on Mac can be resolved by cleaning the file rather than changing system settings. Treat the CSV as sensitive data, work from a copy, simplify the structure, and test in small batches. With a clean header row, consistent columns, and a standard CSV format, the import is far more likely to complete successfully.
