The .tsv file.
A CSV whose separator does not appear inside the data. That single change removes the most common way a delimited file goes wrong.
What it actually is
A TSV separates fields with a tab character. Because tabs almost never appear inside a value, the quoting rules that make CSV parsing genuinely difficult are rarely needed, and a file can usually be split on the delimiter with no further thought.
It is the default export of a great many scientific and bioinformatics tools for exactly that reason, and it is what you get from most database command-line clients.
The cost is invisibility. A tab and a run of spaces look identical, so a file damaged by a text editor that converts one to the other gives no visual warning at all.
At a glance
- Delimiter
- A tab character
- Quoting
- Rarely needed, because tabs seldom appear in values
- Encoding
- Undeclared, like CSV
- Common from
- Database clients, scientific tools, some ad platforms
- Read here as
- Direct, as delimited text
- Status
- Ready
- Fidelity
- Read directly
- Largest file
- 250 MB
Read as delimited text.
Upload one
The analysis runs before there is anything to pay for. You see what it found, and the evidence behind it, first.
No account needed to start. You only pay when you like what you see.
What goes wrong, and what is done about it
01
An editor that turned tabs into spaces
Many editors expand tabs on save. The file then has no delimiter at all, every row is one field, and nothing about it looks different.
The delimiter is detected from the content rather than the extension, so a file whose tabs have become spaces is identified as fixed-width or space-delimited instead of failing silently.
02
Embedded newlines with no quoting to protect them
Because TSV rarely quotes, a value containing a line break splits the row, and the columns after it shift left for the rest of the file.
Rows whose column count does not match the header are reported with their line numbers rather than dropped, so the damage is visible and locatable.
Questions people ask
Is TSV better than CSV?
For anything containing commas in its text, yes, because the delimiter collision is what most often breaks a CSV. For long-term storage, Parquet beats both, since it carries types.
Do I need to say it is tab-separated?
No. The delimiter is detected by trying each candidate and keeping whichever one produces a consistent column count down the whole file. Tabs, commas, semicolons and pipes are all handled without being declared anywhere.
Can I mix TSV and Excel files in one project?
Yes. Sources are joined on their content rather than their container, so the format each one arrived in makes no difference to how they are matched. A TSV export and an .xlsx workbook can be two halves of the same analysis.