Fix subtitles with broken characters

2026-11-13

Find out whether the issue affects the original subtitle file or only the player’s display.

How it works

Character errors can occur when a player interprets text using a different encoding. WebVTT specifies UTF-8. A styled or embedded track can behave differently from an external text file.

What to do

1. Try a second compatible player with the same authorized file.
2. If you own the subtitle file, save a separate UTF-8 copy and test it.
3. Keep the original file and note the exact language and error pattern.

Identify the pattern before editing the file

If café becomes café in several lines, the pattern is consistent with text encoded in UTF-8 and decoded using a different character set. If you see a box where one character should be, compare the same subtitle in another font or player because a missing font glyph can look different from a decoding error. If the saved text already contains the replacement character �, find an earlier copy of the subtitle.

Work on a copy of a subtitle file you control. Open it in an editor that can select a text encoding and compare the first affected sentence against the original. A valid WebVTT file is UTF-8 and starts with the WEBVTT header. A filename ending in .vtt tells you nothing about the underlying text or timing syntax.

Verify the fix from the source through the television

Once the same line is readable in the editor, save a new copy and play that cue locally. Then open the exact file in the intended player and check another line with accented letters or another script. Include the specific letters or script that exposed the problem.

If the track is embedded in a service’s stream, keep the timestamp, language and a short example of the misrendered characters for support. An unrelated subtitle download might use a different cut or frame rate and introduce a timing problem. Use the corrected track from the source where available.