Convert tab-separated values to comma-separated format with proper escaping.
Enter your tab-separated data or upload a TSV file.
Click convert to transform tabs to comma-separated values.
Save or copy the converted CSV output.
Tab-separated data looks harmless: fields side by side, tabs between them, easy to copy out of any spreadsheet. The catch is that most software that consumes tabular data - database importers, web forms, analysis scripts - expects commas, and a comma sitting inside a value would be read as a column break. This page takes TSV input and emits CSV with the escaping that keeps the data intact: fields containing commas or quotes are wrapped in double quotes, and embedded quotes are doubled. The usual surprise is that the quote marks in the output are the conversion working correctly, not damage to your data.
A concrete input and expected output from the current implementation.
Input
name age note Ada 36 likes "tea", scones
Expected output
name,age,note Ada,36,"likes ""tea"", scones"
The note field contains a comma and double quotes, so it is wrapped in quotes and its internal quotes are doubled. The header and the other two fields contain no special characters and pass through unchanged.
Every tab in the input marks a column boundary. When a field moves to the output it is checked against the CSV convention in RFC 4180: if the field contains a comma, a double quote, or a line break, it is wrapped in double quotes and every quote inside it is doubled. A field with none of those characters is copied verbatim, so clean data comes out clean.
Conversion is line-based: each input line becomes exactly one output row, in the same order, with no header invented and no columns added, removed, or reordered. Because strict TSV forbids tabs and newlines inside fields, a value that spans two lines in the input is two records, not one, and rows whose field counts differ come through uneven, leaving column alignment to the reader.
Because those values contain commas or quotes, and in CSV an unquoted comma means the next column - a value like likes "tea", scones would otherwise split into two columns. Wrapping it in quotes, doubling any internal quotes, tells a reader to treat the whole thing as one field, and the reader removes the quotes when it parses.
For data with no commas, quotes, or line breaks inside values, yes - the result is identical, and for small clean files that is often faster. The moment a value contains a comma, a plain replace creates a new column boundary and shifts everything after it. Preventing exactly that corruption is why the escaping exists.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Convert CSV data into structured JSON arrays or objects with automatic type detection.
Transform JSON arrays and objects into downloadable CSV spreadsheet format.
Convert YAML configuration files to JSON format with validation and formatting.
Parse XML documents and convert them to equivalent JSON structure with attributes.
Convert numbers between binary, octal, decimal, and hexadecimal bases.
Convert between Roman numerals and Arabic numbers with validation.