Text Encoding Detector
Check a text file for a Unicode signature, valid UTF-8 or likely legacy encodings. Compare decoded previews and export UTF-8 text.
Identify a Legacy Receipt’s Text Encoding
Text Encoding Detector: how to use it
- Open the original file and choose Inspect encoding. Paste only when you want to check the UTF-8 bytes of text already in the browser.
- Read the signature, strict decoding or statistical evidence. Compare likely encodings in Preview as.
- Use the familiar words, punctuation or source settings to choose a decoding. Download the decoded UTF-8 text or save a JSON report.
Limits and notes
Files up to 5 MiB and pasted text up to 100,000 UTF-16 units. Supports exact checks for UTF-8 and UTF-16 or UTF-32 signatures. Legacy model scores sample the first 64 KiB and are heuristic. Browser decoders determine which previews are available. Short and ASCII-only files can remain ambiguous.
How your privacy works →Text Encoding Detector: common questions
Can pasted text tell me whether the original file used Windows-1252?
Pasting gives the browser text that was already decoded. Select File bytes and open the original to check its encoded bytes.
Why does the report say ASCII-compatible bytes?
All bytes are in the ASCII range, which UTF-8 and many legacy encodings share. The same bytes can come from several source encodings.
Can a byte-order mark appear before damaged text?
Yes. The tool checks the bytes after the mark. If they are invalid, it reports the signature and the decoding problem separately.