Mojibake Fixer

This is a repair tool, not a Unicode or text-code representation converter. Processing uses browser-side TextEncoder and TextDecoder logic.

Repair mojibake

1. Paste garbled text into the input textarea. You can also click Upload to choose a text file, or drop a file onto the input area. Dropped content is read as text.
2. Review the Suspected Repair Path & Candidates panel. It lists the supported paths found for the input and their displayed corruption scores.
3. The lowest-scoring candidate is marked Suggested and selected automatically only when its score improves on the original. Otherwise, Keep original text (no repair) remains selected. You can choose another radio-button candidate.
4. Inspect the readonly output textarea. Selecting an option updates it immediately. A repair candidate also updates the Preview - What Changes panel.
5. Use the output textarea's Copy or Download control to take the result.

The read-only output mirrors the selected option immediately. There is no separate commit step: review the candidate and preview, then use Copy or Download when the result is ready.

Review candidates and preview changes

The displayed score is a weighted heuristic corruption score. A lower score is a cleaner ranking signal, not a direct count of remaining signatures. It is not a grammar, spelling, or semantic check, so inspect the candidate before copying it. The stats line reports the original Corruption score, any replacement-character count, and the number of candidates found.

Preview - What Changes normally shows a token-based comparison with changed candidate text highlighted. It may not show every deletion as an explicit character-level change. For inputs whose token arrays exceed 250000 pairs, the page uses an escaped candidate preview instead of the normal diff. That fallback is limited to 4000 characters and adds [preview truncated] when needed.

These transformations are applied to the input as a whole. Clean text will generally remain unchanged when it survives the selected byte transformation, but check the output and preview for the text you supplied.

When no repair candidate is shown

• The text may already be clean.
• No common encoding-misinterpretation pattern may be detected.
• Unicode replacement characters may indicate that some original bytes were already lost.

When no repair is appropriate, select Keep original text (no repair). There is no established maximum input size on this page; the confirmed size behavior concerns the preview fallback above.

Input and output limitations

• Upload and page-wide drop use the shared text-file input. The picker accepts .txt, .csv, .log, and .md files, which are read as text in the browser; unsupported file types show an error and leave the current text intact.
• The page does not establish browser or platform compatibility details.
• The output is readonly and can be copied or downloaded after you select an option.

Frequently Asked Questions (FAQs)