Importing a CSV file into the Mac Passwords app should be simple: choose the file, confirm the import, and watch your saved logins appear. In reality, many people run into vague messages, missing passwords, rejected rows, or imports that appear to work but produce messy results. The good news is that most CSV import errors come from a small set of fixable issues: column names, formatting, encoding, duplicate entries, and invalid website addresses.
TLDR: If your CSV will not import into the Mac Passwords app, first check that it uses a clean, supported structure with columns such as Title, URL, Username, Password, and Notes. Make sure the file is saved as a standard CSV in UTF-8 format, with commas as separators and properly quoted fields. Fix blank required fields, malformed URLs, strange characters, and duplicate entries before trying again. For best results, test with a small CSV first, then import the full file once the structure is confirmed.
Why CSV Imports Fail in the Mac Passwords App
The Passwords app on macOS is designed to keep login data organized, encrypted, and synced through iCloud Keychain. Because passwords are sensitive, the app is much less forgiving than a spreadsheet program. A spreadsheet app may happily open a messy CSV with missing cells, invisible characters, or inconsistent columns, but the Passwords app may reject it or skip entries.
CSV stands for comma separated values, but not every CSV is created the same way. One password manager may export fields in a different order, another may use semicolons instead of commas, and a third may include extra columns for tags, folders, custom fields, or attachments. The Mac Passwords app expects data it can map clearly to login items. If that mapping is unclear, errors happen.
Start by Checking the Column Headers
The most common cause of import failure is an incompatible header row. The first row of your CSV tells the Passwords app what each column contains. If the headers are missing, misspelled, or too specific to another password manager, the import may fail.
A clean CSV for the Mac Passwords app should generally include columns like:
- Title — the name of the login, such as “Gmail” or “Bank Account”
- URL — the website address associated with the login
- Username — the email address, user ID, or account name
- Password — the actual password
- Notes — optional extra information
- OTPAuth — optional one-time password data, if supported by your export
If your CSV has headers like login_uri, account, secret, folder, or nickname, consider renaming them to simpler labels before importing. You do not always need every column, but you do need the important ones to be recognizable. At minimum, make sure each login has a website, username, and password wherever possible.
Make Sure the File Is Really a CSV
A surprisingly common problem is that the file looks like a CSV but is not saved correctly. For example, you may have opened the export in Numbers or Excel, edited it, and then saved it as a spreadsheet file instead of exporting it back to CSV. The Passwords app needs a plain CSV file, not an XLSX, Numbers, TSV, or rich text document renamed with a .csv extension.
To avoid this, open the file in a spreadsheet app only for editing, then use the export option and choose CSV. If you are using Numbers, go to File > Export To > CSV. If you are using Excel, choose Save As or Export, then select a CSV format. When possible, choose UTF-8 encoding.
Fix Encoding and Strange Character Problems
If your import fails or produces odd symbols, the issue may be text encoding. Passwords exported from older apps or non-English systems may contain accented letters, smart quotes, emojis, currency symbols, or non-Latin characters. If the CSV is not saved as UTF-8, those characters may become corrupted.
Look for signs such as:
- Website titles showing question marks or boxes
- Names with broken accented characters
- Passwords containing unexpected replacement symbols
- Rows that import only up to a certain point and then stop
The best fix is to reopen the CSV in a trusted editor and re-export it as UTF-8 CSV. If you are comfortable with a text editor, you can also open the file in an app such as BBEdit, Visual Studio Code, or another plain text editor and confirm the encoding before saving.
Check for Broken CSV Formatting
CSV files are simple, but they are also easy to break. A comma inside a note, a quotation mark inside a password, or a line break inside a field can confuse the import process if it is not formatted correctly.
For example, this can cause trouble if not quoted properly:
My bank, checking account
Because the comma may be interpreted as a separator, the Passwords app might think the row has too many columns. The correct CSV format wraps that field in quotation marks:
“My bank, checking account”
Quotation marks inside a field need special handling too. In a valid CSV, quotes inside quoted text are usually doubled. If you see messy rows where the columns shift sideways halfway through the file, you likely have a quoting problem.
A practical fix is to open the CSV in Numbers or Excel and inspect whether each piece of data appears under the correct column. If passwords are appearing in the Notes column, URLs are appearing under Username, or some rows have extra columns, clean those rows before importing.
Use Proper Website URLs
The Passwords app relies heavily on the website address to match logins with websites and apps. If the URL column contains invalid or incomplete values, the import may fail or the saved password may not autofill correctly later.
Instead of entries like:
- gmail.com login
- www bank site
Use proper addresses such as:
- https://google.com
- https://accounts.google.com
- https://www.examplebank.com
Not every URL has to be perfect, but it should look like a real web address. Remove spaces, comments, and multiple websites from a single URL field. If an entry has several URLs, choose the main login page and place the rest in Notes.
Remove Empty or Useless Rows
Blank lines are easy to miss, especially at the bottom of a spreadsheet. But empty rows can cause import warnings or make the app behave unpredictably. Before importing, scroll through the CSV and delete rows that contain no useful login data.
Also watch for rows where the password is blank. Some password managers export secure notes, identities, credit cards, Wi-Fi passwords, or software licenses into the same file as website logins. The Mac Passwords app may not know what to do with these items if they do not resemble login credentials.
It is often better to split your export into two files:
- A clean login CSV containing websites, usernames, and passwords
- A reference archive containing notes or unsupported items that you store elsewhere securely
Handle Duplicates Before Importing
Duplicate entries can create confusion, especially if you have already used iCloud Keychain or Safari password saving. The Passwords app may warn you about duplicates, skip some entries, or import multiple versions of the same login.
Before importing, sort your CSV by URL or Username and look for repeated accounts. If two entries have the same website and username, decide which password is current. Keep the better entry and delete the outdated one. If you are not sure, keep both temporarily but add a note such as old export or verify later.
After import, you can use the Passwords app’s security recommendations and search tools to review duplicates, reused passwords, and weak passwords. However, cleaning duplicates before importing saves time and reduces clutter.
Try a Small Test Import First
If you have hundreds or thousands of passwords, do not begin by importing the entire CSV. Create a small test file with five to ten rows. Include a few typical entries, such as one simple login, one login with notes, one with a long password, and one with special characters.
If the test import works, your file structure is probably acceptable. If it fails, troubleshooting is much easier because you only have a few rows to inspect. Once the small file imports correctly, apply the same formatting to the full CSV.
Check macOS and iCloud Settings
Sometimes the CSV is not the problem. Make sure your Mac is updated to a macOS version that includes the Passwords app and supports the import feature you are trying to use. Restarting the app or restarting the Mac can also clear temporary glitches.
If you expect imported passwords to sync to your iPhone, iPad, or another Mac, confirm that iCloud Keychain is enabled. Go to your Apple Account settings, open iCloud options, and make sure password syncing is turned on. Importing may happen locally first, but syncing depends on your iCloud configuration and network connection.
Protect the CSV After Importing
A CSV password export is extremely sensitive. It is usually unencrypted plain text, meaning anyone who opens it can read your usernames and passwords. While troubleshooting, keep the file somewhere private and avoid uploading it to online converters or unknown repair tools.
After the import succeeds, securely delete the CSV if you no longer need it. Also empty the Trash. If you stored copies in Downloads, Desktop, iCloud Drive, email attachments, or backup folders, remove those too. For long-term safety, consider changing important passwords after migration, especially for banking, email, cloud storage, and work accounts.
Common Import Error Fixes at a Glance
- Import button is unavailable: Confirm the file is a real .csv file, not a spreadsheet or text document with the wrong extension.
- Rows are skipped: Check for missing URLs, usernames, or passwords, and remove blank rows.
- Columns import incorrectly: Fix the header row and check for commas or quotes that are not escaped properly.
- Characters look broken: Re-save the CSV using UTF-8 encoding.
- Autofill does not work: Clean up the URL column so each entry has a valid website address.
- Too many duplicates appear: Sort and remove repeated entries before importing again.
Final Thoughts
CSV import errors in the Mac Passwords app can be frustrating because the messages are not always detailed. Still, the solution is usually methodical rather than mysterious. Clean the headers, verify the format, save as UTF-8, repair broken rows, and test with a small file before moving everything over.
Once the import is complete, the effort pays off. Your passwords become easier to search, safer to store, and more convenient to use across Apple devices. A tidy CSV is not just a troubleshooting step; it is the bridge between an old password system and a cleaner, more secure workflow on your Mac.
Comments are closed, but trackbacks and pingbacks are open.