Charset Converter — Fix Mojibake
Fix mojibake — decode legacy code pages such as Windows-1252, ISO-8859, Shift_JIS, EUC-KR, GBK, Big5 and KOI8-R to Unicode. Free, no upload, in your browser.
🔒 Decoding runs entirely in your browser with the native TextDecoder — your bytes and files are never uploaded, and it works offline.
Turn garbled text back into readable characters
When a file or database was saved in a legacy code page — Windows-1252, ISO-8859, Shift_JIS, EUC-KR, EUC-JP, GBK, GB18030, Big5 or KOI8-R — but later read as UTF-8 (or the wrong code page), you get mojibake: café turns into café, and Korean shows up as ÇѱÛ. Paste the raw bytes as hex or Base64, or drop the file, choose the charset the bytes were originally written in, and read the correct Unicode text instantly.
How it works
Everything runs on the browser-native TextDecoder, which implements the WHATWG Encoding Standard — the same decoder your browser uses to render web pages. There is no library and no server round-trip, and it works offline, so your bytes never leave your device.
Frequently asked questions
What is mojibake?
Mojibake is garbled text that appears when bytes encoded in one character set are decoded as another — for example, legacy Windows-1252 or EUC-KR bytes read as UTF-8. Choosing the correct source charset here restores the original characters.
Which encodings are supported?
Every code page the browser TextDecoder supports, including Windows-1250 to 1258, ISO-8859-2/5/6/7/8/13/15, KOI8-R and KOI8-U, Mac Roman, Shift_JIS, EUC-JP, EUC-KR, GBK, GB18030 and Big5. UTF-8 is included too so you can verify already-correct bytes.
How do I get the bytes of my text?
Paste them as hex (like 48 65 6c 6c 6f) or Base64, or switch to Upload file and drop the file directly — the tool reads its raw bytes and decodes them with the charset you pick.
Is my data uploaded?
No. All decoding happens locally in your browser via the native TextDecoder, so your bytes and files stay on your device and it works offline.