Paste addresses in any format — one per line, comma separated, or copied straight out of a To field with names attached. Download as CSV, Excel, JSON, plain text or vCard. Nothing is uploaded.
Or drag a file onto the box — choose a CSV or text file.
Addresses copied out of a To or Cc field arrive as Dana Reed <dana@example.com>. That format gets split into separate name and email columns. Quoted names containing commas — "Patel, R." <r.patel@bbc.co.uk> — are handled correctly, which is where most quick conversions break.
Separators don't matter. Line breaks, commas, semicolons, or addresses buried in ordinary text all work.
CSV for almost anything — spreadsheets, CRM imports, mail platforms. XLSX if you want a real Excel file that opens without an import dialog. JSON for feeding into a script. vCard to import as contacts into Outlook, Apple Contacts or Google Contacts.
CSV and XLSX exports include a byte-order mark, so Excel opens accented characters correctly instead of turning them into mojibake.
The conversion happens inside your browser. Your list is never sent anywhere, which matters when the list is customers rather than test data.
Paste the list or open a file, then download. You can choose which columns to include, the delimiter, and whether to keep a header row.
Yes. Addresses copied from a To or Cc field arrive as Dana Reed <dana@example.com>, and the name is split into its own column. Quoted names containing commas are handled correctly, which is where most quick conversions break.
Yes. The CSV imports into Google Contacts, Outlook and most CRMs. The vCard export imports directly as contacts into Outlook, Apple Contacts or Google Contacts without any mapping step.
A vCard (.vcf) is the standard contact format. Unlike a CSV, it needs no column mapping on import — you open it and the contacts are simply added.
Because Excel assumes the wrong encoding unless the file says otherwise. The exports here include a byte-order mark, so accented and non-Latin addresses open correctly.