Google Password Manager CSV Format
By Mihaly Kertesz · Updated
Google Password Manager imports CSV files with url, username and password columns. A spreadsheet-like appearance does not establish valid headers, delimiters or quoting. The original export and a preserved copy provide a clearer basis for diagnosis than manual changes to real credentials.
Google Password Manager CSV columns
The first record names the columns rather than representing a login. Google documents url, username and password as required import names. Other managers may use labels such as website or login; changing the file extension does not convert those fields.
Passary’s Google-export importer has its own contract: required columns plus optional name and note, case-insensitive header comparison and rejection of unsupported nonempty columns. Acceptance by one destination does not establish acceptance by another.
| Column | Meaning | Passary Google-export import |
|---|---|---|
| url | The login website address | Required header |
| username | Login name or email | Required header |
| password | The saved password | Required header |
| name | Entry label | Optional |
| note | Associated note | Optional |
Google: importing and exporting passwords · Google CSV import to Passary
Google Password Manager CSV example
The sample values are invented and publicly known. They illustrate structure rather than credentials suitable for real use. A comma inside a field requires quoting, and a quotation mark inside a quoted field is doubled. Display wrapping in a text editor does not create another record.
name,url,username,password,note
Example login,https://example.com,reader@example.com,FICTIONAL_PASSWORD_01,Practice only
"Example, two",https://example.org,reader@example.org,FICTIONAL_PASSWORD_02,"A note with ""quotes"""Google Password Manager CSV errors
A preserved copy allows one format difference to be isolated at a time. A file without a readable header may be an incomplete or unrelated download. A fresh export from the source app provides stronger evidence of its intended format.
| Symptom | Relevant detail | Relevant diagnosis |
|---|---|---|
| Missing required header | First record uses the documented labels | Field mapping on a preserved copy |
| Unknown header in Passary | File is actually an unmodified Google export | Importer and format compatibility |
| Whole row appears in one column | Delimiter is a comma rather than a semicolon | Fresh export or documented conversion |
| Notes split into multiple records | Embedded line breaks are quoted | Fictional reproduction of quoting and record structure |
| Import partly succeeds | Skipped rows, blank values or invalid URLs | Summary and missing-record comparison |
Google Password Manager CSV encoding and quoting
Spreadsheets may interpret leading zeros, formulas and long strings instead of retaining exact characters. Those changes matter for passwords and recovery material. The original export and a local plain-text view avoid some of that interpretation.
Unicode, quoted notes and embedded newlines are part of the field data. An XLSX workbook or HTML download is not a text CSV, and removing quotes or line breaks can change valid records. Online conversion introduces another readable copy of the credentials.
Google Password Manager CSV import limits
Google documents a limit of 3,000 passwords per import. Separate batches need complete records and the header in each batch. Splitting on every physical newline can divide a quoted multiline note.
A partial import may already have added records. Further attempts can create duplicates or conflicts, making the summary and representative source comparisons relevant to the result.
Google Password Manager CSV migration recovery
Punctuation, long passwords, Unicode notes and rarely used accounts can reveal mapping differences. A copied encrypted destination backup establishes a separate recovery path after import.
CSV remains readable without a vault password. Temporary copies may persist in Downloads, the Recycle Bin, synchronized folders or backups. Ordinary deletion reduces retention but does not guarantee forensic erasure or remove copies held elsewhere.