Text looks garbled
The file may be decoded with the wrong encoding. Try UTF-8 or GB18030 and check the preview. A UTF-8 BOM export can help spreadsheet apps recognize Unicode.
A LITTLE ORDER FOR YOUR DATA
Messy CSV.
Clean handoff.
Open the file, find the problem, export with confidence. Fix encoding and delimiters without sending your data to a server.
Processed on your deviceFree · No sign-in
01 / Bring your data
First row is treated as column headers.
02 / Check & export
WAITING FOR DATA—data rows
—columns
—separator
▦
A clearer view starts here.
Load a file or try the sample.Preview shows the first 12 data rows.
KNOW WHAT YOU ARE FIXING
Three common CSV headaches, explained.
Everything lands in one column
The separator may be a semicolon or tab instead of a comma. Choose the matching input separator, then export with the delimiter your next tool expects.
IDs lose digits or leading zeros
This tool keeps cells as strings. CSV cannot store cell types: import ID columns as Text in your spreadsheet app. Digits already lost in a saved file cannot be reconstructed.
Before you export
Are the files uploaded?
No. File decoding, CSV parsing, and export happen in your browser. Close or clear the page to remove the loaded data from this tool's memory.
Does adding a BOM fix every encoding problem?
No. A BOM identifies UTF-8; it cannot repair text that was already saved incorrectly. Choose the correct source encoding before exporting, and inspect the preview.
How are JSON headers and empty cells handled?
The first row supplies property names. Blank headers become column_1, column_2, and so on; duplicate names receive a numeric suffix. Missing cells become empty strings, and extra columns receive generated names.
What does formula protection change?
CSV cells beginning with formula markers such as =, +, -, or @, including leading whitespace, receive an apostrophe. Spreadsheet behavior varies, so review untrusted files. JSON exports always preserve the original strings.