SyncMySubsWhy are my subtitle characters garbled?
If your subtitles show é, “, or runs of odd accented letters instead of real words, nothing is broken with the video or the file's timing. This is mojibake, and it means the text was read with the wrong character encoding. It is one of the most common subtitle problems, and it is quick to fix.
How to recognize it
Mojibake has a signature look. A single accented letter becomes two or three wrong ones: é shows up as é, ñ as ñ, and curly quotes as “ and â€. Cyrillic, Greek, or Asian text can appear as a wall of unrelated symbols. The giveaway is that only the letters are wrong. The line breaks, the timing, and the cue numbers are all intact, which tells you this is a text-encoding issue and not a damaged file or the wrong subtitle format.
Why it happens
A subtitle file is just bytes, and an encoding is the rule that turns those bytes into letters. The file was saved using one encoding, very often Windows-1252 or an ISO-8859 variant, which use a single byte for characters like é or a curly quote. When a player or website then reads the same bytes as UTF-8, where those characters are stored differently, the rule no longer matches and you get the wrong letters. It shows up most with subtitles pulled from the web, which are frequently saved in a legacy code page rather than UTF-8.
How to fix it
You do not retype anything. The original bytes are correct; they just need to be read with the right rule and saved in a format everything agrees on. Open the file in the Fix Encoding tool, choose the source encoding starting with Windows-1252, and watch the live preview. When the accents and punctuation snap back to normal, download the file, which is exported as clean UTF-8 that modern players and websites read correctly.
If you do not know the encoding
Not sure what the file started as? Run it through the Encoding Detector first. It inspects the bytes and tells you the most likely encoding, so you can go straight to the right choice in Fix Encoding instead of guessing. As a rule of thumb, Western European text is usually Windows-1252, Central European often ISO-8859-2 or Windows-1250, and Cyrillic usually Windows-1251.
FAQ
What does mojibake look like?
Accented and non-Latin letters turn into short runs of the wrong characters: é where an é should be, ñ for ñ, “ for curly quotes, and strings of odd letters where Russian, Greek, or Asian text should be. The timing and layout look fine; only the letters are wrong.
Why does it happen?
The file was saved with one encoding, often Windows-1252 or an ISO-8859 variant, but the player or website reads it as UTF-8, so the bytes for special characters map to the wrong letters. It is especially common with subtitles downloaded from the web.
How do I fix it?
Re-decode the file with its real encoding and save it as UTF-8. The Fix Encoding tool does exactly this: pick an encoding, starting with Windows-1252, watch the live preview, and download once the text reads correctly.
What if I do not know the original encoding?
Let the Encoding Detector inspect the file and suggest the most likely encoding, then fix it. Windows-1252 covers most Western European cases; Central European text often needs ISO-8859-2 or Windows-1250, and Cyrillic usually needs Windows-1251.