How to Convert an Email List Between TXT, CSV and JSON

Every tool wants your list in a different shape: your mailer imports CSV, your script wants JSON, your spreadsheet pastes one-per-line. Converting by hand with find-and-replace is where formatting errors creep in. Here’s the reliable way.

1. Paste the list in whatever shape it’s in

Open the Email Converter and paste your addresses — one per line, comma-separated, semicolon-separated, or already-structured CSV/TSV/JSON. The parser detects the input shape automatically, so you don’t need to pre-clean it. Like everything on this site, conversion runs locally in your browser; the list is never uploaded.

2. Pick the output shape

Choose the target format and tune it:

• Plain text with newline, comma, semicolon, pipe or a custom separator for pasting into forms and documents.
• CSV / TSV with an optional domain column — ideal for spreadsheet pivots and mail-merge imports.
• JSON for scripts and APIs.
• Batching splits large lists into fixed-size groups with blank lines between them, ready for chunked sending or staged imports.

Need a specific order first? Run the list through the Email Sorter — alphabetical, by domain, by length or by frequency — then convert. The Email Formatter handles separators, grouping and column layout for display-oriented output.

3. Validate before you import

Format errors are the most common reason imports fail silently: a stray space, a duplicated address, an invalid row. Before pushing the converted file into another system, pass it through the Email Cleaner to drop invalid lines and through the Email Deduplicator if the list was assembled from multiple sources. The dedupe guide covers exact, case-insensitive and Gmail-aware merging.

Copy the result or download it as TXT, CSV or JSON. Thirty seconds, zero uploads, and a file the next tool accepts on the first try.

Common mistakes to avoid

Hand-converting with find-and-replace. Replacing newlines with commas in a text editor breaks quoted CSV fields, leaves trailing separators, and silently merges invalid rows into the output. Paste the original into the Email Converter instead — it detects newline, comma, semicolon, pipe, CSV, TSV, and JSON inputs automatically and emits correctly escaped output for the chosen target.

Converting before cleaning and deduping. Format-shifting a dirty list bakes invalid rows and repeats into the new file, where the next tool imports them as if they were legitimate. Run the Email Cleaner to drop syntax failures and the Email Deduplicator to collapse repeats first, following Remove Duplicate Emails. Convert only the survivors so every row in the export is worth importing.

Dropping the domain column when you will need it. A bare one-per-line TXT export is perfect for pasting but useless for pivots, per-company filtering, or bounce analysis later. When the destination is a spreadsheet, CRM, or mailer, choose CSV with the domain column enabled so each address travels with its domain. You can always derive a plain list later with the Domain Extractor or a second conversion pass.

Using the wrong separator for your locale. Many European spreadsheet versions expect semicolons because commas serve as decimal separators, so a comma-joined list imports as a single column. Match the converter’s separator to the destination: commas for most US mailers, semicolons for EU Excel, tabs/TSV for strict tabular pastes, and newlines for form fields. When in doubt, export CSV and test-import five rows before committing the full list.

Pro tips and workflow recipes

Recipe 1: Mailer-ready CSV in under a minute. Clean the list, dedupe it, and sort by domain if you want provider blocks preserved. Open the Email Converter, select CSV with domain column, and download. Import the five-row sample into your sender first to confirm header mapping, then import the full file. Recount with the Email Counter after import — accepted rows should equal cleaned uniques.

Recipe 2: Script-ready JSON without hand-editing. Paste the vetted list into the converter and choose JSON for APIs and Node or Python scripts. JSON output avoids the trailing-comma and quoting bugs of manual assembly and pairs directly with extraction logs from the Email Extractor. Keep a TXT twin for human review via the Email Formatter when separators and grouping matter for display.

Recipe 3: Chunked sending batches. For staged rollouts or per-day sending caps, use the converter’s batching control to split a 10,000-address list into fixed-size groups with blank lines between them. Convert each batch to the mailer’s preferred shape separately, label files batch-01, batch-02, and track per-batch bounces using the routine in Reduce Email Bounce Rate. Batching locally keeps list order deterministic and auditable.

Troubleshooting

• Symptom: CSV imports but only the first column fills. Cause: separator mismatch — the file uses commas while the spreadsheet expects semicolons, or vice versa. Fix: re-convert with the matching separator in the Email Converter and re-import the sample before the full file.
• Symptom: JSON fails to parse downstream. Cause: hand-edited trailing commas, smart quotes from word processors, or concatenated exports. Fix: regenerate JSON directly from the converter without pasting through Docs or Word, and validate addresses beforehand with the Email Validator.
• Symptom: converted file still contains blank lines and junk rows. Cause: the source was converted before cleaning. Fix: pass the source through the Email Cleaner, dedupe, then convert again — formatting cannot fix data quality.
• Symptom: special characters garble after import. Cause: encoding mismatch or display formatting baked into the file. Fix: download the converter output directly as TXT/CSV/JSON and import without opening in rich-text editors. Conversion runs entirely in-browser in a Web Worker, so re-exporting is instant and private — confirm zero uploads in DevTools Network tab.

FAQ

How do I convert a TXT email list to CSV?

Paste the one-per-line list into the Email Converter and select CSV, enabling the domain column if you want spreadsheet pivots. Download the result and open it in Excel or Sheets. For source material still buried in documents, extract first per Extract Emails from PDF Word or Extract Emails from Any Text, then convert.

How do I convert CSV emails to JSON for a script or API?

Drop the CSV into the converter and choose JSON output — headers and separators are detected automatically, so no manual restructuring is needed. Validate the resulting addresses with the Email Validator before feeding them to code, since scripts typically fail harder than mailers on a single malformed row.

How do I change comma-separated emails to one-per-line?

Paste the comma, semicolon, or pipe-separated string into the Email Converter and select plain text with newline separator. For display-oriented grouping with custom separators and columns, the Email Formatter offers finer layout control after conversion.

Can I convert email list formats without uploading my list?

Yes. The converter, sorter, and formatter on this site all process 100% locally in your browser via a Web Worker. Paste or drop the file, convert, and download — open DevTools Network tab to verify nothing is transmitted. That makes format-shifting safe for sensitive CRM and client exports.

What to do next

Shape the list for its destination: order it with the Email Sorter, polish separators with the Email Formatter, and audit the final file with the Email Counter. Then systematize quality with Sort Email List Alphabetically by Domain and Email List Hygiene Validation.