The short version
- Subtitle files are just plain text. Because the video player draws the lines on screen, the same SRT file might look fine in one app and broken in another.
- Punctuation and numbers have no built-in direction. They copy the direction of the text around them, which is why they jump when a line ends with an English word.
- Always save subtitle files as UTF-8. Other encodings turn Hebrew and Arabic characters into question marks or garbled text.
- Clean up text problems before you export, and check the finished file in the same video player your audience uses.
- If a video platform still messes up your subtitles, burn the captions straight into the video frame so they cannot shift.
Why does punctuation end up on the wrong side?
You read Hebrew and Arabic from right to left, but any numbers or Latin letters inside the sentence still go from left to right. Every program uses the Unicode Bidirectional Algorithm to figure out how to display a line that mixes both. Actual letters have a fixed direction. Spaces, commas, periods, quotes, and brackets do not. They are neutral, so they just take on the direction of whatever letters sit next to them.1
Trouble starts when one of those neutral characters lands between two directions. Take a Hebrew sentence that ends with an English brand name and a period. Since the period comes right after English letters, the layout engine puts it at the far left of the line instead of at the end of the sentence. The file itself isn't broken. The layout engine just had to guess.
Which problems happen most often?
The most common problem is punctuation showing up at the wrong end of a line, which usually happens after English words, digits, or a closing bracket. Another issue is when a number paired with a symbol, like a percentage or currency sign, displays in reverse order. A third problem is a number range or a timestamp like 10:30 that reads fine on one line, then flips if a line break splits it across two lines.
Mixing alphabets mid-sentence causes another headache. An English name dropped into the middle of a Hebrew line will read fine on its own, yet it can scramble the order of the Hebrew words on either side of it. You will see the same mess with sound cues in square brackets, speaker names followed by a colon, and music note icons, since all of them put neutral symbols at the start or end of a line.
How to fix a subtitle line before exporting
Try changing the wording first. If a line ends with an English word, see if you can rephrase it so a Hebrew or Arabic word comes last, or move the punctuation away from the Latin text. Often a small change, like putting a Hebrew word after a brand name, fixes the layout in every player.
If you cannot change the wording, you can insert a directional mark. It is an invisible Unicode character that tells the layout engine which direction a neutral character should follow. If you put a right-to-left mark at the end of the line, right after the period, it anchors the punctuation to the right-to-left text. The W3C recommends this same method for web pages, and the marks work the same way inside subtitle files.2
It also helps to keep your lines short, which we talk about more in our guide to subtitle reading speed and line length. Short lines give mixed-direction text fewer chances to wrap weirdly, and if you do split a sentence across two lines, it is much easier to control where the break happens.
Do file format and encoding matter?
Yes, starting with encoding. Always save your file as UTF-8. When a Hebrew or Arabic SRT file shows up as question marks or garbled symbols, it was likely saved or opened with a legacy encoding. Open it again as UTF-8, or export a fresh copy from your subtitle editor.
As for the file type, an SRT file only holds plain text and timestamps. VTT was built for web video under a W3C standard, so it lets you style the text and pick where captions sit on screen. Still, both formats use the same rules for right-to-left text, so the fixes here work the same in either one.3
KolWrite lets you export both SRT and VTT files from your edited transcript with the right-to-left formatting already handled for Hebrew and Arabic. Fix the wording in the transcript first, then export, so all your edits carry over into the final file.
How to test the final file
Load the exported file into the actual player your viewers will use, whether that is a social media app, a web player, a phone gallery, or your editing software. Different players handle right-to-left text in slightly different ways, so a subtitle that looks fine in one app might still need a small tweak for another.
Pay special attention to the three spots where layout problems usually show up: lines that end in English, lines with digits or symbols, and sentences broken across two lines. Play the video back with the audio on, too. A line can look fine on screen while still being out of sync with the spoken words.
When to burn captions into the video
If a target platform cannot display a subtitle file properly, or if you want exact control over typography and placement, burn the captions into the video. That makes the text part of the image itself, so every viewer sees the exact same layout on every device. You lose flexibility, though, because viewers cannot turn the captions off, resize them, or switch languages.
A practical workflow is to deliver both versions. Give a clean SRT or VTT file to platforms that support closed captions, and a burned-in video to platforms that do not. KolWrite can export either format from the same transcript, so you only have to proofread the text once.
Common questions
Why does my Hebrew subtitle show the period on the left?
The line probably ends with a number or English letters. Because punctuation has no direction of its own, it just follows the text next to it. You can either reword the line so a Hebrew word comes last, or add a right-to-left mark right after the period.
What encoding should a Hebrew or Arabic SRT file use?
Use UTF-8. Legacy encodings cannot hold every Hebrew and Arabic character and often swap letters out for question marks or garbled text.
Is VTT better than SRT for right-to-left languages?
Not for text direction, since both formats follow the same Unicode rules. VTT does let you style the text and place captions in specific spots on screen, so pick whichever format fits the player you are using.
Can I fix punctuation order inside the video player?
Usually no. Video players just draw the text you give them. To fix it for good, edit the subtitle file itself and check it again in the player you plan to use.
Do burned-in captions avoid these layout problems?
Yes, because the software turns the text into part of the video image before you export it. You still have to check the layout before rendering the video, and your viewers will not have the option to hide the captions.