Fix Arabic subtitle encoding

Updated May 18, 2026 | Subtitle Problems

Arabic subtitle encoding problems are frustrating because the timing may be correct while the text is unreadable. Instead of Arabic words, you may see question marks, random Latin characters, boxes, or disconnected letters. This usually means the player is reading the file with the wrong character encoding.

The safest modern encoding for Arabic subtitles is UTF-8. It preserves Arabic characters, works across browsers and most media players, and avoids old regional code page problems. This guide explains how to recognize an encoding issue, save a subtitle file correctly, and avoid breaking the file while converting or editing it.

Recognize Arabic encoding problems

If every Arabic line is unreadable but timestamps still work, the file is probably encoded incorrectly. If only some lines are wrong, the subtitle may have been damaged during editing or copied from a source that mixed encodings.

Arabic shaping problems are different from encoding problems. If letters appear separated but still recognizable, the player or app may not support proper Arabic shaping or right-to-left display. If the text is random symbols, question marks, or empty boxes, focus on encoding first.

Step-by-step: save Arabic subtitles as UTF-8

Do not paste Arabic text into a random converter without checking the output. A tool that does not preserve Unicode correctly can turn a recoverable file into question marks. If the editor already shows question marks, the original characters may have been lost and you may need another source file.

1. Make a backup copy of the subtitle file.
2. Open the file in a text editor that can choose encoding, such as Notepad, VS Code, or another subtitle editor.
3. If the Arabic text is readable in the editor, choose Save As and select UTF-8 encoding.
4. Keep the subtitle extension as .srt unless your target platform requires another format.
5. Test the UTF-8 file in your video player.
6. If you need a web format, convert the clean UTF-8 SRT with the SRT to VTT Converter.
7. If timing changed during editing, repair it with the Subtitle Shifter.

Check media player subtitle settings

Some desktop players let you choose a default subtitle encoding. If Arabic looks broken in one player but correct in another, the file may be fine and the player setting is wrong. Look for subtitle encoding, default charset, or subtitles text encoding in preferences and choose UTF-8.

For browser video and HTML5 captions, use UTF-8 and WebVTT when possible. If you start from SRT, convert with a proper tool instead of just renaming the extension. Renaming a file from .srt to .vtt does not add the required WebVTT structure.

If you work with Arabic, keep one clean master SRT file in UTF-8 and create other formats from that master. This prevents repeated copy and save operations from slowly damaging the text. It also makes later translation or timing work easier because the subtitle source remains readable.

Quick Arabic display test

Open the file before conversion and confirm a normal Arabic sentence is readable. If the source already shows question marks, conversion will not restore it.

Common mistakes with Arabic subtitles

• Renaming the file extension without fixing the internal text encoding.
• Saving Arabic subtitles in an old code page when the target player expects UTF-8.
• Opening the file in a program that cannot display Arabic correctly and then saving over the original.
• Assuming timing is broken when only the text encoding is wrong.
• Converting to VTT before confirming the Arabic text is readable in the source file.