Nepali Unicode vs Preeti font: what's the difference (and how to convert)

If you've ever opened an old Nepali document and seen something like "g]kfn" instead of "नेपाल", you've met the Preeti problem. The fix is usually quick: convert the text to Unicode. Understanding why it happens helps you avoid it in your own files.

What Preeti actually is

For about two decades, Preeti was the default Nepali font in newspapers, government offices, school textbooks, and publishing houses, along with cousins like Kantipur, PCS Nepali, and Sagarmatha.

The catch is in how it works. Preeti is a font hack: it maps Nepali (Devanagari) glyphs onto ordinary ASCII character codes. So when you type what looks like नेपाल in Preeti, the bytes you actually save are the Latin characters g]kfn. They only look like Nepali because the Preeti font draws Nepali shapes in place of those Latin letters.

Take the font away by opening the file on a phone, pasting it into a website, or emailing it to someone, and the disguise falls away. You see the raw Latin characters, which read as nonsense.

What Unicode does differently

Unicode encodes each Devanagari character by its real identity. The letter न is stored as न, not as a Latin stand-in. Because every modern operating system and browser understands Unicode, Nepali Unicode text:

• displays correctly everywhere, with no special font to install,
• is searchable (you can actually find नेपाल with a search box),
• copies and pastes cleanly between apps, and
• works in URLs, social media, and databases.

This is why Unicode replaced Preeti for anything digital. The trouble is that decades of .doc, .pdf, and .txt files are still trapped in Preeti.

Preeti vs Unicode at a glance

• Preeti: Latin/ASCII bytes drawn as Nepali by a specific font. Looks right

only where the font is installed. Common in legacy print documents.

• Unicode: true Devanagari characters. Looks right everywhere. The standard

for websites, phones, and modern documents.

How to convert

Converting isn't a simple letter swap. Nepali script has half-forms, the ि matra that reorders, reph, and conjuncts like क्ष, त्र, and ज्ञ that need special handling. A good converter applies the established character map and those post-processing rules so the output is correct rather than merely approximate.

• Preeti → Unicode: modernize an old document so it displays and searches

correctly.

• Unicode → Preeti: for a print template or legacy workflow that still

requires Preeti.

• Roman → Unicode: type Nepali by sound, so "namaste" becomes "नमस्ते",

without learning a keyboard layout.

Paste your text, pick the direction, and check the output against the original for the conjuncts above, which is where weaker converters slip.

Which one should you use?

For anything new (a website, a report, a social post, a form), use Unicode. It's portable, searchable, and won't turn into gibberish on someone else's device. Reach for Preeti only when you're reading or feeding an older system that still depends on it.

If the document you're converting also contains dates, remember those follow the Nepali calendar. Once the text is readable in Unicode, the complete Bikram Sambat guide and how to convert Nepali dates accurately cover turning those into Gregorian dates correctly.

Key takeaways

• Preeti maps Nepali glyphs onto ASCII codes, so Preeti text is really Latin

characters that look like Nepali only where the font is installed.

• Unicode encodes real Devanagari characters, so it displays correctly

everywhere and is searchable, with no font to install.

• Use Unicode for anything digital. Reach for Preeti only to read or feed a

legacy system.

• Accurate conversion handles half-forms, the ि matra, reph, and conjuncts like

क्ष, त्र, and ज्ञ, so check those in the output.