Text Encoding Converter
Decode an uploaded file from its source character encoding (Shift-JIS, Windows-1252, GBK and more), then re-encode it as UTF-8.
Tool guide
What this tool does
Text Encoding Converter decodes an uploaded file from a chosen source character encoding, UTF-8, UTF-16, Windows-1252, Shift-JIS, GBK, Big5 and more, using the browser’s native TextDecoder, and lets you download the result re-encoded as UTF-8, the modern universal standard.
A text file saved with an older, regional character encoding, Shift-JIS for Japanese, GBK for Chinese, Windows-1252 for Western European languages, looks like correct text to the program that originally wrote it, but opens as garbled "mojibake" nonsense anywhere expecting UTF-8, today’s near-universal standard.
This tool decodes an uploaded file using your chosen source encoding, via the browser’s native TextDecoder, which supports a wide range of legacy encodings, revealing the correct, readable text, and lets you re-save it as clean UTF-8.
How to use Text Encoding Converter
- Choose the Source encoding you believe the file was saved in.
- Upload the file to decode.
- Check the Decoded text looks correct and readable.
- Press Download to save it re-encoded as UTF-8.
Tips for better results
- If the decoded text still looks garbled, try a different source encoding, guessing correctly sometimes takes a couple of attempts if you don’t already know the file’s original encoding.
- Re-encoding for download is limited to UTF-8, since the browser’s native TextEncoder only writes UTF-8; converting back out to a different legacy encoding would need a dedicated encoding library.
- UTF-8 is backward-compatible with plain ASCII text and is the standard encoding expected by virtually all modern software, web pages and systems, making it the safest target for long-term compatibility.
- Common mismatches to try: Windows-1252 for old Western European Windows files, Shift-JIS or EUC-JP for older Japanese text, GBK or Big5 for Chinese text, KOI8-R for older Cyrillic/Russian text.
Common use cases
- Fixing a text file that displays as garbled nonsense (mojibake) due to a legacy encoding mismatch.
- Converting an old file saved in a regional encoding to modern, universally compatible UTF-8.
- Recovering readable text from a file whose original encoding isn’t immediately obvious.
- Standardising a batch of files from different legacy sources to one consistent encoding.
Common mistakes to avoid
- Guessing the wrong source encoding and assuming the file is simply unreadable; trying a few of the common legacy encodings (Windows-1252, Shift-JIS, GBK) often reveals the correct one quickly.
- Expecting to re-encode to a non-UTF-8 target for download; the browser’s native encoder only writes UTF-8, which is also the better long-term choice for compatibility anyway.
- Confusing a genuinely corrupted file with an encoding mismatch; if no source encoding produces readable text, the file itself may be damaged rather than just mis-encoded.
Frequently asked questions
What is "mojibake"?
Garbled, nonsensical-looking text that results from decoding a file with the wrong character encoding, the bytes are intact, but interpreting them with the wrong encoding rule produces the wrong characters.
Why can I only download as UTF-8?
The browser’s native TextEncoder API only writes UTF-8; re-encoding to a different legacy target would require a separate, dedicated encoding library beyond what’s built into the browser.
How do I know which source encoding to pick?
If you don’t already know it, try the most likely candidates for the file’s origin (Windows-1252 for old Western text, Shift-JIS for Japanese, GBK for Chinese, etc.) until the decoded text looks correct and readable.
Is my file uploaded anywhere?
No, decoding and re-encoding both happen entirely in your browser using native Web APIs; the file is never uploaded anywhere.
Feedback & suggestions
Help us improve Text Encoding Converter. We read every message.