Updated 2026-10-16
CSV vs TSV: What's the Difference?
CSV separates fields with a comma. TSV separates them with a tab character. Everything else is nearly identical, so the choice usually comes down to which character is more likely to appear inside your values.
Quick answer
Both formats are plain text where each line is one record and each field is separated by a single delimiter. Use CSV when tools expect commas and your values can tolerate quoting. Use TSV when your values contain commas but rarely tabs, because a tab-delimited file then needs no quoting at all. Neither format is a database format, and both lose type information when you save.
What each format actually is
CSV
CSV stands for comma-separated values. RFC 4180 defines the common form: each line is a record, records are separated by a line break, and fields are separated by commas. Fields containing a comma, a double quote, or a line break must be wrapped in double quotes, and a literal double quote inside a quoted field is written twice.
RFC 4180 also states that a different delimiter can be used if both sides agree on it. That sentence is why regional variants of CSV exist. Some locales produce semicolon-delimited files, and the same rule is what makes a tab-delimited file a close relative rather than a separate species.
TSV
TSV stands for tab-separated values. The tab character has a registered media type in the IANA text media type table, text/tab-separated-values. In many TSV conventions the tab is treated as a field separator and quotes carry no special meaning, so a value is never escaped.
That simplicity is also the format's limitation. If a value ever contains a real tab character, the row cannot be represented without an out-of-band rule, and different tools resolve that differently.
Side-by-side comparison
| Property | CSV | TSV |
|---|---|---|
| Field separator | Comma | Tab (U+0009) |
| Quoting rule | Defined by RFC 4180, double quotes | Often none; quotes are literal text |
| Commas inside a value | Must be quoted | No special handling needed |
| Tabs inside a value | No special handling needed | Cannot be represented cleanly |
| Tool support | Very wide across spreadsheets and libraries | Common in Unix tools and data pipelines |
| Typical source | Spreadsheet export, web download | Database export, log and CLI output |
Why commas cause so much trouble
A comma inside a value breaks the column count unless the value is quoted. Addresses, names written as "Last, First", and free-text notes all contain commas regularly, which is why CSV files so often arrive misaligned or land in a single column.
If your import opens with everything in column A, the delimiter detected by the tool does not match the file. Our guide to CSV delimiter options covers how to spot which character a file actually uses.
When to choose TSV instead
- Your values are full of commas: addresses, product titles, descriptive text.
- You are piping data between command-line tools, where tab is the default field separator.
- You want a file a human can scan without mentally skipping quote characters.
- Your pipeline controls both ends and can forbid literal tabs inside values.
Stick with CSV when you need the broadest support, when you are sharing the file with someone who will open it in a spreadsheet, or when your values may contain tabs.
Converting between the two
Conversion is a delimiter swap plus an escaping decision. Moving TSV to CSV, wrap any field containing a comma in double quotes and double the quotes inside it. Moving CSV to TSV, unquote the quoted fields only if no value contains a tab, and remember that a quoted value spanning multiple lines will not survive a naive line-by-line conversion.
You can do the swap in a spreadsheet by choosing the source delimiter at import and the target delimiter at export. For a quick browser-based pass, try our delimiter converter. If your file is tab-delimited today, converting it to comma-separated is the same operation described in Convert TSV to CSV.
Encoding and the tab character
Both formats are affected by character encoding, and neither defines one. The tab character is U+0009 in the Unicode standard, so it is identical across ASCII and UTF-8. What changes between files is how non-ASCII text is encoded, which is a separate problem from the delimiter. If fields look garbled rather than shifted, the issue is encoding, not the separator.
Frequently asked questions
What is the difference between CSV and TSV?
CSV uses a comma to separate fields on each line, while TSV uses a tab character. Both are plain-text, line-based formats defined so each line is one record. The only structural difference is the field separator, plus the quoting rules that follow from it.
Is TSV the same as CSV with tabs?
In practice, yes. A TSV file is a delimited text file whose delimiter is the tab character. CSV is defined by RFC 4180 with comma as the default delimiter, and RFC 4180 itself allows a different delimiter to be used by mutual agreement.
Which is better, CSV or TSV?
Choose CSV when your data may contain tabs inside field values and when you need the widest tool support. Choose TSV when your values often contain commas but rarely tabs, because tabs inside a value are far less common and quoting becomes unnecessary in most files.
Can TSV files contain commas inside a field?
Yes. In a TSV file the comma is an ordinary character, so a value like "New York, NY" needs no quoting at all. That is the main practical advantage of TSV over CSV for address and free-text columns.
How do I convert a TSV file to CSV?
Replace each tab character with a comma, then wrap any field that itself contains a comma in double quotes and double any quotes inside it, as described by RFC 4180. You can do this in a spreadsheet by importing with the tab delimiter and exporting as comma-separated, or with a browser tool.
Sources
- IETF, RFC 4180: Common Format and MIME Type for CSV Files (delimiter rules and quoting).
- IANA media types registry,
text/tab-separated-values. - Unicode standard, U+0009 CHARACTER TABULATION.
Related reading
Related reading
Format Conversion — other guides that pair well with this one.
- CSV vs ODS: Which Spreadsheet Format Should You Use?
- CSV vs JSON
- Convert CSV to PDF
- Convert CSV to Excel Without Excel
Browse all guides in the NoCodeCSV blog.