Detect whether a CSV is UTF-8 or Korean EUC-KR (CP949), compare both readings side by side, and save it as UTF-8 with a BOM so it opens correctly in spreadsheet apps.
Your files are processed right here in your browser. Nothing is uploaded or stored on a server.No library — uses the browser’s built-in TextDecoder
Good to know. Characters already saved as � can't be recovered. Files are saved as UTF-8 (with BOM) only. Very large files may be slow.
A BOM is a small marker at the very start of the file that says “this is UTF-8”. With it, spreadsheet apps open the file correctly on double-click. Saving back to EUC-KR isn’t offered: the browser’s TextEncoder can only produce UTF-8, and nearly every program today reads UTF-8 with a BOM.
The file is in one encoding (say UTF-8) but the app reads it as another (say EUC-KR), or the other way round. Adding a BOM to a UTF-8 file lets most apps recognize it.
No. The browser’s TextEncoder only produces UTF-8, so EUC-KR output isn’t supported. Nearly every modern app reads UTF-8 with a BOM.
Characters already replaced by � have lost their original data and can’t be recovered. Only files that are simply read with the wrong encoding can be fixed.