Text Encoding Fixer

Suggest common garbled-text repairs or reverse an explicit Latin-1 or Windows-1252 mistake.

On-device No sign-up Free to use

Repair encoding controls

Showing an example. Edit to see your own.

?

Up to 100,000 characters. The text is reinterpreted as bytes, then decoded as UTF-8.

?

Automatic mode changes only recognizable sequences, keeps the rest and needs review. Or choose the original single-byte mapping yourself. Browsers treat labels such as Latin-1 and ISO-8859-1 as Windows-1252; this Latin-1 option uses the true one-byte-to-one-code-point mapping.

Processed in your browser. Your inputs stay on this device.

Result

Showing an example.

Reverse a Windows-1252 interpretation of UTF-8.

The strict reversal returns café and € without replacement characters.

Loading the tool. Your result will appear here.

https://usefreetools.net/text-encoding-fixer · 20 November 2026

Was this helpful?

How to use Text Encoding Fixer

  1. Paste the garbled text and keep a separate copy of the original.
  2. Choose common-sequence suggestions or a strict original character mapping.
  3. Run the repair and compare accents, symbols and unchanged sections.
  4. Copy the repaired result only after checking it against the intended wording.

Example: Text Encoding Fixer

Reverse a Windows-1252 interpretation of UTF-8.

You add
Text: café and €. Source interpretation: Windows-1252.
You get
The strict reversal returns café and € without replacement characters.

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.

Page updated · Project managed by Tony Hines · Report a problem with Text Encoding Fixer

Related reading

All guides