Common Urdu Font Problems & How to Fix Them

Urdu text turning into boxes, letters refusing to join, or a font that simply will not appear is almost never a mystery — it is one of a handful of causes, and each one has a specific fix. This is the complete troubleshooting guide for Urdu fonts on UrduFontss.net: find your symptom below, jump to its section, and apply the fix step by step. If several of our font pages sent you here from their troubleshooting sections, this is the page they mean.

For the background — why Unicode fonts behave the way they do, and why old non-Unicode (legacy) fonts break on modern systems — read our explainer on proper Unicode support and Urdu font issues. This guide is the practical companion: less theory, more fixing.

Quick Diagnosis: Match Your Symptom

Why Urdu Font Problems Happen

Urdu is a right-to-left language written in a script where most letters change shape and join to their neighbours. For that to render correctly, four things must line up at the same time:

• Unicode text — the characters themselves must be real Unicode Urdu characters, not letters borrowed from a legacy font’s private encoding.
• A Unicode Urdu font — the selected font must actually contain Urdu glyphs and joining rules.
• An Urdu-capable keyboard — so the characters you type are the right ones.
• App support for complex scripts — the software must shape and join the letters; not every app does this equally well.

When any one of the four is missing, you get one of the symptoms below. The good news: each symptom points at its missing piece, so work through the matching section rather than reinstalling everything at random.

Problem 1: Urdu Text Shows as Boxes (Tofu)

What it looks like: every Urdu letter is replaced by an empty rectangle — □□□□ — sometimes called tofu.

Cause: the font currently applied to the text contains no Urdu characters at all, so the system has nothing to draw. This also happens when Unicode Urdu text is pasted into a document set in a Latin-only font.

Fix:

1. Select the boxed text and apply a font that genuinely covers Urdu — a Unicode Nastaliq or Naskh font such as Jameel Noori Nastaleeq or Urdu Naskh Unicode.
2. If the boxes appear everywhere on the device (not just one app), the system font has no Urdu coverage — on Windows and Android this is rare; on older software, update the app or the system.
3. If the boxes appear only after pasting text from an old file, the source text may not be Unicode at all — go to Problem 6.

Problem 2: Urdu Letters Are Not Joining

What it looks like: the letters are the right ones, but each stands alone, disconnected — the word looks broken apart instead of flowing.

Cause: correct joining (called shaping) is done by the app, not the font alone. If the app does not fully support complex scripts — or if the text was typed with a legacy font — the letters stay in their isolated forms.

Fix:

1. Retype a test word with a Unicode font and a proper Urdu keyboard. If the retyped word joins correctly, the original text was legacy-encoded — see Problem 6.
2. In design apps, enable the right text engine: in Photoshop, choose the World-Ready Layout / Middle Eastern features (Preferences > Type, then the paragraph panel’s shaping options) and restart Photoshop.
3. In simple editors and some mobile apps, joining support is limited by the app itself. Test the same text in Word or in our live Urdu font preview tool — if it joins there, the app is the limit, not your font.
4. For the theory of why some text can never join without conversion, read how proper Unicode support works.

Problem 3: Font Not Showing in the App List

What it looks like: you installed the font, other programs see it, but the app you need does not list it.

Cause: most apps read the font list when they start, and some apps (Canva, CapCut, KineMaster, PixelLab, Google Docs) do not use system fonts at all — they have their own font systems.

Fix:

1. Fully close the app (not just minimise it) and reopen it. This alone solves most cases in Word, Photoshop and video editors on PC.
2. Check the font really is installed: on Windows, open Settings > Personalisation > Fonts and search for its name; on Mac, open Font Book.
3. If the app has its own font system, the system install is not enough — import the font inside the app instead. Guides: Urdu fonts in CapCut, Urdu fonts in KineMaster, Urdu fonts in PixelLab, Urdu fonts in Canva.
4. Google Docs never accepts uploaded fonts — it uses Google Fonts only. See how to use Urdu fonts in Google Docs for the fonts it does offer.

Problem 4: Font Not Installing on Windows, Mac or Android

What it looks like: double-clicking the download does nothing, or the system reports the file is invalid or corrupt.

Cause: fonts on this site download as ZIP files. A ZIP is a container, not a font — the TTF inside it is the font. Install errors also come from incomplete downloads.

Fix:

1. Extract the ZIP first (right-click > Extract All on Windows; double-click on Mac; Extract in your file manager on Android) and install the .ttf file inside.
2. On Windows, right-click the TTF and choose Install — or see our full PC font installation guide. On Mac, open the TTF in Font Book and choose Install Font.
3. If the error repeats, download the font again — an interrupted download corrupts the file.
4. On Android there is no system-wide Install button for a TTF. Use the font inside an app that imports fonts (CapCut, KineMaster, PixelLab), as covered in Problem 7 and our Android font guide.

Problem 5: Urdu Font Broken in Microsoft Word

What it looks like: Urdu text in Word shows wrong shapes, reversed order, cut-off Nastaliq lines, or switches font by itself.

Fix:

