MakeFileWork

Convert CSV to TSV without losing fields

Change the separator of a UTF-8 table while keeping cell values, quoted line breaks and accented text intact.

What this tool actually does

CSV → TSV creates a new file in the target format; it does not merely rename the extension. MakeFileWork processes the source in the browser where this conversion supports local execution and keeps the job bounded so a single file cannot consume unlimited memory or CPU.

How the result is verified

Before download, the engine re-serializes, reopens, parses or otherwise checks the output according to the format. The result shows concrete evidence such as pages, structure, extracted text or generated format instead of treating any downloadable blob as a successful conversion.

Limits and fidelity

Formats do not represent every feature in the same way. Layout, fonts, animation, formulas, metadata, transparency or interactive elements can change when the destination cannot preserve them. The tool does not promise fidelity that the target format cannot support and calls out known trade-offs.

When to use this workflow

Use this workflow when another application, device or upload portal requires the target format and you need a newly generated, verifiable file. If the rejection also specifies KB/MB, pixel dimensions or other measurable limits, use the upload-requirement workflow to validate those constraints together.

Privacy and final verification

Keep the original file until the output has been reviewed in the destination application or portal. Supported workflows process locally in the browser and enforce bounded size and complexity limits. For CSV → TSV, verify that the generated format preserves the properties that matter for your use case. For important data, compare a representative sample and confirm that format, content and quality meet the actual requirement before replacing the source file. Also open the generated file in the destination application when compatibility, colour, transparency, layout or compression matters.

When TSV is useful

TSV separates columns with tabs instead of commas. It is useful when text fields contain many commas or when a data-import tool specifically requests tab-delimited input. Changing the separator does not change the meaning of the values or create an Excel workbook.

How the conversion checks your data

Upload a CSV file with comma, semicolon or pipe delimiters. The converter infers the source separator, parses quoted cells and multiline values, then serializes a TSV. It reparses the generated TSV and compares every row and cell against the parsed input. A successful comparison checks structural preservation, not whether the original columns were correctly chosen in an ambiguous file.

Example: names with commas and newlines

A quoted value such as “García, Ana” remains one cell. A line break inside a quoted description stays inside that same cell. The output uses UTF-8 with a byte-order mark and CRLF row endings; quoted tabs, quotation marks and embedded newlines are escaped.

Limits and spreadsheet safety

Files are limited to 10 MiB, 50,000 rows, 200 columns and 100,000 characters per cell. Malformed UTF-8, NUL bytes and formula-like spreadsheet cells are rejected rather than silently altered. A file mixing separators can be ambiguous: inspect the first rows before trusting automatic delimiter inference.

Related tools

To reverse the format use TSV to CSV. For a malformed table use repair CSV; to split a large file into byte-exact parts use split text files.