Subtitles Showing Question Marks or Gibberish? Fix SRT

Equalang

In brief

Diagnose whether garbled SRT subtitles come from a legacy encoding mismatch or missing font glyphs, and convert files to UTF-8 without corrupting text.

Keywords: subtitles showing question marks; vlc subtitles showing question marks; convert the srt file to utf 8 encoding; srt gibberish fix; subtitle encoding mismatch

When subtitles show up as question marks, scrambled accents, or empty boxes, you are looking at one of two completely separate problems. Strange symbols like ``, ???, é, or random characters mean a character encoding mismatch (Mojibake): your player is reading an older regional .srt file as UTF-8 (or vice versa). Uniform empty rectangles (□□□), on the other hand, mean missing font glyphs ("Tofu"): the file is already valid UTF-8, but your player's active subtitle font lacks characters for Chinese, Japanese, Korean, Arabic, or Thai.

Identifying which symptom is on your screen takes five seconds—and prevents you from changing the wrong setting or permanently overwriting your subtitle file.

Encoding Mismatch vs. Missing Font Glyphs: Spot the Difference

Older .srt files from subtitle archives were frequently saved in single-byte or regional legacy codepages rather than Unicode UTF-8. Because an .srt plain-text file carries no mandatory internal header declaring its encoding, media players have to guess—or default to UTF-8 or your operating system's local codepage.

Use what you see on screen to pinpoint the exact cause:

What You See on ScreenTechnical CauseWhy It HappensThe Actual Fix
`` (diamond question mark) or ???Legacy bytes read as UTF-8Single-byte characters (such as accented letters in Windows-1252 or Cyrillic in Windows-1251) form invalid byte sequences when a player expects UTF-8.Reopen the .srt in its original legacy encoding, then convert and save as UTF-8.
é, á, ¿, or æ—¥UTF-8 bytes read as a legacy codepageA valid multi-byte UTF-8 character (like é, encoded as two bytes 0xC3 0xA9) is split and rendered one byte at a time in Windows-1252.Set your player's default subtitle encoding to UTF-8, or add a UTF-8 BOM if a legacy hardware player requires it.
Scrambled CJK or Latin gibberishWrong regional multi-byte codepageA file saved in GB18030/GBK, Big5, Shift_JIS, or EUC-KR is decoded using a Western European or different Asian codepage.Reopen the file using the matching regional encoding in VS Code or via iconv, then save as UTF-8.
Uniform empty boxes (□□□)Missing font glyphs ("Tofu")The .srt file is already valid UTF-8 and the player knows the exact Unicode code points, but the selected subtitle font only contains Latin letters.Leave the file encoding alone; switch the player's subtitle font to a Unicode/CJK-capable font.

For instance, consider a French line containing accented letters and an inverted Spanish question mark:

14
00:01:12,400 --> 00:01:15,100
¿Où est le café ?

If that file was saved in Windows-1252 and your player strictly expects UTF-8, the high bytes for ¿, ù, and é are invalid standalone UTF-8 sequences, so the player substitutes replacement characters:

14
00:01:12,400 --> 00:01:15,100
O est le caf ?

Conversely, if the .srt file is already properly encoded in UTF-8 (é = 0xC3 0xA9), but your player is configured to decode subtitles as Windows-1252, each byte is printed as its own Windows-1252 character:

14
00:01:12,400 --> 00:01:15,100
¿Où est le café ?

Stop Before You Save: How People Permanently Ruin an SRT File

Before you open a garbled .srt file in a text editor and hit "Save as UTF-8," watch out for the single most common mistake in subtitle troubleshooting.

If you open an .srt file in an editor where the dialogue **already looks like , `???`, or `é` on screen**, and you immediately click **Save as UTF-8**, you permanently destroy the original text. The editor takes the broken replacement characters currently displayed in the window and writes their literal `UTF-8` bytes (`U+FFFD` for or U+003F for ?) to disk, overwriting the original regional bytes forever. Once that happens, no encoding converter can recover the missing letters.

To convert a file safely:

  1. First make a backup copy of your original .srt file.
  2. Tell your editor to re-interpret (reopen) the raw bytes on disk using the original source encoding until every word looks completely normal.
  3. Only after the characters look right on screen should you save (convert) the file to UTF-8.

Which Legacy Encoding Is My SRT File Using?

When you need to reopen an older .srt file, match the subtitle language to its standard legacy codepage:

Subtitle LanguageLegacy Codepage to TryTypical Broken Symptom Before Fix
English, French, Spanish, German, Italian, PortugueseWindows-1252 (Western European)Accented vowels (é, ñ, ü) and smart quotes turn into `` or é
Russian, Ukrainian, Bulgarian, Serbian (Cyrillic)Windows-1251 (Cyrillic)Entire lines appear as `` or accented Latin letters like Ïðèâåò
ArabicWindows-1256 (Arabic)Dialogue turns into `` or disconnected Latin punctuation
Simplified ChineseGB18030 or GBKDialogue turns into `` or half-width Latin/symbol combinations
Traditional ChineseBig5Dialogue turns into scattered symbols, question marks, or mismatched hanzi
JapaneseShift_JISKana and kanji break into half-width symbols or ``
KoreanEUC-KRHangul blocks turn into `` or broken Latin pairs

