CSV Encoding Fix
CSV will not import because of its encoding — convert it to UTF-8
Your system refuses a supplier's CSV file because it is not saved as UTF-8, or the text arrives as garbled characters. Pick the file — its encoding is detected automatically, and you download the same file as UTF-8.
The file is processed locally in your browser and is not sent to the server. Only anonymous usage events are sent — never the file name and never its contents. No fingerprinting is used.
- File
- —
- Detected encoding
- —
- Result
- —
What this tool does
- What to choose
- One CSV or other delimited text file, in whatever encoding your supplier sent it.
- What happens
- The encoding is detected automatically, then the contents are re-encoded as UTF-8.
- What you get
- The same file as UTF-8 without a BOM. Delimiters, quotes, column order, the header row and the rows all stay as they were — only the encoding changes.
- Where the file goes
- Nowhere. Reading and re-encoding happen in your browser, and the file's contents are never sent to the server.
What this tool does not do
- It does not guarantee a successful import into any particular system — it solves the encoding problem only.
- Encoding detection is automatic and not always unambiguous. If a file cannot be recognised or is damaged you get an error rather than a corrupted result.
- Some rare encodings cannot be read by the browser (UTF-32, for example) — those show an error.
- It does not repair delimiters, quotes, column order, header rows or extra rows, and it is not a CSV editor.