SRT to SSA Mistakes and Best Practices for Indian Language Subtitles

Converting SRT to SSA looks easy, and it is. But the small mistakes around it cause most of the pain. A creator posts a video and finds empty boxes where the Telugu letters should be. An editor sends a file to a client and the client sees a plain font. A student loses the only copy of the original subtitle file.

This article lists the mistakes that Indian users make most often and shows how to avoid them. It then gives a set of best practices you can follow on every project.

Why mistakes happen with Indian language subtitles

English subtitles are forgiving. Almost every font has the letters, and the text is narrow. Indian scripts are different in four ways.

• They use many more characters, including conjuncts, vowel signs and special marks.
• The letters are often taller and wider, so they need more room.
• They need Unicode (UTF-8) to store correctly.
• The font and player must support text shaping, which joins the parts of a letter correctly.

If any one of these four is missing, the result looks wrong. Knowing this helps you find the cause quickly.

Mistake 1: Wrong or unknown encoding

Old Windows tools save text in ANSI or in a regional code page. When you convert such a file, the letters turn into question marks or strange symbols. Always open the SRT first, check that the text is readable, and save as UTF-8. If your file came from an old subtitle tool, re-save it in Notepad with the UTF-8 option.

Mistake 2: A font without your script

Fonts such as Arial or Times New Roman may have limited or no coverage for Tamil, Telugu or Bengali on some systems. The result is empty boxes. Pick a font made for your script, such as Noto Sans Devanagari, Noto Sans Tamil, Noto Sans Telugu or Noto Sans Bengali. These are free and widely used.

Mistake 3: Font size too large or too small

A size that looks fine for English can cover half the screen in Tamil. A size that is too small becomes unreadable on a phone. Start at 20 to 24 and test. The right number also depends on the PlayRes values in the file header, so test in the same kind of player where the audience will watch.

Mistake 4: Ignoring margins and safe areas

TVs, projectors and some phone players crop the screen edges. Text placed right at the bottom may be cut. Keep a vertical margin of 30 or more and side margins of 40 to 60. Also keep subtitles away from channel logos, tickers and lower-third graphics.

Mistake 5: Deleting or overwriting the SRT

The SRT is your master file. YouTube, Facebook and many apps need it. If you overwrite it, or lose it, you cannot make new SSA styles or fix errors without going back to scratch. Keep it safe in a folder with a clear name and a backup.

Mistake 6: Expecting every platform to read SSA

SSA is great for desktop players and for burned-in video. It is not the best choice for platforms that expect SRT or VTT. Check what your platform accepts before you spend time on styling. If you need to move between formats, a tool like the SRT converter can help with the plain-text side.

Mistake 7: Not testing

Many problems show only on playback. Test in at least one player. If your audience watches on phones, test on a phone as well. A five-minute test saves a re-export.

Worked scenario 1: A Hindi news clip with broken text

Vikram is a freelance editor in Delhi. A client sent him an SRT made years ago with an old tool. After conversion with the SRT to SSA tool, his Hindi lines showed as question marks.

He checked the original file in Notepad. The text was already broken there, so the problem was the source encoding, not the conversion. He asked the client for the original document, pasted the text into a new file, saved as UTF-8 and ran the conversion again. This time the text was clean. His lesson was simple: always read the SRT before converting.

Worked scenario 2: A Telugu short film with boxes

Anusha made a short film in Warangal and sent a styled SSA file to a festival. The festival team opened it on their computer, and the Telugu text showed as boxes. Her SSA used the font Gautami, which was on her own laptop but not on theirs.

She fixed it in two ways. She changed the font to Noto Sans Telugu, and she also burned the subtitles into a screening copy, so no font was needed on the festival computer. She also sent a small text note naming the font. The festival played the burned-in copy without trouble.

Worked scenario 3: A Bengali explainer with overlapping text

