Convert TSV to CSV without shifting cell boundaries
Re-save a tab-separated spreadsheet when the receiving system accepts CSV. A field can contain commas or line breaks of its own, so replacing every tab with a comma in plain text would not be enough to preserve cell boundaries.

How to use this tool
- Choose files in TSV, TXT format. Maximum files per batch: 1.
- Review Input encoding, then start processing.
- Download the CSV result and check its content and quality.
Choose the right settings
Check whether the source uses UTF-8 or an EUC-KR-compatible encoding and choose it accordingly. Input fields are read with tabs, while the saved CSV uses commas as its separators.
- Supported input
- TSV, TXT
- Output
- CSV
- Available settings
- Input encoding
Before you start
Establish the meaning of the input
Before converting or arranging data, identify what a row or value represents and keep a source copy. In tabular files, review headers, separators and text encoding; in structured files, inspect the required object or array shape. Identifiers, dates and amounts should not be interpreted solely from how a spreadsheet happens to display them.
Where the tool offers matching columns, type rules or output fields, choose them according to the destination’s requirements. Test a sample with a blank, a repeated value and a value containing punctuation. For labels, charts or personalized documents, check which column supplies each displayed value and whether the source units and wording are correct.
Define a few checks before processing: an identifier that must retain its spelling, a value with a known interpretation and an expected relationship between records. If the tool offers type conversion or matching rules, distinguish a source value from the program’s display of it. Test ambiguous dates or differently written keys before accepting a broad rule. Keep the chosen rules and destination requirements with the result; this makes a discrepancy traceable to input, interpretation or the requested transformation.
Verify values, structure and exceptions
Reopen or import the result using the destination’s settings. Compare headers, record counts and several values with the source, allowing for the operation you requested. A summary, split or duplicate-removal task can legitimately change the count; verify why it changed rather than expecting every transformation to keep identical rows.
Inspect any exception or validation report before continuing. If columns shift, characters are garbled or a key is not found, check delimiters, encoding and exact header spelling first. Encoding data does not encrypt it, and formatting a value does not confirm its meaning. For printed codes or labels, test the actual output before making the full set.
Example input and output
tab-separated name/count → comma-separated CSVExamples describe the workflow. Results depend on the source file and settings.
Check the saved result before using it
Compare the header width and number of data rows with the source. Inspect an address containing commas or a description containing quotes to confirm that each remains one cell.
If the result is different from what you expected
Unclosed quotes or nonstandard field syntax can cause parsing errors. If the output appears in one column, check that the receiving application's import settings also use a comma delimiter.
Limits to keep in mind
- Quoted delimiters and newlines need valid input syntax. Formula-like cells are escaped in the result.
Continue with a related tool
This guide explains the public browser tool. Keep a copy of the original and inspect the result before sharing it.