TSV to CSV Converter — Free Online
Convert spreadsheet clipboard data from TSV to valid CSV. Quotes fields with commas, newlines, and escapes quotes by doubling them.
TSV to CSV Converter
Files never leave your browser0 lines · 0 chars · 0 B
0 lines · 0 chars · 0 B
You're on 7BusyBoss — 300+ free tools that run instantly in your browser. No signup, nothing uploaded.
The spreadsheet clipboard workflow: why copying cells gives you TSV
When you select a range in Excel or Google Sheets and copy it, what lands on the clipboard is tab-separated, not comma-separated. That is the single most common way people end up holding TSV without having chosen it — you wanted "the data", and the clipboard handed you a format. Converting that paste into valid CSV is what this tool is for.
Going TSV to CSV adds quoting rather than removing it
This is the opposite of the reverse conversion. A cell containing a comma — an address, a price written 1,250, an ordinary sentence — was perfectly safe in TSV, where the only special character is the tab. In CSV that comma would split the cell in two, so the converter wraps the field in double quotes. Portland, Maine becomes "Portland, Maine".
The same rule catches two more cases. A cell containing a newline is quoted so the multi-line content stays one field. And a cell containing a double quote is quoted and has that inner quote doubled, which is the CSV standard's escape mechanism: a field reading Pipe 5" is written "Pipe 5""". That run of three closing quotes looks alarming and is correct — the outer pair delimits the field, and the doubled pair inside represents one literal quote character.
Worked example: all three cases at once
Input (TSV, tabs shown as gaps):
Product Price Note
Widget 1,250 Good
Pipe 5" 99.99 ok
Output (CSV):
Product,Price,Note
Widget,"1,250",Good
"Pipe 5""",99.99,okOnly the two cells that needed protection were touched. Widget, Good, 99.99 and ok pass through untouched, because quoting every field would be valid CSV but needlessly noisy.
Ragged rows and empty lines
The converter does not pad short rows. If your source has rows with differing column counts, that unevenness is preserved exactly, because silently inventing empty cells would be a guess about data you did not supply. Fully empty rows are dropped, and carriage returns are stripped so Windows-style line endings normalise cleanly. This padding behaviour differs from the CSV to Markdown Table Converter, which must pad, since a Markdown table has to be rectangular to render at all.
How to use the TSV to CSV Converter
Takes about a minute. No signup, no download, your data stays in your browser.
- 1Open the tool. Scroll up to the TSV to CSV Converter above — it loads instantly in your browser, no install needed.
- 2Enter your values. The fields come pre-filled with realistic defaults so you can see how it works — replace them with your own numbers.
- 3Read the result. The output updates instantly. Copy or share it — nothing is uploaded to a server, everything stays on your device.
Frequently asked questions
Common questions about the TSV to CSV Converter.
Why do some cells have quotes around them after conversion?
Quotes are added only when a cell contains a comma, a double quote, or a newline. Those characters are structural in CSV and must be quoted so they are read as content rather than as a column or row break. Cells without them are left bare, since quoting everything would be valid but needlessly noisy.
Why does one of my fields end in three quote marks?
Because a literal double quote inside a CSV field is escaped by doubling it, and the whole field is then wrapped in quotes. A cell reading Pipe 5 followed by an inch mark comes out as a quote, then Pipe 5, then two quotes, then a closing quote. The outer pair delimits the field and the inner pair means one real quote character.
Will my rows be padded if they have different numbers of columns?
No. Ragged rows are preserved exactly as they are, because adding empty cells would be inventing data you did not provide. If you need a uniform rectangular grid, the CSV to Markdown Table converter pads rows, since a Markdown table cannot render without it.
Are empty rows and carriage returns removed?
Yes. Completely empty rows are dropped, and carriage returns are stripped during parsing, so a file with Windows line endings converts the same as one with Unix endings. Blank lines between data rows therefore will not produce phantom empty records.
Does a stray inch mark or apostrophe in my data break the conversion?
No. A double quote appearing in the middle of a cell is treated as an ordinary character, which is what it is in TSV, and is escaped properly on the way into CSV. Only a quote at the very start of a field begins a quoted section, matching the CSV standard.
Community rating
Discussion (0)
No comments yet. Start the discussion.
Keep exploring
Related tools across 7BusyBoss — all free, all instant.
More in Data Converters
- CSV to Markdown Table Converter
- JSON to XML Converter
- CSV to TSV Converter
- JSON to Markdown Table Converter
- XML to JSON Converter