Online Tool Store
· 6 min read
Top 3 Text Encoding Detectors Worth Using
Heshan Fernando
Co-founder & COO
A CSV opens with é where every é should be, or a supplier’s export is a field of question marks. The file is fine; the encoding you opened it with is not.
Encoding is not stored in the file in any reliable way. A text file is bytes, and the same bytes mean different characters under UTF-8, Windows-1252 or Shift-JIS. Detection is therefore always a guess — an educated one based on byte patterns and, if you are lucky, a byte order mark. Tools differ in how good the guess is and how honestly they report their confidence in it.
How to judge an encoding detector
Does it give you a confidence score? Detection is probabilistic. A tool reporting one answer with no confidence is hiding the uncertainty rather than removing it.
Does it check for a BOM? A byte order mark at the start of a file settles the question outright. Any detector should look there first.
How many encodings does it know? UTF-8 and Latin-1 are easy. Cyrillic, Shift-JIS, GB2312 and Big5 are where a shallow detector confidently gives the wrong answer.
Can it take a file, or only pasted text? Pasting text through a browser re-encodes it, which can destroy the evidence. Reading raw bytes from a file is more reliable.
The comparison
| Tool | Best for | Free tier | Watch out |
|---|---|---|---|
| Monocalc Text Encoding Detector | Colour-coded confidence across 30+ families | Free, browser-based, 10 MB files | Pasted text is re-encoded before analysis |
| utils.com Character Encoding Detector | Clear BOM explanation and hex input | Free, reads files locally | Detects only — it doesn’t convert |
| Aback Tools Text Encoding Detector | Sitting beside repair and BOM removal tools | Free, no signup, client-side | Page doesn’t detail its detection method |
Facts checked August 2026; tools change their plans. Table covers only the 3 alternatives — our tool gets its own section below.
Monocalc Text Encoding Detector
The most rigorous about uncertainty, which is the right instinct for a task that is fundamentally a guess. It analyses raw bytes and returns likely encodings with a colour-coded confidence bar for each — green at 90% and above, yellow from 60 to 89, red below 60 — so a marginal call looks marginal instead of authoritative.
Input can be pasted text, an uploaded file up to 10 MB, or a hex byte string, and detection runs in three phases: BOM sniffing, multi-byte sequence validation, then byte-frequency analysis across more than 30 encoding families covering Unicode, ASCII, legacy Western and Cyrillic, and CJK. Free, no account, nothing uploaded. Note its own caveat that pasted text is re-encoded to UTF-8 for analysis — for a real diagnosis, give it the file.
utils.com Character Encoding Detector
The clearest explanation of what it is doing. It analyses text or hex byte sequences and identifies the most probable encoding among UTF-8, ASCII, ISO-8859-1, Windows-1252, UTF-16 in both byte orders and UTF-32 variants, and it explains byte order marks properly — that a BOM is an optional U+FEFF signature at the start of a stream identifying both encoding and byte order.
The file is read locally in your browser with nothing uploaded, and it is free with no account. Its stated limitation is that it detects only: once you know the encoding, converting the file is a separate job requiring a different tool.
Aback Tools Text Encoding Detector
Part of a large browser-based tool platform, and the advantage is what sits next to it: a BOM detector and remover, a line-ending fixer, and a Unicode and encoding repair tool. Diagnosing an encoding is rarely the end of the task, and having the repair tools one click away is worth more than a marginally better detector.
It states no signup, no premium tiers or usage limits, and 100% client-side processing via JavaScript and WebAssembly so files never leave your device, with UTF-8, UTF-16 and UTF-32 byte inspection. The page does not detail its detection method or whether it reports confidence, so treat those as unverified.
Text Encoding Detector
Ours previews encoding clues — UTF-8, UTF-16 and ASCII-friendly detection — in a plain browser-only interface. It is the quick triage version: enough to tell you whether you are looking at a Unicode problem or a legacy single-byte one, which is usually the fork in the road that decides what you do next.
What it does not do: report numeric confidence scores, cover CJK and Cyrillic legacy encodings, or accept hex byte input. For a Shift-JIS or GB2312 file, Monocalc’s wider coverage is the better tool. The W3C’s explanation of the byte order mark is worth reading if a BOM is what is breaking your file — it frequently is, particularly with CSVs.
Which one to pick
- An unfamiliar file from an unknown source — Monocalc, for the confidence scores and coverage.
- Understanding what a BOM is doing to your file — utils.com.
- You need to fix it, not just identify it — Aback Tools’ surrounding repair tools.
- A quick check of whether it is Unicode at all — the tool below.
How to do it with Text Encoding Detector
- Open the Text Encoding Detector and give it the text.
- Read the clues — a BOM, if present, is decisive.
- Reopen the file specifying the detected encoding rather than converting blindly.
- If the detection looks uncertain, get the original file rather than a pasted copy.
The walkthrough is in how to use Text Encoding Detector. Other developer tools are in the tools directory.
You might also need
For CSVs specifically — where mangled accents in a spreadsheet import are the classic symptom — the CSV Encoding Fixer does the repair rather than the diagnosis.
If the problem is a web page rather than a file, the Meta Charset Validator checks whether the page declares the encoding it is actually served in.
Frequently asked questions
Is there a free encoding detector that doesn’t upload my file?
Yes. Monocalc, utils.com, Aback Tools and ours all state that analysis happens in your browser. That matters here more than usual, since the files people need to diagnose are often exports full of customer data.
Why does my file show é instead of é?
Because UTF-8 bytes are being read as Windows-1252. In UTF-8, é is two bytes; interpreted one byte at a time as Windows-1252 they become à and ©. Seeing that specific pattern is a reliable sign of exactly this mismatch.
Can encoding be detected with certainty?
Only with a BOM. Otherwise it is inference from byte patterns, and short files give a detector very little to work with — which is why a confidence score is more useful than a single confident answer.
Final thought
Give the detector the original file, not text pasted through a browser. The paste already re-encoded the bytes, which means you are asking the tool to diagnose a copy that has had the evidence removed.