CSV encoding fixer
Your input is processed only in this browser. See the privacy policy.
How to use it
- Drag your CSV file onto the box above, or click the box and choose it. No file at hand? Press a Try a sample file button or paste the content under Paste text.
- Under Encoding candidates, compare each candidate's confidence, broken-character count and five-row preview. The best match is already selected; pick another one if its preview reads better. Then check the column counts of the Delimiter candidates and say whether the first row is a header.
- In the Result preview, check that the first 200 rows split into the right columns. Choose an output (Excel, UTF-8 or CP949) and press Download, or use Copy as TSV to paste straight into a spreadsheet.
Examples
Korean text turns into question marks in Excel
A CSV exported as UTF-8 without a BOM shows Korean as garbage when opened in Excel for Windows. Drop the file here, keep the Excel output, and download. The copy has the three-byte BOM that tells Excel the file is UTF-8, and the Korean text opens correctly.
A file from a Korean system opens as nonsense in a UTF-8 tool
Banks, government sites and older Korean software often export EUC-KR (CP949). The tool detects that automatically and converts to UTF-8, so the same file now reads correctly in Python, databases and web apps.
- Input
C0 CC B8 A7 2C B3 AA C0 CC (EUC-KR bytes)
- Result
이름,나이 (after conversion to UTF-8)
Details
A CSV file is only text, but the file does not say which character encoding that text uses. Excel has to guess, and for files without a byte order mark (BOM) it usually assumes the legacy code page of your Windows installation. A UTF-8 file with Korean, Japanese or accented letters then appears as garbled symbols, while an EUC-KR file opened in a UTF-8 tool shows replacement characters.
Detection works in order. A BOM settles it immediately. Without one, the tool checks whether the whole file is valid UTF-8, which is a strong signal because Korean text in EUC-KR almost never happens to form valid UTF-8 by accident. If it is not, the file is read as EUC-KR (CP949) and judged by how many bytes cannot be decoded and how much of the text is Hangul.
The delimiter is guessed by reading the first rows with each candidate (comma, tab, semicolon and pipe) while respecting quotes, and picking the one that splits every row into the same number of columns. Fields are parsed as RFC 4180 describes: a field in double quotes may contain delimiters and line breaks, and a doubled quote stands for one quote character.
Frequently asked questions
Is my file uploaded anywhere?
No. The file is read and converted inside your browser, and the tool does not send the file or its contents to a server.
What is a BOM and do I want one?
A BOM (byte order mark) is three bytes at the very start of a UTF-8 file that announce the encoding. Excel for Windows relies on it to open UTF-8 CSV correctly.
The preview still looks wrong after conversion. What now?
Pick another card under Encoding candidates, or choose an encoding under Read with another encoding, and watch the preview change. A file can have been saved wrongly before it reached you, for example Korean text already replaced by question marks, and no tool can bring those characters back.
Excel still removes the zeros at the start of my numbers.
That comes from Excel turning text that looks like a number into a number, not from encoding. In Excel use Data, then From Text/CSV, and set the column type to Text before loading.
How big a file can I convert?
Files of several megabytes convert in about a second. Very large files depend on your device's memory because the whole file is held in memory while it is read and converted.