CSV Korean Encoding Fixer
Fix garbled Korean in CSV files — convert between EUC-KR and UTF-8 (BOM).
Files never leave your device · Processed in your browser
Why Korean text gets garbled
When a CSV has no BOM (EF BB BF) at the start, Excel on a Korean Windows PC reads it as CP949 (an EUC-KR variant), the system default. Most CSVs exported from web services and developer tools are UTF-8 without a BOM, so opened in Excel, the Korean text turns into strange symbols. The reverse happens too: an EUC-KR file from an older business system looks broken when a modern program reads it as UTF-8.
If the file is meant for Excel, re-saving it as UTF-8 with BOM is the simplest fix.
How to use
Choose or drag in the garbled CSV file. The tool detects the encoding and shows the first 20 rows as a table. Once the text looks right, pick the Save as encoding and press Download. The saved file keeps the original name plus -utf8bom, -utf8 or -euckr.
If auto-detection guesses wrong and the text still looks broken, set the Source encoding to UTF-8 or EUC-KR yourself. The preview redraws right away.
Things to watch for
When saving as EUC-KR (CP949), emoji and some Hanja or special symbols cannot be represented and become a question mark (?). The tool tells you how many characters will change beforehand; if you need them, save as UTF-8. Only the encoding changes: content, line breaks and comma positions are left alone.