Add Suffix
Put the same text at the end of every line.
Decode UTF-8 bytes and fix mojibake.
The UTF-8 Decoder does two jobs: it decodes a list of UTF-8 bytes back into text, and it repairs mojibake — the é and ’ that appear when UTF-8 is read as Latin-1. The second is what most people arrive looking for, and it fixes most real cases in one pass.
Mojibake is what you get when UTF-8 text is read as if it were Latin-1: café becomes café, a curly apostrophe becomes ’, and an em dash becomes —. It happens constantly in database migrations, CSV imports and badly configured feeds, and once you recognise the pattern it is entirely repairable.
This tool does two things. It decodes a list of UTF-8 bytes back into text, in hex, decimal or percent-encoded form. And it repairs mojibake by reversing the mistaken decoding — reading the mangled characters back as bytes and decoding them properly as UTF-8. That second function is the one people actually arrive looking for, and it fixes the great majority of real cases in one pass.
Reverses the mistaken Latin-1 read and decodes the bytes properly, which fixes the great majority of real cases.
How many recognisable mojibake sequences were found, so a low count warns you the text may be fine already.
Hex, decimal and percent-encoded byte lists all decode back to text.
Bytes that do not form valid UTF-8 are named rather than silently becoming replacement characters.
The page explains that text saved again in a lossy encoding has genuinely lost characters no tool can recover.
A list of UTF-8 bytes, or text full of é and ’.
Decode bytes, or repair mojibake by reversing a mistaken Latin-1 read.
The correct text appears, with any invalid sequences reported.
The tool counts how many mangled sequences it recognised, so you know it found the real problem.
Reading UTF-8 bytes as if they were a single-byte encoding, usually Latin-1 or Windows-1252. The two bytes of an é get read as two separate characters, Ã and ©, which is exactly what you see.
Most of it. The repair works when the mangling was a clean UTF-8-read-as-Latin-1 mistake. If the text was then saved again in a lossy encoding, some characters are genuinely gone and no tool can recover them.
It is a curly right single quotation mark (U+2019) whose three UTF-8 bytes were read as three Windows-1252 characters. It is the single most common piece of mojibake in English text.
If the text was not actually mojibake, reversing the decoding corrupts perfectly good characters. The tool reports how many recognisable mojibake sequences it found, so a low count is a sign to leave the text alone.
What people who use the UTF-8 Decoder think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the UTF-8 Decoder. It takes half a minute and no account.
Write the first reviewPut the same text at the end of every line.
Rank every word and phrase in your text by how often it appears.
Turn text into ꜱᴍᴀʟʟ ᴄᴀᴘꜱ that paste anywhere.
Rank single words, pairs and triples by how often they appear.
Strip indentation so every line starts at the left margin.
Turn Unicode escape sequences back into characters.
Write in aLtErNaTiNg cApS for the mocking SpongeBob effect.
Compare two texts word by word and see exactly what changed.