PortaPass / Guides
Header reference · checked 13 October 2026

Password CSV header examples for Apple and Chrome

Compare column names without exposing a single login. These examples contain headers only—not passwords, accounts or sample credential rows.

Try the private header checkerView PortaPass on App Store
Keep the records off this website. Do not paste password rows, usernames, notes or one-time-code seeds. A header match does not establish that values are safe, rows are valid or an import will succeed.

Try column names without using your file

Load a fixed example below, then check it. You can also enter one header line of familiar column names. The checker never accepts a file or password rows and clears the input after every check.

Column names only. No upload or storage. Input clears after checking, changing destination, or leaving this page's foreground. Never enter usernames, passwords, notes or OTPAuth values.

Your result will appear here. No file or password rows are checked.

Apple mode compares PortaPass's export names, not an Apple-published required schema. Google mode checks the documented core names. For full local analysis, view PortaPass on the App Store.

Real PortaPass iPhone CSV analysis screen showing ready entries, warnings and duplicates, without showing password values
Real iPhone app screen with illustrative analysis results—not your file or a browser analysis. Full CSV analysis runs in the app on your device.

Google Password Manager: the documented minimum

Google identifies three required column names:

url,username,password

The documentation does not require that example order: keep each column name aligned with its values. Renaming a header is not a reason to move, merge or discard the records beneath it. Read Google's import instructions.

PortaPass's Chrome-format export

name,url,username,password,note

PortaPass writes this five-column order. The name and note fields are additional to Google's documented minimum; a name column cannot replace the URL column. Google's required-header guidance alone is not a promise that every extra field will be preserved.

PortaPass's Apple-format export

Title,URL,Username,Password,Notes,OTPAuth

This is the six-column order written by PortaPass's exporter. Apple's current Mac import guide describes importing a CSV and reviewing failures, but does not publish a required column schema. This example is not an Apple compatibility guarantee for every OS or source file. Check Apple's current Mac instructions.

OTPAuth may contain a secret used to generate verification codes. PortaPass's Chrome-format export has no OTPAuth column. Do not mistake a password migration for a completed second-factor migration: verify codes separately in the destination before removing the source.

How PortaPass maps the two export formats

Field correspondence in PortaPass's exporter—not a promise of destination support
PurposeChrome formatApple format
Service labelnameTitle
Website or login locationurlURL
Login identifierusernameUsername
PasswordpasswordPassword
Sensitive notesnoteNotes
Verification-code provisioning dataNot exportedOTPAuth

A header-only check is just the first step

  1. Export from the source manager on a trusted device. Keep the plaintext file private and temporary.
  2. Compare only its column names here. Use the header-only checker for malformed quotes, duplicate names and hidden line separators.
  3. Review the full file locally for missing values, quoting problems, duplicates and conflicting logins. Follow the local preflight checklist; never upload the file to an online converter.
  4. Import using the destination's current instructions, inspect the result and verify representative logins and verification codes. Once verified, remove the temporary exports yourself.

This reference does not convert a file, validate a password, inspect your vault or perform an import. For on-device analysis and deliberate export, view PortaPass. Full CSV Export is an optional one-time purchase, not a subscription.

Related migration guides