Nepali Unicode and Devanagari Typography on the Web

Every Nepali web developer has received this call: "Our site is showing boxes instead of Nepali." Getting Nepali Unicode fonts right on a website is genuinely a solved problem in 2026, yet broken Devanagari is still everywhere, on school sites, on cooperative notices, on menus. The fixes are simple once you understand the two separate things that go wrong: the encoding and the font.

First, the Preeti problem: it was never Nepali

Preeti and its cousins (Kantipur, Himali) are not Nepali fonts in the modern sense. They're English fonts wearing a costume: type "s" and the font draws क. The text underneath is still gibberish Latin characters. Paste it into a website, a phone, or Google, and without that exact font installed you get nonsense. Search engines can't read it. Screen readers can't speak it. If your old content lives in Preeti, run it through a Preeti-to-Unicode converter before it goes anywhere near a website. This is non-negotiable, and it's the first thing WebsNP checks when migrating old sites.

The fonts that actually work

Real Unicode Devanagari webfonts, all free on Google Fonts:

• Noto Sans Devanagari: Google's workhorse. Complete conjunct coverage, many weights, never surprises you. Our default for body text.
• Mukta: designed for Devanagari-Latin pairing, slightly warmer than Noto. Excellent for headings and body alike.
• Hind: clean and compact, good for dense UI text like menus and buttons.
• Poppins or Inter alongside: for the English half of bilingual sites, paired deliberately so the two scripts feel related, not clashing.

Load only the weights you use. Each Devanagari weight is heavier than a Latin one because of conjunct glyphs, and three unnecessary weights can add real seconds on a 4G connection outside the Ring Road.

Typography rules Devanagari quietly demands

Devanagari hangs from the top line and dives below the baseline, so it needs air. We set line-height around 1.7 to 1.8, versus 1.5 for English. Font size usually needs a step up too: 17 to 18 pixels where English body text sits at 16. Avoid tight letter-spacing entirely; it breaks the shirorekha, that connecting top line, and makes text feel wrong in a way readers can't name. Bold sparingly, many Devanagari fonts get muddy at heavy weights on low-end phone screens, and low-end phones are most of your Nepali traffic.

Loading strategy matters as much as font choice. Always set font-display to swap so visitors see text in a fallback font immediately instead of staring at blank space while the webfont downloads over 4G. Preload the one Devanagari weight your body text uses. And if your Nepali content is limited, a notice section, a tagline, a menu, consider subsetting the font to just the glyphs you need; a full Devanagari font file can weigh several hundred kilobytes, and a subset a fraction of that. These sound like micro-optimisations until you watch someone open your site on a bus past Kalanki with one bar of signal. Then they're the difference between a visitor and a bounce.

Testing: trust devices, not your design file

Devanagari rendering differs across Windows, Android and iOS more than Latin does. Conjuncts like क्ष and ज्ञ are the canaries: if a font stack is broken, they break first. We test on a cheap Android phone deliberately, because that's what a huge share of Nepali visitors hold. Also declare charset UTF-8 in your HTML and ensure the database uses utf8mb4, or your CMS will happily eat Nepali characters on save and replace them with question marks. Half of "font problems" are actually database encoding problems.

Getting it done properly

None of this is expensive, it's just fiddly, and it's exactly the kind of detail that separates a professional build from a cheap one. Every Nepali-language site WebsNP delivers ships with Unicode-clean content, a tested Devanagari font stack, correct encoding end to end, and on-page SEO that lets Google actually index your Nepali text. Fixed-price quote within 24 hours, sites delivered in 2 to 7 days, free domain and first-year hosting on our NVMe servers, free SSL and daily backups included. If your current site shows boxes, send us the URL. Diagnosing it takes us about five minutes, and we'll tell you for free.