Code · Made a little simpler

CSV Encoding Detector

Check a CSV for a byte-order mark, valid Unicode or evidence about legacy encodings. Choose a source encoding and separator, then preview its records and save the same text in UTF-8.

Free to useNo account neededProcessed on your device
Your workspaceProcessed on your device

Add this tool to your website

Paste this code into your page to add the tool and a visible ToolMellow credit link.

HTML embed code
Preview embed

CSV Encoding Detector: how to use it

  1. Open the original CSV file or load the example to give the checker its original bytes.
  2. Inspect the file and read the encoding evidence. For ambiguous results, select a source encoding and inspect again. Choose the original separator to check the fields.
  3. Check the decoded records and download the UTF-8 copy. Reopen it with the same separator and import text identifiers as text.

Limits and notes

Reads local files up to 5 MiB, with a preview parser limit of 4,194,304 decoded UTF-16 code units and 250,000 cells. Supports comma, semicolon, tab and pipe. The export keeps source separators, field quoting, line endings and record order. It removes the detected original signature and adds no UTF-8 signature.

How your privacy works →

CSV Encoding Detector: common questions

Can CSV bytes distinguish Windows-1252 from ISO-8859-1?

Overlapping character bytes can decode the same way in both. In the example, hexadecimal 80 represents a euro sign in Windows-1252 and a control in ISO-8859-1. Use the export settings or known text to confirm the choice.

Does a byte-order mark prove the entire CSV is valid?

The mark identifies a Unicode encoding. The tool also checks the remaining bytes and parses the records using the selected separator.

Will converting to UTF-8 change 001 or 1.2300?

The download keeps both as written. Choose text import for identifiers if your spreadsheet automatically converts numbers.

Guides