TSV to CSV Converter

TSV means tab-separated values. It stores each row on a line and separates columns with tab characters rather than commas. TSV is common when copying cells from spreadsheets because tabs can separate columns without conflicting with commas used inside ordinary text.

A TSV to CSV converter reads tab-delimited rows and writes them as comma-separated or other delimiter-separated records. ToolsSonic parses TSV in your browser, applies configurable quoting and line-ending rules, shows the parsed table, and creates a CSV file that can be copied or downloaded.

Yes. ToolsSonic processes pasted TSV and local TSV files entirely in browser memory. The converter does not upload rows to a server, call a remote conversion API, save persistent history, or fetch a URL. Your data never leaves your device.

Yes. A tab inside a quoted field is treated as cell content rather than a column separator. The parser also recognizes doubled double quotes and line breaks inside quoted fields, so a notes field can contain tabs or multiple lines without shifting later columns.

When a TSV value contains the selected output delimiter, such as a comma, the converter quotes that field and doubles any embedded double quotes. This prevents a comma in an address, description, or note from being interpreted as a new CSV column.

RFC 4180-style CSV conventionally uses double quotes around fields that contain the delimiter, double quotes, or line breaks. A double quote inside a quoted field is represented by two double quotes. ToolsSonic uses these rules in Minimal quoting mode and lets you choose more conservative modes when needed.

Yes, provided the multiline value is enclosed in double quotes. The TSV parser keeps line breaks within a quoted field and the CSV serializer quotes the resulting field so the output remains parseable. An unclosed quote is reported as a warning for review.

Yes. The output delimiter can be comma, semicolon, or pipe. Commas are the conventional CSV choice, semicolons work better in locales where commas are decimal separators, and pipes are useful for text-oriented interchange when commas are frequent in the data.

CRLF is commonly associated with Windows and legacy spreadsheet workflows. LF is common on Unix, Linux, macOS, and developer tooling. If an import system is sensitive to line endings, select the format it documents and verify the first and last records after export.

Keep first row as header preserves the first TSV row as the first output row and uses it for the preview label. No header row treats every parsed row as data. Generate header row adds Column 1, Column 2, and similar labels before the data rows when the source has no column names.

Minimal quoting protects only values that need quoting. Quote all fields wraps every cell in double quotes. Quote non-numeric protects text-like values while leaving numeric-looking values unquoted. Never quote is provided for review or specialized dialects and can create ambiguous CSV when values contain delimiters, quotes, or line breaks.

When Trim outer cell whitespace is enabled, leading and trailing whitespace around each parsed cell is removed before serialization. Whitespace inside the value remains. Disable trimming when spaces at the start or end of a cell are meaningful, such as fixed-width codes or intentionally padded text.

The converter calculates the widest parsed row and reports a warning for every row whose field count differs. Missing cells are represented as empty output fields so you can inspect the generated CSV, but the warning means the source should be reviewed before production import.

Yes. Copy cells from Excel, Google Sheets, LibreOffice, or another spreadsheet and paste the tab-separated text into the input, or open a local TSV or text file. Confirm the first row, delimiter, line ending, and quoting policy, then inspect the table preview before downloading.

Yes. Copy CSV places the current output on the clipboard, and Download .csv saves a local file named converted.tsv-to-csv.csv. The download is created in the browser and does not require a server-side conversion job.

No. It treats cell contents as text and never executes formulas, macros, scripts, external links, or database statements. Spreadsheet applications may interpret cells beginning with formula characters when you open the output, so review untrusted or user-generated content before opening it in a spreadsheet.

The practical limit depends on available browser memory because the input, parsed rows, preview, and generated CSV are held in page memory. Browser conversion is convenient for ordinary exports; use a streaming command-line or data-pipeline workflow for very large files and validate the result separately.

No. TSV uses tab characters as separators, while CSV commonly uses commas, although real-world CSV dialects also use semicolons or other delimiters. Both formats can use quoted fields, but the input separator and output rules must be interpreted correctly to avoid shifted columns.

A UTF-8 BOM (byte order mark) is a hidden three-byte sequence at the start of the file that tells some Windows applications, including older versions of Excel, that the file is UTF-8 encoded. Enable it when importing into Excel or a system that requires explicit encoding detection. Most developer tools and modern spreadsheets do not require it.

The tool is designed as a free browser utility with no account required. TSV parsing, CSV generation, statistics, preview, copy, and download run locally without a remote conversion service or persistent data storage. Always consider clipboard permissions and shared-device access when handling sensitive data.