File Tools. Local by design

CSV Encoding Converter

Make your text readable. Save a UTF-8 copy without changing your data.

Files stay on your device

Bring your file. Keep your characters.

or drop one CSV, TSV or TXT · up to 10 MiB

Choose a file or try the sample.

Already replaced with question marks? Lost characters cannot be recovered. This tool changes encoding; it does not translate text or repair every kind of corrupted file. CSV formulas are preserved as text here; spreadsheet apps may interpret them when opening a file.

Convert CSV to UTF-8 without changing your values

An incorrectly decoded export can show broken accents or symbols. Choose the source encoding that makes the preview readable, then save a UTF-8 copy. No file upload is required.

How to use this tool

  1. Choose one CSV, TSV or TXT up to 10 MiB, or try the built-in sample.
  2. Check the decoded text. If needed, select Windows-1252, GBK or UTF-16 manually. Table preview has its own delimiter setting.
  3. Choose UTF-8 without BOM for apps, or with BOM for Excel. Create and download your copy.

A practical example

A Windows-1252 export containing José and München can be converted to UTF-8. A customer ID such as 00123 stays 00123 in the file. Excel may still interpret values when opening CSV; import ID columns as text.

Frequently asked questions

Can this fix every garbled CSV?

No. You need the correct source encoding and original bytes. Characters already replaced with question marks cannot be restored. Double-encoded text may need a different repair process.

Should I use UTF-8 with BOM?

A BOM helps Excel recognize UTF-8. Some apps require UTF-8 without BOM. It does not change delimiters or guarantee that every regional Excel configuration opens columns correctly.

Does this change numbers, formulas or delimiters?

No. Text, whitespace, separators and line endings are preserved after decoding. The table delimiter changes the preview only. Formulas are not executed here, but spreadsheet apps may interpret them.

Is automatic detection certain?

No. A BOM or valid UTF-8 helps identify an encoding, but legacy encodings can be ambiguous. Windows-1252 is only a fallback candidate; always check the preview.