Hindi Text Broken After Word to PDF? How to Fix It
Hindi text that turns into boxes, wrong characters or jumbled shapes after converting Word to PDF is almost always a font problem, not a conversion bug. Legacy fonts like Kruti Dev store Hindi text using English keyboard mappings that only display correctly with that exact font installed, while Unicode fonts like Mangal encode the actual Hindi characters, which is why switching to a Unicode font usually fixes the conversion.
Hindi text that turns into boxes, wrong shapes or jumbled letters after converting Word to PDF is almost always a font problem, not a fault in the conversion tool itself. Legacy fonts like Kruti Dev map Hindi letters onto English keyboard keys in a way that only displays correctly with that exact font installed, while Unicode fonts like Mangal store the actual Hindi characters, which convert reliably to PDF.
Why this happens: legacy fonts versus Unicode
Fonts like Kruti Dev, Chanakya and several older DTP-era Hindi fonts were built before Unicode Devanagari support was common. They work by remapping ordinary English keyboard characters (A, B, C and so on) to look like Hindi letters, purely as a visual trick tied to that specific font file. Type the letter "d" in Kruti Dev and it displays as a Hindi character, but only because that font's design draws a Hindi shape for the "d" key.
The moment that text is viewed, printed or converted using a system that does not have the exact same font, or a system that treats the text as its actual underlying character rather than that font's picture, the illusion breaks. What you usually see instead is a jumble of English letters and symbols, since the underlying character was never actually a Hindi letter to begin with. Empty boxes or question marks are more often a sign that the converting system has no font with Devanagari glyphs for genuine Unicode text, which the next section covers.
If you regularly need to convert Hindi documents to PDF, the Word to PDF converter handles genuine Unicode Hindi text cleanly, since it works with the actual Devanagari characters rather than a font's visual trick.
Word to PDF
Same settings as the full tool page.
Files are uploaded over HTTPS, processed and deleted from our server straight after. Open the full Word to PDF page
How to tell which kind of font you are dealing with
- Select and copy the Hindi text, then paste it somewhere else like a plain text editor or a WhatsApp chat box. If it pastes as readable Hindi, it is Unicode. If it pastes as random English letters or symbols, it is a legacy font like Kruti Dev.
- Check the font name in Word's font box while the Hindi text is selected. Common legacy fonts include Kruti Dev, Chanakya, DevLys and Shusha. Common Unicode fonts include Mangal, Nirmala UI and Noto Sans Devanagari.
Step by step: fixing the PDF conversion
- Identify whether your document uses a legacy font or Unicode font, using the copy-paste check above.
- If it is Unicode already, the boxes or jumbling on conversion are more likely a missing font on the system doing the conversion. Try converting from a device that has the same Unicode font installed, or embed the font in the Word file before converting.
- If it is a legacy font like Kruti Dev, use a legacy-to-Unicode conversion tool (widely available for Kruti Dev to Mangal/Unicode specifically) to convert the underlying text, not just change the font name.
- After conversion, the text should now be genuine Unicode Devanagari. Change the font to a Unicode Hindi font like Mangal or Nirmala UI for a clean, standard look.
- Convert the corrected Word document to PDF using the Word to PDF converter.
- Open the resulting PDF and confirm the Hindi text displays correctly, and try copying a line of text from the PDF to double check it pastes as real Hindi elsewhere.
Why simply changing the font name does not work
A common first instinct is to select the Hindi text and change the font dropdown from Kruti Dev to Mangal, expecting the text to just display correctly. This does not work, because the underlying characters are still the original English letter codes; only the font used to draw those codes has changed. Mangal will render those same letter codes as its own (wrong) shapes, producing a different kind of gibberish rather than fixing anything.
The actual fix requires converting the underlying characters themselves from the legacy encoding into real Unicode Devanagari characters, which is what a proper legacy-to-Unicode converter does, as opposed to a font change.
Where this problem shows up most
This is especially common with older government forms, court documents, and DTP files originally typed in the 1990s and 2000s using Kruti Dev, which was widely used for Hindi typing in Indian government offices for years. If you are digitising an old typed Hindi document, converting it to Unicode first will save you from this exact problem every time you need to convert, search or edit that text again.
It also shows up when a document created on one computer, with a legacy font installed, is opened and converted on a different computer that does not have that exact font, even if the original author never noticed a problem on their own machine.
If you need to type fresh Hindi text instead
Rather than dealing with legacy fonts at all, type new Hindi content directly in a Unicode-friendly way using voice typing in Hindi, which produces standard Unicode text from the start and avoids this entire category of conversion problem. If you already have a scanned Hindi document rather than an editable Word file, converting a scanned Hindi PDF to Word covers that separate situation.
Common mistakes
- Changing only the font name from Kruti Dev to a Unicode font, expecting the text to fix itself.
- Not checking whether a document uses a legacy or Unicode font before troubleshooting a conversion issue.
- Converting on a device that lacks the specific legacy font, without first converting the text to Unicode.
- Assuming every "broken Hindi" issue is a PDF converter bug, when it is almost always a font encoding mismatch.
Tools for this
Frequently asked questions
Why does my Hindi text show boxes instead of letters after converting to PDF?
This usually happens because the original document used a legacy font like Kruti Dev, which maps Hindi shapes onto English keyboard characters rather than storing real Hindi characters, and that mapping breaks without the exact same font installed.
Does changing the font from Kruti Dev to Mangal fix broken Hindi text?
No. Changing the font name alone does not convert the underlying characters, so the text still displays incorrectly, just with different wrong shapes. You need to convert the actual character encoding, not just the font.
How can I check if my Hindi text is Unicode or a legacy font?
Copy the Hindi text and paste it into a plain text box, like a WhatsApp chat. Readable Hindi means it is Unicode; random English letters or symbols mean it is a legacy font.
Is Mangal a safe font to use for Hindi PDFs?
Yes, Mangal is a Unicode Devanagari font, which stores actual Hindi characters and converts and copies reliably across systems, unlike legacy fonts.
Can I fix this without retyping the whole document?
Yes, a legacy-to-Unicode conversion tool can convert Kruti Dev or similar text into genuine Unicode Devanagari without retyping, though you should always proofread the result afterward.
Sources
- Unicode Consortium, Devanagari code chart (checked 2026-09)
- Microsoft Typography: Mangal font (checked 2026-09)
- Microsoft Typography: Nirmala UI font (checked 2026-09)
Rules and limits change. Always check the latest official notification or portal before you submit a form.