TSV to CSV Converter

About this tool

When data fields contain commas, CSV breaks or requires cumbersome quoting that confuses older tools. TSV uses the tab character as its delimiter, so commas inside fields are never special and the file works cleanly with Linux tools like cut and awk. The converter flips between these formats handling edge cases that break naive implementations: quoted comma-containing fields unwrap properly going CSV to TSV, and fields gaining commas get auto-quoted going TSV to CSV. Rows keep their original order, header included. A cell that contains a line break or a double quote is wrapped in double quotes in either output, with inner quotes doubled, so multi-line cells survive the trip but appear as quoted fields in the TSV. The output can be pasted into Excel or Google Sheets, or saved for BigQuery's TSV importer and Snowflake bulk loads. Because conversion happens in the browser, customer data and HR exports never leave your machine.

Why use it

• Tab Delimiter, Little Quoting: In TSV output, commas inside fields are ordinary characters, so only cells containing a tab, a line break or a double quote are quoted — no column misalignment when pasting into tools that split on commas.

• Quote-Aware CSV Parsing: Going CSV to TSV, the parser correctly unwraps quoted fields containing commas or embedded newlines before writing tab-separated output. Going TSV to CSV, fields containing commas are automatically wrapped in RFC 4180 quotes.

• Header Row Preserved: The first row is kept at the top of the output in the original column order. Column names are never altered, reordered, or truncated during conversion.

• Multi-Line Cells Kept Intact: A quoted cell that spans several lines stays one cell — it is written back as a quoted field with its line breaks, rather than being split into extra rows.

• Spreadsheet Friendly: Paste the TSV output straight into Excel or Google Sheets and each value lands in its own column without an import wizard.

• Local-Only Conversion: Customer PII, financial records, and HR data exports stay entirely in your browser tab throughout the conversion. No file is uploaded and no data is sent to any server or third-party endpoint during the conversion process.

How to use

1. Click CSV → TSV or TSV → CSV to choose the direction
2. Paste the source data including the header row into the Input box
3. Click Convert and verify that the column count per row looks correct
4. Use Swap to move the output back into the input for another pass (pick the direction again first)
5. Click Copy and paste the result into a file or spreadsheet

When it helps

• Converting a comma-delimited export to TSV because fields contain commas (addresses, product names, descriptions)
• Preparing data for a Linux pipeline using cut or awk, which prefer tab delimiters over quoting-sensitive CSV
• Converting a TSV database export back to CSV for import into Excel or Google Sheets
• Uploading data to BigQuery or Snowflake using their TSV bulk load format which reduces parse errors for comma-heavy data
• Fixing a misaligned CSV file caused by unquoted commas in fields by converting to TSV and back with proper quoting
• Sharing tabular data with a colleague who works in a tool that reads TSV but not CSV

Examples

name,city,note
Acme,"New York, NY",Founded 1903
Globex,Springfield,"Multi, line"

name	city	note
Acme	New York, NY	Founded 1903
Globex	Springfield	Multi, line

id	name	note
1	Ada	no commas here
2	Alan	needs, quoting

id,name,note
1,Ada,no commas here
2,Alan,"needs, quoting"

title,body
Hello,"Line one
Line two"

title	body
Hello	"Line one
Line two"

Tips

• TSV is the natural format for Linux pipelines — cut -f2 and awk -F'\t' both work without any quoting complexities.
• If your data already contains tab characters, replace them with a placeholder before converting — TSV has no standard escape mechanism for literal tabs inside fields.
• Excel auto-detects tab delimiter on files with the .tsv extension; saving with that suffix skips the import wizard entirely.
• BigQuery and Snowflake prefer TSV for bulk loads when fields commonly contain commas — it reduces parse errors compared to quoted CSV.
• If a downstream tool needs one record per line, replace line breaks inside cells before converting, since the converter keeps them in quoted fields.

Frequently Asked Questions

Glossary

Delimiter

The character used to separate fields within a row of tabular data. CSV uses comma; TSV uses tab. The choice of delimiter determines which characters in field values require special handling.

Tab character (\t)

The ASCII horizontal tab character (code point 9) used as the field separator in TSV files. Because tabs rarely appear in real data values, TSV files almost never require field quoting.

RFC 4180

The informal standard defining CSV file structure, including how to quote fields that contain commas, newlines, or double-quote characters. TSV does not follow RFC 4180 because its delimiter makes most quoting unnecessary.

Quoted field

A CSV field wrapped in double quotes to allow it to contain the delimiter character (comma), newlines, or literal double-quote characters. Quoted fields must be unwrapped before converting to TSV.

Header row

The first row of a tabular file that contains column names rather than data values. The CSV-TSV converter detects and preserves the header row at the top of the output in the original column order.

Field escaping

The technique of encoding special characters in field values to prevent them from being misinterpreted as delimiters or row terminators. In TSV, escaping is rarely needed because the tab delimiter rarely appears in real data.