Values containing tabs are the risk here
Rare, but not impossible — text pasted from a document can carry a tab. Those values are quoted, which some strict TSV readers do not expect.
Tabs make a delimited file dramatically less fragile, because real data almost never contains one. Converting CSV to TSV is a common step before loading into a database, a bioinformatics tool, or a shell pipeline built on cut and awk.
Reading CSV
Auto-detect reads the first rows and picks the separator that splits them consistently.
Turn off when the file starts straight into data. Columns are then named column_1, column_2, and so on.
Turns "42" into a number and "true" into a boolean. Values with leading zeros stay text so IDs and zip codes survive.
Which worksheet to convert. Filled in once the workbook is read.
Dotted path to the array of records, such as data.items. Leave empty to use the whole document.
Turns {"user":{"id":7}} into a user.id column. Arrays are kept as JSON text.
Pick the encoding the file was written in. Wrong encoding shows up as garbled accents.
Comma-separated words that should become null instead of text.
Writing TSV
Snappy is the default across Spark, DuckDB and pandas. Gzip is smaller but slower to read.
Turns a user.id column back into {"user":{"id":7}}.
Excel needs a byte order mark to open UTF-8 files with accents correctly.
Rows per row group. Larger groups compress better; smaller groups let readers skip more.
conversion-preroll
This short ad is what keeps the converter free.
Plain text rows that open anywhere, with no types and no schema. Like CSV, but tab-delimited, so commas inside values stay harmless.
| CSV | TSV | |
|---|---|---|
| Type information | None — every value is text | None — every value is text |
| Structure | Flat rows and columns | Flat rows and columns |
| Compression | None | None |
| Typical file size | Baseline (100%) | Same as CSV |
| Schema | Header row at best | Header row at best |
| Human-readable | Yes, in any text editor | Yes, in any text editor |
| Tool support | Universal | Universal |
Rare, but not impossible — text pasted from a document can carry a tab. Those values are quoted, which some strict TSV readers do not expect.
Tabs render at different widths depending on the tab stop, so columns rarely line up visually. This is a display artefact, not a data problem.
Some expect no quoting at all and backslash escapes instead. Check a sample if you are loading into something strict, such as a bulk COPY into Postgres.
Bulk load commands handle tab-delimited input with fewer escaping surprises.
cut, awk and sort all default to tab-aware behaviour.
Much of that ecosystem standardised on tab-delimited files.
sticky-bottomYour file is downloading
post-conversion