Convert TSV to CSV
Convert TSV to CSV free in your browser. No upload, no signup, no watermark. Files stay on your device.
drop a .tsv file
or click to browse
related
more tsv & csv
see all spreadsheet converters →guide
how to convert tsv to csv
Drop your TSV file
Drag your TSV file into the drop zone above, or click the box to pick a file from your computer or phone. The browser reads the file directly — nothing uploads.
Click Convert
The page runs PapaParse on your device to decode the Tab-Separated Values and encode it as Comma-Separated Values. Most conversions finish in a few seconds; large or codec-heavy files (RAW, video) can take longer.
Download the CSV file
When the conversion finishes, the CSV file is ready to download. Save it anywhere on your device.
FAQ
common questions
What's the difference between TSV and CSV?
Just the delimiter. TSV (Tab-Separated Values) uses tab characters to separate fields; CSV (Comma-Separated Values) uses commas. Both are plain-text tabular data formats with the same general structure (one record per line, fields separated by the delimiter). TSV is popular for data that frequently contains commas (text content, addresses, biology data) where comma escaping would be painful; CSV is the universal default.
Why convert TSV to CSV?
Tooling compatibility. Many data-loading utilities, spreadsheet imports, and analysis frameworks default to CSV — TSV requires explicit delimiter specification or doesn't work at all in some contexts. CSV is the lowest-common-denominator format that everything reads. Converting TSV to CSV makes data drop-in usable in the widest range of tools without configuration.
What happens to commas inside TSV cells?
They get properly escaped in the CSV output. TSV files often contain raw commas in cells (text fields, addresses, etc.) because tab is the delimiter — those values become safe in CSV by wrapping the cells in double quotes (`"value, with comma"`). The converter handles the escaping automatically; the CSV is RFC 4180-compliant.
Will my data values change in any way?
No. The cell values are byte-identical — only the field separator changes from tab to comma (with appropriate quoting for cells containing commas, quotes, or newlines). Numbers stay numbers (as text), strings stay strings, line breaks stay line breaks. The conversion is structurally lossless.
Will Excel and other tools open the resulting CSV correctly?
Yes — well-formed CSV opens correctly in Excel, Google Sheets, Numbers, every data tool. The converter produces standard RFC 4180 CSV with proper escaping. The one caveat: Excel's CSV parsing in some locales (particularly European with comma as decimal separator) may need semicolon-delimited CSV instead; if you're in such a locale and Excel mis-parses, use 'Data > From Text' to specify the delimiter explicitly.