Fix garbled characters (mojibake) in an old subtitle file locally in your browser - automatic encoding detection, clean UTF-8 as the result. No upload.
Running locally on your device ...
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
Subtitles from the old DVD-rip era or from older Windows editors were often saved in an 8-bit encoding like windows-1252 instead of UTF-8. If a modern player or browser opens such a file as UTF-8 anyway, umlauts and special characters turn into cryptic multi-character sequences instead of the intended letter - this phenomenon is called mojibake. This tool detects the broken encoding and repairs it.
Technically, the tool first checks whether the raw bytes are valid UTF-8 at all. If that fails, it is a strong sign of an 8-bit encoding such as windows-1252 - the file is then re-read as that encoding and cleanly written back out as UTF-8. If the bytes ARE valid UTF-8 but still look like the classic pattern of a double-encoding, the tool also attempts to repair that rarer case.
If the encoding cannot be determined with reasonable confidence, the tool stops with an honest error message instead of guessing and producing more garbled text. If the file is already clean UTF-8, nothing changes - a safe no-op. The whole analysis runs locally in your browser.
| Input formats | SRT, VTT, ASS, SSA, SBV, TTML, DFXP, SMI, SAMI, LRC |
|---|---|
| Auto-conversion | MP4 |
| Output format | SRT |
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Only the most common case (windows-1252/Latin-1 saved instead of UTF-8) and a simple double-encoding are reliably detected; rarer, multiply-nested encoding errors are honestly rejected rather than guessed. The subtitle content itself (timings, lines) stays unchanged - only the character encoding is repaired.
No, the repair runs entirely locally in the browser.
Garbled multi-character sequences instead of the intended letter - they appear when a file saved in an 8-bit encoding is wrongly read as UTF-8.
The tool reports that honestly instead of guessing a wrong encoding and producing even more garbled text.
No - an already-valid UTF-8 file comes back unchanged.