1. Set the paragraph direction to right-to-left and alignment to right while typing Urdu (Home tab > paragraph direction buttons, visible when an Urdu or Arabic keyboard is active).
2. Make sure the keyboard is the Windows built-in Urdu (Pakistan) layout — if you do not have it yet, follow our Urdu keyboard installation guide.
3. If Nastaliq lines overlap or get cut, increase the line spacing (Line Spacing Options > Multiple, around 1.5 or higher) — tall Nastaliq glyphs need more vertical room than Latin text.
4. If Word keeps switching back to another font, the document’s complex-script font is set separately: select the text, then in the Font dialog set the Complex scripts font to your Urdu font as well.
5. If the text came from an old InPage-era document and shows as symbols, it is legacy text — go to Problem 6.

Problem 6: Old or Legacy Font Text Breaking (InPage-Era Text)

What it looks like: a document that looked fine years ago now shows random Latin letters, symbols, or unjoined Urdu — usually after moving to a new computer, a new app, or a Unicode font.

Cause: older Urdu software such as InPage stored text in the legacy font’s own character arrangement instead of Unicode. That text only displays correctly with the original legacy font installed; anywhere else it breaks — and simply changing the font cannot repair it, because the underlying characters are different.

Fix:

1. To view the old document as it was: install the same legacy font it was written with, and open it in software that tolerates legacy fonts (InPage itself, or Word with the font installed).
2. To reuse the text in modern apps: the text must be converted from the legacy arrangement to Unicode characters first. After conversion it works in every modern app with any Unicode Urdu font.
3. To avoid the problem in new work: always type new Urdu text in Unicode with a Unicode font. The difference is explained in our Unicode support explainer.

Problem 7: Font Not Working on a Phone

What it looks like: the font works on your PC, but on your phone nothing changes — or an app shows a default font instead of yours.

Cause: Android and iPhone do not let a downloaded TTF replace the system font the way Windows does. On phones, fonts work inside apps that support importing them. Expecting the phone’s menus or WhatsApp to change font will not work from a TTF file.

Fix:

1. Download the font ZIP on the phone and extract the TTF (see Problem 4).
2. Import the TTF inside the app you are designing in — the steps differ per app: CapCut, KineMaster and PixelLab all support this.
3. Add the Urdu keyboard to your phone keyboard (Gboard: Settings > Languages > Add keyboard > Urdu) so you can type real Urdu text for the font to display.
4. On iPhone, use apps that import fonts or a font-installer app that installs a configuration profile; there is no direct “install TTF system-wide” option on iOS.

Problem 8: Problems in Canva, Photoshop, CapCut and Other Apps

Canva: custom font upload requires a paid Canva plan (Pro, Teams, Education or Nonprofits) — the free plan cannot upload fonts. Canva also struggles with Nastaliq shaping in some layouts; if letters break, try a Naskh-style Unicode font and check our full Canva Urdu fonts guide for the workarounds.

Photoshop: if Urdu pastes in reversed or unjoined, switch the text engine to the World-Ready layout and enable Middle Eastern features (see Problem 2), then restart Photoshop before testing.

CapCut / KineMaster / PixelLab: these apps only use fonts you import into them (mobile) or that are installed on the system (CapCut desktop). A font that “does nothing” usually was never imported — follow the app guides linked in Problem 3.

Google Docs: no upload exists; use its built-in Arabic-script fonts (Noto Nastaliq Urdu and others) — full method in the Google Docs guide.

Problem 9: Garbled Text and Question Marks (Encoding)

What it looks like: Urdu text becomes question marks (????), strange accented Latin characters, or a mix of both — often after saving a file, moving text between apps, or opening a file from someone else.

Cause: the file was saved or read with a non-Unicode encoding. Once real characters have been replaced by question marks in the saved file, that damage is permanent in that copy — the original file is needed.

Fix:

1. In text editors, always save Urdu text as UTF-8 (in Notepad: Save As > Encoding > UTF-8).
2. If a file opens garbled in one app, reopen it choosing UTF-8 encoding explicitly, or open it in a browser and copy the text from there.
3. When sending Urdu text to someone, send it as pasted text or a properly saved document — not through tools that strip non-Latin characters.

App-by-App Quick Fixes

When the Font Itself Is the Problem

Sometimes every setting is right and one particular font still misbehaves — a damaged file, an incomplete character set, or a legacy font being asked to do a Unicode job. Test with a known-complete Unicode font: if Jameel Noori Nastaleeq (Nastaliq) or Urdu Naskh Unicode (Naskh) renders your text correctly in the same app, your setup is fine and the first font is the problem — replace it. You can compare how fonts handle your own text before downloading with the live preview tool, and browse reliable Unicode fonts in the Urdu fonts category. Decorative fonts such as Zohra Unicode and Xebec Unicode suit headings and short text better than long paragraphs — if body text looks odd, the font choice, not your system, may be the whole issue.

Quick Checklist Before You Ask for Help

• The ZIP was extracted and the actual .ttf file was installed or imported.
• The selected font is a Unicode Urdu font (not a legacy font).
• The app was fully closed and reopened after installing.
• The text was typed with an Urdu keyboard, in a right-to-left paragraph where the app supports it.
• The same text was tested in a second app to separate a font problem from an app problem.

If you work through the section for your symptom and the checklist above, the large majority of Urdu font problems are solved. For anything still stuck, the Unicode support explainer covers the deeper causes, and each app’s dedicated guide (linked throughout this page) covers its own quirks.

Frequently Asked Questions (FAQs)