Encoding fault
Characters are replaced by boxes or unrelated symbols, usually across the whole file. The file itself is wrong. Save it as UTF-8 and the text returns.
Bengali subtitle generator
Bengali subtitles that hold together.
Generate an editable Bengali caption track, review the wording, then check the conjuncts in the player your audience actually uses before you publish.
Bengali does not just need the right characters
Most subtitle problems in other scripts are about which characters ended up in the file. Bengali adds a second question: whether the player can draw them properly.
Bengali writing joins consonants into conjuncts, single shapes formed from two or more consonants, and attaches vowel signs around a consonant rather than simply after it. That means the font has to reshape glyphs depending on what sits next to them. A font without real Bangla support cannot do it.
The failure that produces is unusually deceptive. Nothing vanishes and nothing turns into a box. Every character is present and technically correct, but the conjuncts stay unjoined, so words come apart into their pieces. It looks like sloppy typing rather than a technical fault, which is exactly why it survives a quick check and reaches an audience.
Telling two faults apart
Shaping fault
Every character is correct but conjuncts render unjoined. The file is fine and the font is not. Changing the encoding will not help; changing the player or the font will.
Check it where it will actually be watched
A Bengali subtitle file can look perfect in the editor you wrote it in and render incorrectly in the app your audience opens, purely because of the font each one uses. So the last check is not a proofread. It is opening the file in the real destination and looking at words that contain conjuncts.
Rule out the simpler fault first. Confirm the file is saved as UTF-8, which the subtitle encoding guide covers, including the mistake that makes garbled text permanent. If the encoding is right and the text still looks wrong, you are looking at shaping, not data.
What to read, and how long the lines run
Names of people, places and channels come first, as they do in any language, because those are what viewers write in to correct. Then English words spoken inside Bengali sentences, which usually belong as they were said rather than transliterated.
Then line length. Bengali sets long, and a line that fits comfortably in English can overflow a vertical frame. The subtitle validator will tell you which cues are over, and the subtitle line breaker will re-break them without touching the timing.
Bangladesh and West Bengal share the script, so one file serves both. Some everyday vocabulary differs, so a video aimed squarely at one audience is worth reading with that in mind, but that is a wording judgement rather than a reason for a second track.
Publishing the track
YouTube accepts a subtitle track per language, so Bengali can sit alongside others on one upload; the subtitle track upload guide walks through the path and the UTF-8 requirement. Short-form feeds take no subtitle file, so those need the captions rendered into the picture, which also sidesteps the font question entirely because the shaping is settled at export. The delivery guide covers which destinations take which.
For other South Asian languages, see the Hinglish caption generator, the Urdu subtitle generator, and the Punjabi caption generator.
Bengali subtitle questions
Why do Bengali subtitles look broken in some players?
Bengali writing needs the font to reshape glyphs in context. Conjuncts, which are ligatures of two or more consonants, have to be joined into a single form, and vowel signs attach around the consonant rather than sitting after it. A player using a font without proper Bangla support shows the letters but fails to join them, so words come apart instead of disappearing.
Is that the same problem as a wrong file encoding?
No, and it is worth telling them apart. An encoding fault replaces characters with boxes or symbols across the whole file. A shaping fault leaves every character present and correct but renders conjuncts unjoined, so the text is readable-ish and subtly wrong. Confirm the file is UTF-8 first, then judge shaping in a player rather than in a text editor.
How should I check a Bengali caption file before publishing?
Open it in the actual player your audience will use, not just in the editor where you made it. Look at words with conjuncts specifically, since those are what break. A file that looks perfect in one application can render incorrectly in another purely because of the font in use.
What should I review in the caption text itself?
Names of people, places and channels first. Then English words spoken inside Bengali sentences, which usually belong as they were said rather than transliterated. Then line length, because Bengali sets long and a comfortable English line can overflow a vertical frame.
Does the same file work for Bangladesh and West Bengal?
The script is shared, so one subtitle file serves both. Some everyday vocabulary differs between them, so if a video is aimed squarely at one audience it is worth reading the draft with that in mind, but this is a wording judgement rather than a separate track.
What can I export?
Reviewed Bengali captions export as SRT or VTT subtitle files, plain text, or a captioned video. Keep the subtitle file even when you ship a captioned video, since it is the version you can still correct. Open the caption generator.
Start a Bengali caption track
Transcribe the video, review the wording and the line length, then export SRT, VTT, text, or a captioned video.