Method 1: Convert an SRT File to UTF-8 Safely in VS Code

Visual Studio Code makes encoding repair transparent because it separates Reopen with Encoding (changing how existing bytes on disk are read) from Save with Encoding (converting and writing new bytes).

  1. Open your .srt file in VS Code. If the subtitles look broken (???, ``, or gibberish), do not edit or save the file yet.
  2. Look at the bottom-right status bar and click the encoding indicator (it usually says UTF-8).
  3. Select Reopen with Encoding from the command drop-down at the top of the window.
  4. Pick the legacy encoding that matches the subtitle language from the table above (for example, Western (Windows 1252) for French/Spanish, Cyrillic (Windows 1251) for Russian, or Simplified Chinese (GB18030) for Simplified Chinese).
  5. Check the editor window. If the dialogue still looks scrambled, click the bottom-right encoding indicator again, choose Reopen with Encoding, and try the next candidate until every accent or character is clean and readable.
  6. Once the text looks completely normal on screen, click the bottom-right encoding name one more time.
  7. Select Save with Encoding -> UTF-8.

Your .srt file is now genuinely converted to UTF-8 and will load cleanly across desktop players, browsers, and mobile apps—whether you are watching a single track, setting up VLC dual subtitles, or preparing a clean source file before following our SRT subtitle translation guide.

Method 2: Convert SRT Files to UTF-8 via Terminal (iconv)

On macOS or Linux, you can convert legacy .srt files directly from the command line using iconv, which reads the source bytes with -f (from) and writes clean UTF-8 to a new file with -t (to) without touching your original file.

Convert a Western European (Windows-1252) subtitle file to UTF-8:

iconv -f WINDOWS-1252 -t UTF-8 old.srt > utf8.srt

Convert a Cyrillic (Windows-1251), Simplified Chinese (GB18030), or Japanese (Shift_JIS) file to UTF-8:

# Russian / Cyrillic
iconv -f WINDOWS-1251 -t UTF-8 movie-ru.srt > movie-ru-utf8.srt

# Simplified Chinese
iconv -f GB18030 -t UTF-8 movie-zh.srt > movie-zh-utf8.srt

# Japanese
iconv -f SHIFT_JIS -t UTF-8 movie-ja.srt > movie-ja-utf8.srt

Always redirect output to a new filename (> utf8.srt) rather than redirecting back into the same file (> old.srt), which would truncate your source file before iconv finishes reading it.

How to Fix Empty Boxes (□□□) in VLC When Encoding Is Already UTF-8

If your subtitles appear as uniform empty rectangles (□□□), converting the .srt file will not change anything. Empty boxes mean VLC has already decoded the UTF-8 text properly, found the exact Unicode code points, and asked the currently selected font to draw them—only to find that the font has no glyphs for that script.

This frequently happens on smart TVs or fresh VLC installs where the default subtitle font only covers Latin characters, and you load a Chinese, Japanese, Korean, Thai, or Arabic .srt file.

To fix □□□ in VLC immediately:

  1. Open VLC and go to VLC > Preferences (on macOS) or Tools > Preferences (on Windows/Linux).
  2. Click the Subtitles / OSD tab.
  3. Locate the Font dropdown under Subtitle Effects.
  4. Change the font from a Latin-only font to a comprehensive Unicode or CJK-capable font installed on your system:
    • Cross-platform / Linux: Noto Sans CJK or Arial Unicode MS
    • macOS: PingFang SC
    • Windows: Microsoft YaHei 5.While you are in the Subtitles / OSD tab, set Default encoding to Universal (UTF-8) so VLC never tries to decode modern UTF-8 files as a legacy regional codepage.
  5. Click Save, close the video completely, and reopen it (VLC caches the subtitle font renderer while a video is active).

Frequently Asked Questions

Why is my question mark or accented letter showing up as é or ¿?

In UTF-8, characters outside basic ASCII are stored using two to four bytes. For example, é is stored as the two-byte sequence 0xC3 0xA9, and the inverted question mark ¿ is stored as 0xC2 0xBF. When a media player or text editor is set to a single-byte legacy encoding like Windows-1252 instead of UTF-8, it treats each byte as a separate character—turning 0xC3 0xA9 into é and 0xC2 0xBF into ¿. Switching the player's subtitle encoding to UTF-8 fixes it immediately.

Can I recover an SRT file that was already saved with literal ??? or `` characters?

No. Once an editor saves a file while `` (U+FFFD) or ? (U+003F) is displayed on screen, every corrupted character is replaced by the identical byte sequence for that placeholder. Because dozens of different letters collapse into the exact same replacement symbol, the original bytes are gone. You will need to re-download the original .srt file and use Reopen with Encoding before saving as UTF-8.

Should I save my SRT file as UTF-8 or UTF-8 with BOM?

Standard UTF-8 (without a Byte Order Mark) is the universal recommendation per the Unicode specification and works across modern desktop players, web <track> elements, and subtitle tools. However, if an older television USB player or legacy Windows program still defaults to a local codepage when opening a standard UTF-8 file, saving as UTF-8 with BOM prepends three identification bytes (0xEF 0xBB 0xBF) that force legacy software to recognize the file as UTF-8.

Sources