Why tabs instead of commas
The whole appeal of TSV is that a tab almost never appears inside ordinary data, whereas commas turn up constantly — in prices, addresses, names and prose. With CSV you must quote and escape any field that holds a comma or a line break, and different tools disagree about how that quoting works. TSV mostly avoids the issue: most fields contain no tab, so you can split a line on the tab character and get your columns back with no further ceremony. That simplicity is why TSV is registered with IANA as a media type and why so many command-line tools assume tab-delimited input by default.
The trade-off is honesty about edge cases. The classic TSV convention says a field may not itself contain a literal tab or newline, full stop, so there is no universal escaping mechanism the way there is in CSV. In practice values are sanitised before export, or a stricter variant is used that escapes tabs. If your data genuinely contains tabs, TSV will not protect you and you should reach for a quoted format instead.
Where you meet it
TSV is everywhere in bioinformatics — gene tables, variant summaries and annotation files are routinely tab-delimited, and many genomics tools read and write it without being asked. It is also the natural output when you dump a relational table from the command line, since database clients tend to separate columns with tabs. Spreadsheet applications open it cleanly, and because the structure is so plain it survives being passed through scripts, pipelines and version control without surprises. The invisibility of the delimiter is both its strength and its one usability wart: a tab and a run of spaces look identical on screen, so a file can look right and still be subtly broken.
Strengths
- No comma-quoting headaches — a tab rarely appears inside real values, so parsing is trivial.
- IANA-registered and widely understood by command-line tools, spreadsheets and database clients.
- Extremely compact and human-legible compared with verbose markup.
- Streams and diffs well, one record per line.
Limitations
- The delimiter is invisible, so tabs and spaces are easy to confuse.
- No universally agreed way to escape a tab or newline inside a field.
- Flat by nature — it cannot represent nested or hierarchical data.
- Column meaning depends on position or an informal header row, with no built-in schema.
When to use TSV
Reach for TSV when you are exporting or exchanging simple tabular data and want to avoid the comma-escaping quirks of CSV, particularly in scientific or database workflows.
TSV FAQ
- Is TSV better than CSV?
- Neither is strictly better — TSV wins when your data is full of commas, because it avoids quoting altogether, while CSV is more forgiving when fields can contain tabs or arbitrary text since it has a defined escaping scheme. Choose based on which delimiter is least likely to appear in your values.
- Can I open a TSV file in a spreadsheet?
- Yes. Most spreadsheet programs recognise the tab delimiter automatically, though some prompt you to confirm the separator on import. If columns land in one cell, tell the importer to split on tabs rather than commas.
- How does Morphr convert TSV to other formats?
- Morphr reads the rows on your device — nothing is uploaded — and maps each line to a record, so it can write the same data out as CSV, JSON, JSON Lines or even SQL inserts. Because TSV is flat, converting from a nested source flattens the structure to fit the columns.