Convert TSV to CSV

Yes – for real, this time. Fields containing the output delimiter, double quote, CR, or LF get wrapped in "..." with embedded quotes doubled. Doe, Jr. → "Doe, Jr."; say "hi" → "say ""hi""". Output passes through standard CSV parsers (Excel, Python csv module, Node csv-parse) without data corruption. Many tools skip this step and produce broken CSV that fails when a value contains a comma – we don’t.

TSV uses tab characters as field separators; CSV uses commas. TSV has no escaping convention – it assumes values don’t contain tabs. CSV has RFC 4180 escaping rules for fields with commas, quotes, or newlines. Excel exports both formats; databases and APIs vary. The main advantage of TSV is that values like 3,14 (decimal commas) stay intact without escaping.

In locales where comma is the decimal separator (Germany, France, Italy, Spain, Brazil, much of EU), Excel saves CSV using semicolons as the field separator to avoid ambiguity with decimal commas. So 3,14;Berlin means “3.14 in Berlin”, not “three values: 3, 14, Berlin”. Pick semicolon if your target environment uses this convention.

Replaced with spaces with a warning toast. TSV has no escaping convention – if a value contains a tab, it would silently become two values, corrupting the structure. The tool replaces embedded tabs and newlines with single spaces and reports how many replacements happened so you can spot data that needs further cleanup before TSV-ization.

Yes – the whole pipeline is UTF-8 throughout. Accented characters (é), CJK (你好), emoji (😀), RTL scripts all pass through unchanged. The browser’s text rendering handles them; the conversion logic just shuffles characters between columns. No re-encoding step that could corrupt anything.

Preserved as-is. Each row is converted independently to match its actual column count. If row 1 has 3 columns and row 2 has 5 columns, the CSV output mirrors that. Spreadsheet apps render this as a ragged table; some downstream tools expect rectangular data and may complain, but the conversion itself is faithful.

Not specifically stripped. If your CSV/TSV starts with a BOM (), it appears as a leading invisible character in the first cell. Strip it from the source before pasting if needed. Most modern exports don’t include BOM unless explicitly requested for Excel compatibility.

200,000 characters. Beyond that the table preview slows browsers (each cell is a DOM node). Conversion still processes the full input; only the table preview caps at 50 displayed rows with a “Showing first 50 of N rows” note. Copy and Download deliver the complete output.

No. All parsing, escaping, table rendering, and TSV/CSV serialization run in your browser. Open DevTools → Network and confirm zero requests fire – even when you Convert or Download. Safe for proprietary datasets, customer lists, or anything you’d rather not send to a third-party converter.

Yes. Total bundle is about 20 KB. Load once, disconnect, keep converting. The parser and serializer are pure JavaScript – no library dependencies, no fonts to fetch, no analytics. Useful for cleaning data on airgapped systems or in environments without internet access.