CSV encoding converter
Convert a CSV or TSV from Windows-1252, UTF-16, Shift JIS and other selected text encodings to UTF-8 for Excel and spreadsheet imports.
Your results
CSV encoding converter
Accented names or non-Latin text can look garbled when a CSV export is opened with the wrong character encoding. Upload the original CSV or TSV, select the encoding used by the source program, and check the decoded rows before downloading UTF-8. Choose a UTF-8 BOM when opening the file directly in Excel, or omit it for a system that expects plain UTF-8. The column separator stays the same. This tool converts source bytes; it cannot restore characters that were replaced with question marks before the file was saved.
How to use this tool
- Upload a CSV or TSV export, drag it into the dropzone, or import a direct public file URL. Try the Windows-1252 example if you do not have a file.
- Select the source encoding and column separator. Check names and non-Latin characters in the preview; change the source encoding if they look wrong.
- Choose whether Excel needs a UTF-8 BOM, then download the UTF-8 CSV or TSV and check it in the destination application.
Supported input formats
CSVTSVTXT
Available settings
- Source encoding
- Column separator
- UTF-8 BOM for Excel
Output and limitations
Convert a CSV or TSV from Windows-1252, UTF-16, Shift JIS and other selected text encodings to UTF-8 for Excel and spreadsheet imports.
Choose the source encoding yourself, then check accented or non-Latin characters in the preview. CSV files generally do not identify their encoding, so automatic guessing can be wrong. The tool accepts one file up to 5 MB and 10,000 rows with 100 columns. It reads comma, semicolon, tab or pipe separators, reserializes the same columns, and writes UTF-8 with an optional BOM for Excel. It skips blank rows and escapes formula-like cells for spreadsheet safety. It cannot recover characters already replaced with question marks or reliably repair text that was corrupted before export. Nothing is uploaded unless you explicitly use URL import.
Will a UTF-8 BOM fix characters that already appear as question marks?
No. If the source bytes contain literal question marks where letters once were, those letters cannot be reconstructed. A BOM helps some versions of Excel recognize UTF-8 at import; it does not repair data already lost in the source file.
Can this automatically detect the original CSV encoding?
No. CSV normally has no encoding declaration. A BOM identifies some Unicode files, but many other encodings have overlapping byte values. Select the known source encoding and verify the preview instead of relying on a guess.
What if processing fails?
Check the supported formats and file limits, then try a smaller file. Keep an original copy. A clear error message will explain an unsupported input or an unavailable processing service.