Skip to content

Encoding Detector & Converter

Guesses a file’s character encoding — CP949, Shift_JIS, GB18030, Windows-1252 and more — with a side-by-side preview of each candidate, then re-saves it as UTF-8 (with or without BOM), UTF-16 or EUC-KR/CP949.

Drops a text file and shows you what it decodes to under each candidate encoding, side by side, so you can pick the one where the text reads correctly. It reads UTF-8, UTF-16, CP949, Shift_JIS, GB18030, EUC-JP, and Windows-1252 and saves as UTF-8, UTF-8 (BOM), UTF-16 LE (BOM), UTF-16 BE (BOM), and EUC-KR / CP949, with the line endings converted if you need — a longer list going in than coming out, because what a legacy system wrote is not what anything should be written in now.

🔒 Runs entirely in your browserencodingcharsetutf8convert

Drop a text file here

CSV, subtitles, logs, source — any text file. It does not leave this tab.

Or paste the text

Pasted text is already decoded, so there is nothing to guess — only the encoding to save it as.

Korean showing as °í°´¸í means a CP949 file was read with another table; ê³ ê° means a UTF-8 file was read as Latin-1. Whichever candidate shows Hangul correctly is the source encoding.

Text that was already saved broken — where you have the text but not the original file — is what the "깨진 한글 복구" tool undoes.

How to use it

  1. Drop the file

    CSV, subtitles, logs, source — anything text. A BOM at the front settles the question outright and is reported as such.

  2. Choose the candidate where Korean reads

    Each candidate shows a preview and how many characters it could not read. Machine detection is a guess; your eyes are not.

  3. Pick the encoding to save as

    UTF-8 for anything modern; UTF-8 with BOM when Excel has to open the CSV; EUC-KR only when an old system demands it. The panel says how many characters that encoding cannot hold before you save.

Common questions

My Korean shows as °í°´¸í

A CP949 file read with a Western table. Pick the CP949 or EUC-KR candidate. If it shows as ê³ ê° instead, that is a UTF-8 file read as Latin-1 — pick UTF-8.

Excel opens my UTF-8 CSV as mojibake

Excel on Windows assumes the system code page unless the file starts with a BOM. Save as "UTF-8 with BOM" and it opens correctly, at the cost of three bytes some Unix tools show as characters.

Some characters became question marks

EUC-KR has no code for them — emoji, some Han characters, most European letters. The list is shown before you save. If you need those characters, UTF-8 is the only answer.

I only have the broken text, not the file

Then this is the wrong tool — it works on bytes. The 깨진 한글 복구 tool takes the mojibake itself and reverses the decoding that produced it.

Feed it from

Next

These accept what this tool produces, so the result can go straight in.