You paste Urdu text into your video editor and get one of these: empty boxes (□□□), letters printed separately like a ransom note (ا ر د و), the whole line running left-to-right, or a stiff Arabic newspaper font that no Urdu reader would call natural. Here's what's actually going wrong — and the checklist to fix it.
The four ways editors mangle Urdu
1. Tofu boxes: the font has no Urdu glyphs
Fonts only contain the characters they contain. The trendy display font you use for English captions almost certainly stops at Latin. Ask it for ک and it shrugs — the renderer draws a placeholder box ("tofu"). Fix: Urdu text needs an Urdu-capable font on that specific text layer.
2. Ransom-note letters: no text shaping
Urdu letters join, and change shape by position — ک looks different at the start, middle and end of a word. Turning "کتاب" into its joined form is a rendering step called shaping. Cheap text engines skip it and print each letter in isolated form. This is the classic sign of an editor that was never tested on Arabic-script text — and it's unfixable from inside that app.
3. Backwards text: no BiDi support
Urdu runs right-to-left, but the digits and English words inside it run left-to-right. Handling that mix is the bidirectional algorithm. Engines without it print your sentence in reverse or scramble the English words' position.
4. It renders… but in Naskh
The subtle one. Most "Arabic" fonts are Naskh — flat, horizontal, the style of Arabic newspapers. Urdu readers expect Nastaʿlīq — the flowing, diagonal calligraphic style of every Urdu book and news channel. Naskh Urdu is readable but feels foreign, the way English set entirely in Fraktur would. If your captions look "technically Urdu but somehow off", this is why.
The checklist for correct Urdu captions
- Font: a true Nastaʿlīq face — Noto Nastaliq Urdu (free, by Google) or Jameel Noori Nastaleeq.
- Line height: Nastaʿlīq hangs deep below the baseline — increase line spacing ~1.5× or descenders collide.
- Short lines: 4–6 words; the diagonal flow needs horizontal room.
- Test a mixed line: paste "یہ AI tool بہت اچھا ہے 100%" — if the English and digits sit correctly inside the RTL line, the engine does BiDi properly.
- Burn in, don't upload SRT: platform caption renderers pick their own font — usually Naskh — throwing away everything above.
The shortcut
Doing this by hand in a generic editor is possible; it's just work you repeat every video. Procaply ships all of it as the default: real Nastaʿlīq rendering with correct shaping and BiDi, sized and spaced for vertical video, previewed exactly as it burns — plus the transcription so you're not typing the Urdu in the first place. What you see in the editor is pixel-for-pixel what exports, because the same rendering rules draw both.
FAQ
Why does the same font work in Word but break in my editor?
Word uses the OS text stack (full shaping); many video tools use game-style engines that trade correctness for speed. The font was never the problem.
Can I mix Urdu and English captions in one video?
Yes — that's normal desi content. The requirement is per-line font switching and BiDi, which purpose-built caption tools handle automatically.