Rajat runs a Bengali science channel. His videos have a name bar at the bottom for the guest speaker. After conversion, the subtitles sat on top of the name bar. He changed MarginV from 30 to 90 for the guest scenes. For the rest of the video, he kept the original margin by splitting the file into two styles, Default and Guest. The converter gave him the base file. He changed the style name in a few lines by hand.

The result was clean and no text ever hid the speaker’s name.

Quick reference: problem, cause and fix

Problem	Likely cause	Fix
Question marks	Source not UTF-8	Re-save SRT as UTF-8 and convert again
Empty boxes	Font missing the script	Use a Noto Sans font or burn in
Text off screen	Size too large or margins small	Lower size, raise margins
Nothing shows	Player not loading file	Match names or add file manually
Overlap with graphics	Bottom margin too small	Raise MarginV or move to top
Wrong timing	Source SRT offset	Fix the offset in the SRT

Benefits of getting the details right

• Professional look: Clean, readable captions build viewer trust.
• Less rework: Fewer re-exports and fewer client complaints.
• Wider reach: Correct text means more viewers understand your video.
• Reusable setup: A good style becomes a template for all future videos.

Challenges and limitations

Even with good habits, you cannot control everything. Different players draw outlines and spacing a little differently. Some mobile players ignore SSA styles or only show plain text. Very old devices may not shape Indic letters properly. And no converter can fix spelling mistakes or poor translation in the source text.

The practical answer is to test where your audience watches, and to burn the subtitles in when you cannot control the player.

Key takeaway: Most SRT to SSA failures come from encoding, fonts and margins, not from the conversion itself. Check those three before you blame the tool.

Common mistakes to avoid (summary)

1. Skipping the UTF-8 check. Read the SRT and re-save it as UTF-8 first.
2. Using a default font. Choose a Noto Sans font that matches your script.
3. Setting the size by guess. Test on a short clip.
4. Placing text at the very edge. Keep margins of 30 or more.
5. Overwriting the master SRT. Save the SSA under a new name.
6. Sharing without testing. Play the file in a real player first.

Best practices

• Save a clean UTF-8 SRT as your master and back it up.
• Use Noto Sans fonts for Devanagari, Tamil, Telugu and Bengali scripts.
• Keep subtitles to two lines and about 35 to 42 characters per line.
• Use a 2-pixel black outline instead of heavy shadows.
• Name files by language and version, such as intro_te_v2.ssa.
• Burn in subtitles when you send the video outside your own devices.

A simple checklist before you share

1. Is the SRT readable and saved as UTF-8?
2. Is the font right for the script?
3. Did you watch the start, middle and end?
4. Do lines fit inside the frame on a phone?
5. Is the original SRT saved in a safe place?

Print this list or keep it in your notes. It takes less than five minutes to go through, and it prevents nearly all the problems in this article.

Conclusion

SRT to SSA conversion is reliable, but your results depend on the care you take around it. Save as UTF-8, pick a font that fits your script, test your sizes, keep safe margins and protect your original file. These habits are easy and cost nothing.

For Indian creators, editors and students working across Hindi, Tamil, Telugu, Bengali and Marathi, they turn a risky step into a routine one.

Frequently Asked Questions

Why do I see boxes instead of Indian letters in my SSA file?

The font in the file does not have glyphs for your script, or it is missing on the viewer’s device. Change to a Noto Sans font for your language, or burn the subtitles into the video.

Is SSA better than SRT?

Not always. SSA allows styling, while SRT is simpler and accepted on more platforms. Use each where it fits.

How many characters should one subtitle line have?

About 35 to 42 characters per line and at most two lines. Indic scripts are wide, so stay near the lower end.

Should I keep both SRT and SSA files?

Yes. Keep the SRT as a master and make SSA copies for styling or local playback. This lets you fix text in one place.

Do phone players support SSA?

Some do, such as VLC for Android, and many gallery apps do not. If you are unsure, burn the subtitles into the video.