How to Add Urdu Subtitles to a YouTube Video

YouTube is one of the few places a creator publishing in Urdu can ship a real subtitle track rather than captions burned into the picture. That is worth using. A separate track can be turned on and off, it sits alongside the video instead of covering it, and you can add more than one language to the same upload.

Decide the script before you generate anything

Urdu video captions come in two forms and they are not interchangeable.

• Urdu script, written right to left in the Nastaliq or Naskh alphabet. This is what a formal channel, a news clip, or an audience that reads Urdu properly will expect.
• Roman Urdu, which is Urdu written in Latin letters. A lot of Pakistani social audiences read this faster than Urdu script, and it is the normal register for casual and comedic content.

Pick one per track. Mixing them inside a single subtitle file reads badly and makes review harder. If you want both, generate them as two separate language tracks. Start Urdu script in the Urdu subtitle generator and Latin script in the Roman Urdu caption generator.

Uploading the track in YouTube Studio

The path in YouTube Studio is the video, then Subtitles, then Add Language. Choose the language, click Add under the subtitles column, and upload the file. YouTube reads the timestamps from the file, so the track lines up with the video without you syncing anything by hand.

Two details matter more for Urdu than for English uploads. Save the file as UTF-8, because Urdu script written in any other encoding arrives as boxes or question marks. And label the track with the language it actually contains: an Urdu script file belongs on the Urdu track, while a Roman Urdu file is still Urdu content and confuses viewers if you file it under English.

Review the words before the track goes live

Automatic transcription of Urdu speech gets the shape of a sentence right far more often than it gets the specific words right, and a subtitle track is read closely by exactly the people who will notice. Read the draft through once with these in mind.

• Names of people, places, channels and sponsors. These are the errors viewers comment on.
• English words inside Urdu speech. Most Pakistani creators code-switch constantly, and a transcript that forces every English word into Urdu spelling reads as wrong.
• Roman Urdu spelling consistency. There is no single agreed spelling, so pick one form of each common word and keep it the same across the file.
• Line length. A line that fits comfortably in English can run past the frame in Urdu script.

What to do about the platforms that will not take a file

A subtitle track only works where the player supports one. YouTube does. Short-form feeds mostly do not, so the same video going to Reels, TikTok or a WhatsApp status needs the captions rendered into the picture instead. Export a captioned video for those and keep the subtitle file for YouTube and your archive. The guide to burned-in and separate subtitles covers when to use which.

A workflow that does not need retyping

Generate the caption draft from the video, correct the wording and the timing while the text is still editable, then export once per destination. That keeps one reviewed source of truth instead of three drifting copies. Start in the caption generator, which exports SRT and VTT for the YouTube track alongside a captioned video for the platforms that need one. If you are taking the same Urdu captions into a mobile edit, the CapCut import guide covers that route.