SubtitleMedic

Fix RTL Subtitles

Periods and question marks at the wrong end of Arabic or Hebrew lines? Load the file, pick how your player shows it, and download subtitles that read right to left.

Processed in your browserNo sign-up.srt, .vtt, .ass, .sbv, .sub

How to fix right-to-left subtitles

  1. Open your subtitle file

    Drop an .srt, .vtt, .ass, .sbv or .sub file into the box above, or click to browse. It’s read by your browser and never uploaded. Try the sample to see an Arabic file with the problem.

  2. Choose how to fix the lines

    Keep “Add right-to-left marks” for VLC, phones and most apps. Switch to “Swap the punctuation” only for a TV that still shows it wrong. The preview shows every line before and after.

  3. Download the fixed file

    Save it as movie.rtl.ar.srt. The language code stays at the end of the name, so players still pick the right track.

Why the punctuation ends up at the wrong end

Arabic, Hebrew and Persian are written right to left, but a subtitle file doesn’t store direction. It stores characters in reading order: the first word of the sentence first, the final period last. Turning that into a line on screen is the job of the Unicode bidirectional algorithm, which every modern player has, and it needs one starting fact: which way the line as a whole runs.

Most players don’t ask the text. They assume the direction of their own interface, which is left to right. Inside such a line, Arabic or Hebrew letters still run right to left, because letters carry a strong direction of their own. Punctuation doesn’t. A period, comma, question mark or dialogue dash at the edge of the line takes the line’s direction, so the period that ends the sentence is drawn on the right, where the sentence begins for a reader of Arabic. A dash that opens a line of dialogue moves to the far end in the same way, and numbers or Latin words in the middle of a line can shuffle the parts around them.

The words are fine and the file is correct. It only lacks the hint that says “this line runs right to left”.

What each option does

Add right-to-left marks. Each row that contains Arabic, Hebrew or Persian is wrapped in two invisible Unicode characters: RIGHT-TO-LEFT EMBEDDING (U+202B) at the start and POP DIRECTIONAL FORMATTING (U+202C) at the end. Players that implement the bidirectional algorithm, which includes VLC, MPC-HC, PotPlayer, Kodi, web browsers and most Android and iOS apps, then lay the whole row out right to left, with the punctuation where it belongs. No visible character changes, rows in other languages are left alone, and running the fix twice changes nothing more.

Swap the punctuation. Some TVs and older players draw characters strictly in the order they are stored. For them, the punctuation at the end of each right-to-left row moves to the start and the dash at the start moves to the end, which is the order that looks right on such a screen. This is a workaround, not a correction: the same file shows the punctuation at the wrong end again on a player that handles right-to-left text. Use it only for the device that needs it.

Remove direction marks. Every invisible direction mark is taken out of every row: the embeddings above, the RIGHT-TO-LEFT and LEFT-TO-RIGHT MARKS (U+200F, U+200E), the Arabic letter mark and the isolates. Use it to undo a fix, or to clean a file that collected marks from several editors before trying again.

In every mode, tags such as <i>, <font> and ASS codes like {\an8} stay where they are, so italics and positions are kept. ASS comment lines are not touched, and the file is saved in the format it came in.

Tips

Strange symbols come first. If the file shows ÇáÓáÇã or ùìåí instead of Arabic or Hebrew letters, it is an encoding problem, not a direction problem. Read the file with Fix Subtitle Encoding, which detects Windows-1256 and Windows-1255, then fix the direction here. The guides for VLC and smart TVs show where those symbols come from.

Test on the screen you will watch on. Players differ in how much of the bidirectional algorithm they follow. Fix a copy, play a few lines on the TV or app you actually use, and keep the version that reads right there.

Fix one line by hand. If a single line still looks odd, for example one that mixes Arabic with a long English title, open the file in Subtitle Editor. For timing problems, use Shift Subtitle Timing.

Frequently asked questions

Why does the period show at the start of my Arabic subtitles?

The text in the file is in the right order, but the player lays each line out left to right, as it would English. Arabic and Hebrew words still run right to left inside that line, while a period, question mark or dash at the end of the sentence takes the line’s left-to-right direction and lands on the wrong side. Adding right-to-left marks tells the player which way the line runs.

Which option should I choose for my player?

Start with “Add right-to-left marks”. It works in VLC, MPC-HC, PotPlayer, Kodi, browsers and phone apps, and it changes no visible character. Only if a TV or an old media player still shows the punctuation on the wrong side, use “Swap the punctuation”, which moves it to the other end of the line in the file itself.

What happens if I swap the punctuation twice?

The lines go back to how they were. Swapping moves the punctuation at each end of a line to the other end, so a second pass undoes the first. That also means a swapped file looks wrong again on a player that lays out right-to-left text properly, so keep the original for those players.

My subtitles show strange symbols, not Arabic letters. Will this fix them?

No, that is a different problem. Symbols such as “ÇáÓáÇã” mean the file was saved in an older code page, usually Windows-1256 for Arabic and Persian or Windows-1255 for Hebrew, and read as another one. Open it in Fix Subtitle Encoding first, then come back here if the punctuation is still at the wrong end.

Is my file uploaded?

No. The file is read and fixed by JavaScript in this browser tab. It never leaves your device, and the tool keeps working offline once the page has loaded.