If you've worked with Marathi text on a computer for more than a few years, you've probably run into all three of these names — Unicode, Kruti Dev, and Shree Lipi — usually while trying to figure out why a document looks fine on one computer and turns into gibberish on another. They're not competing "font styles" the way Modak and Baloo 2 are; they're fundamentally different systems for encoding Devanagari text, and mixing them up is the single most common cause of broken Marathi text online. Here's what each one actually is.
Unicode — The Modern Standard
Unicode is a universal character-encoding standard that assigns every character in every major writing system — including Devanagari — a unique, permanent code point. When you type "न" in a Unicode-compliant app, the computer stores the actual character "न," not a substitute. Any Unicode Devanagari font — Noto Sans Devanagari, Hind, Tiro Devanagari Marathi, and every font in our generator — can then display that same stored character correctly, regardless of which specific font is applied. This is why Unicode Marathi text works everywhere: in a Google search, on any phone, in any app, without needing a specific font installed. It's the only system used by modern websites, WhatsApp, Instagram, and current versions of Microsoft Office.
Kruti Dev — The Legacy DTP Standard
Kruti Dev, created in the 1990s before Indian-script Unicode support matured on Windows, takes a completely different approach: it remaps Devanagari-looking glyph shapes onto ordinary English keyboard keys (essentially the ASCII/Latin character set). Typing "H" in a Kruti Dev-applied text box doesn't produce the actual character stored as "H" — it visually displays a Devanagari glyph, but under the hood, the computer still thinks it's storing the letter H. This only looks correct if the exact Kruti Dev font is installed and applied to that specific text. Move the same text to a device without Kruti Dev installed, or paste it into a Unicode-expecting field like a website or WhatsApp, and it reverts to showing the literal English letters — gibberish to anyone reading it. Kruti Dev remains common in government offices, courts, and older DTP (desktop publishing) workflows across Maharashtra and North India, largely because of decades of typist training on its specific keyboard layout.
Shree Lipi — A Parallel Legacy System
Shree Lipi works on the same basic principle as Kruti Dev — it's also a non-Unicode, glyph-substitution font system rather than a true character encoding — but it uses a different internal key mapping and was developed by a different company (Chitrangi Softwares) for its own suite of DTP tools. Because Kruti Dev and Shree Lipi map keys to glyphs differently, text encoded in one is not automatically compatible with the other, even though both visually produce Devanagari-looking output. A document typed in Shree Lipi needs a Shree Lipi-aware conversion process to become Unicode — it can't simply be run through a Kruti Dev converter and expected to work, because the underlying key mappings don't match.
Side-by-Side Comparison
| System | Type | Works Without the Exact Font? | Searchable / Web-Friendly? |
|---|---|---|---|
| Unicode | True character encoding | Yes | Yes |
| Kruti Dev | Glyph substitution | No | No |
| Shree Lipi | Glyph substitution | No | No |
Which One Should You Actually Use?
For any new project — a website, a WhatsApp business account, a document you'll share digitally, social media content, anything searchable — the answer is always Unicode. There's no practical downside to it anymore; every modern device and app supports it natively, and it's the only system that guarantees your Marathi text displays correctly for every single reader without exception.
Kruti Dev and Shree Lipi are only relevant today if you're dealing with an existing legacy document — an old court file, a historical newspaper archive, an old DTP project — that was originally created in one of these systems and needs to be preserved or reused. In that case, the right move isn't to keep working in the legacy format, but to convert the text to Unicode once and work in Unicode going forward.
Converting Legacy Text to Unicode
Our Kruti Dev to Unicode Converter handles exactly this — paste Kruti Dev-encoded text and get clean, correct Unicode Devanagari Marathi text back instantly, ready to use anywhere. For Shree Lipi-specific content, you'll need a Shree Lipi-aware converter or software, since its key mapping differs from Kruti Dev's and the two aren't interchangeable.
Frequently Asked Questions
Can I tell which system a piece of text is in just by looking at it?
Visually, no — all three can look like normal Devanagari on screen if the right font is applied. The real test is copying the text into a plain text editor or a different app with a different font; Unicode text stays correct, while Kruti Dev or Shree Lipi text turns into English letters and symbols.
Is one of these "better quality" Devanagari than the others?
Not in terms of visual design — plenty of Kruti Dev and Shree Lipi typefaces are visually attractive. The difference is purely technical: how the text is stored and whether it's portable across devices, which is where Unicode wins decisively for any modern use.
Do government offices in Maharashtra still use Kruti Dev?
Many legacy systems and older workflows still do, largely due to trained typing staff and existing document archives, though the broader shift across government digitisation initiatives has been steadily moving toward Unicode for new documents.
Paste Kruti Dev text — get clean Unicode instantly, free.