How to use Text Encoding Fixer
- Paste the garbled text and keep a separate copy of the original.
- Choose common-sequence suggestions or a strict original character mapping.
- Run the repair and compare accents, symbols and unchanged sections.
- Copy the repaired result only after checking it against the intended wording.
Example: Text Encoding Fixer
Reverse a Windows-1252 interpretation of UTF-8.
Supported inputs and limits
- Up to 100,000 characters.
- Suggestion mode replaces selected common garbled sequences while preserving other text, including correctly decoded scripts.
- It does not detect every original encoding.
- Explicit Latin-1 and Windows-1252 modes map visible characters back to bytes and then decode strict UTF-8.
- Those modes refuse unmappable characters and invalid reconstructed UTF-8 rather than inserting replacement characters.
More details
Missing bytes and details already lost to replacement characters cannot be reconstructed.
Keep the original and compare the result with the intended wording.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
A reversal needs the earlier bytes
Mojibake often appears when UTF-8 bytes were read as a single-byte encoding. A supported repair maps those visible characters back to their earlier byte values, then decodes the bytes strictly as UTF-8. It cannot reconstruct information that was already discarded.
Questions about Text Encoding Fixer
Can it repair every garbled document?
No. It reverses a specific supported encoding mistake. Missing bytes, replacement characters and a mix of correctly decoded and garbled text may not be recoverable.
How do Latin-1 and Windows-1252 differ here?
Their mappings differ for several byte values, including punctuation and the euro sign. This tool treats the two modes explicitly rather than relying on the browser's Latin-1 label.
Why does the repair refuse my input?
A character cannot map back to a byte in the selected mode, or the reconstructed bytes are not valid UTF-8. The page refuses that conversion instead of silently inserting replacement characters.
Should I repair text that already looks right?
Keep correctly decoded text unchanged. Applying the wrong reversal can damage valid wording; use the comparison rather than treating repair as automatic cleanup.