Arabic subtitles can look broken in several ways: question marks, boxes, random Latin characters, separated letters, or text that appears in the wrong direction. These symptoms are frustrating, but they usually come from encoding or rendering problems rather than the translation itself.
A subtitle file must store Arabic characters correctly and the player must display them with a font and text engine that supports Arabic shaping and right-to-left reading. If either side fails, the captions can become unreadable.
This guide explains the common causes and a safe repair workflow for Arabic SRT and other subtitle files.
Encoding, fonts, and right-to-left display
Encoding is how text characters are stored in the file. If Arabic text was saved in one encoding and opened as another, the player may show symbols or question marks. UTF-8 is the safest modern choice for multilingual subtitle files.
Fonts matter too. If a player uses a font that does not support Arabic glyphs, it may show boxes even when the file itself is correct. Changing subtitle font settings can solve display problems without editing the text.
Arabic also needs proper shaping and right-to-left handling. Some weak players or old devices may show isolated letters or incorrect direction. Testing in more than one player helps reveal whether the issue is file encoding or player rendering.
Do not repeatedly copy broken Arabic text between editors. Each bad save can make recovery harder. Work from the cleanest available source and save a UTF-8 copy before testing.
When Arabic text is already broken, duplicate the file before attempting encoding repair so you can return to the original bytes if needed.
Broken: ????? ?????? Readable: مرحبا بكم Repair goal: readable Arabic text saved as UTF-8
Step-by-step: fix broken Arabic subtitles
Use a careful workflow because encoding repairs can become worse if the file is saved incorrectly multiple times.
Make a copy of the subtitle file before editing.
Open the file in a text editor or subtitle tool that can detect encoding.
Check whether the Arabic text is readable before saving anything.
If readable, save a UTF-8 copy and test it in the player.
- Make a copy of the subtitle file before editing.
- Open the file in a text editor or subtitle tool that can detect encoding.
- Check whether the Arabic text is readable before saving anything.
- If readable, save a UTF-8 copy and test it in the player.
- If unreadable, try opening the original with likely legacy encodings before converting.
- Choose a player font that supports Arabic characters.
- Test line direction, punctuation, and mixed Arabic-English cues.
- Keep the repaired UTF-8 file as the new master.
Practical examples
Real subtitle work usually fails at boundaries: the first spoken line, a scene change, a translated phrase that becomes longer, or a platform upload that expects a different format. Use the examples below as a quick quality check before you export.
The characters may have been lost during a bad save, which is harder to recover than a display-only issue.
The subtitle may be correct, but the selected font lacks Arabic glyph support.
The player may not handle Arabic shaping correctly, even if the file text is valid.
Arabic captions appear as symbols, boxes, or isolated characters and are repeatedly saved in broken form.
A UTF-8 subtitle copy displays readable Arabic with a font and player that support the script.
Common mistakes to avoid
Most subtitle problems become harder when the source file is edited without a plan. Keep an original copy, make one focused change at a time, and test the output in the environment where viewers will actually use it.
- Saving the broken file over the only original copy.
- Assuming translation is wrong when encoding is the real issue.
- Testing only in one weak player or device.
- Using a font that does not support Arabic glyphs.
- Copying question marks into a new file and expecting recovery.
- Ignoring mixed-language punctuation and direction during review.
Conclusion
Broken Arabic subtitles are usually an encoding, font, or rendering issue. The safest fix is to preserve the original, repair encoding carefully, save UTF-8, and test in a player with Arabic support.
Once the text is readable, keep that file as your clean master for translation, timing fixes, conversion, or platform uploads.
Related tools
Use these TranslateSubtitles.net tools when you are ready to apply the workflow from this guide.
Related guides
FAQ
Why do Arabic subtitles show question marks?
The characters may have been decoded or saved with the wrong encoding, and in some cases the original text may have been lost.
Why do Arabic subtitles show boxes?
The player or selected subtitle font may not support Arabic characters.
Should Arabic SRT files use UTF-8?
Yes. UTF-8 is the safest modern encoding for Arabic subtitle delivery.
Can timing tools fix Arabic text?
Timing tools fix cue times. Encoding or text display problems need text repair and player support checks.