Professional Email Converter — Convert Between Formats Online

Why list formats keep colliding

Every tool wants your list in a different shape: the mailer imports CSV with an email header, the script wants a JSON array, the spreadsheet pastes one-per-line, the legacy system expects semicolons. Converting by hand with find-and-replace is where quoting breaks, headers get treated as addresses, nested export wrappers get mangled and trailing delimiters corrupt the last row.

The converter removes that entire class of error. Drop in a CRM export, a JSON array, a CSV with headers or a plain pasted blob; it detects the input shape, extracts every address, deduplicates, and renders exactly the output format the destination expects — TXT, CSV, TSV or JSON — all locally in the tab.

How input detection works

Input starting with [ or { that parses as JSON is treated as JSON: arrays of strings, arrays of objects with email, address or mail fields, and objects wrapping such arrays under keys like emails, addresses, results or data — the shapes real CRMs and APIs emit. Comma-separated headers or row-like lines map to CSV; everything else is scanned as plain text.

That detection order matters. A JSON export pasted with surrounding commentary still converts correctly because structured parsing is attempted before the plain-text fallback, and the detected-format label in the summary tells you which path was taken so surprises are visible, not silent.

• JSON arrays, object arrays and wrapped result envelopes
• CSV/TSV with headers, quoted fields and mixed columns
• Plain blobs: HTML, logs, chat exports, pasted prose

Choosing the right output

TXT with newlines is the universal interchange — every tool reads it. CSV with the optional domain column is the spreadsheet and CRM import shape. TSV suits locales where commas appear inside fields. JSON is the API and script shape, pretty-printed for readability. Batching with blank lines every N addresses ports directly into staggered-send workflows behind per-message recipient caps.

Conversion re-runs instantly when options change, so preview the destination shape before committing. Forcing a specific output is a deliberate choice in the options rail, not a guess — the same validated list rendered four ways is still the same list.

Converter, formatter, extractor: which one

The Extractor pulls addresses out of hostile sources (documents, pages, logs). The Converter migrates between structured shapes with detection. The Formatter fine-tunes rendering (separators, batches, columns) for a known-good list. A typical CRM migration runs Extractor → Converter → Formatter in sequence; a weekly newsletter export usually needs only the Converter. All three are idempotent and offline, so chaining them never risks your data.

Note on normalization: the Converter folds plus-tag variants (user+tag@domain) to their base address during deduplication, while the Extractor preserves them as distinct entries. If plus-tags carry meaning for your segmentation, use the Extractor or Formatter instead of the Converter.

Keep reading