Preeti to Unicode conversion rebuilds an old Preeti document as searchable Unicode Devanagari (Nepali) entirely inside your browser. Paste the legacy text, press Convert, and copy a Unicode string that any search index, database, or modern app can store and read. प्रीति फन्टको पुरानो फाइललाई खोज्न मिल्ने युनिकोडमा।Free, no account
On the left, the raw bytes a device renders without the Preeti font. On the right, the identical text once remapped into the U+0900 Devanagari block as Unicode.
Turning a frozen Preeti archive into data a computer can read
A Preeti file is not really Nepali to a computer. It is a string of Latin keystrokes that only looks like Nepali while the Preeti font is painted over it. This preeti to unicode converter performs the one operation that frees the text: it remaps each legacy keystroke to its true Devanagari code point, so a document locked to one installed font becomes a Unicode string any search index, database column, or modern app can read. For two decades of Nepali typing, that remap is the gap between a searchable archive and files only one old machine can display. It all runs locally in your browser.
The reason a font swap never fixes this is that the data and the display were always two separate layers. Standards-based Nepali, written in the Devanagari script, stores each letter as a code point in the Unicode range U+0900 to U+097F, a 128-slot block defined in Unicode 1.0 back in 1991. A Preeti document stores none of those code points. It stores ASCII bytes in the 0 to 127 range and leans on the font to fake the script, which is exactly why the same bytes surface as gibberish such as g]kfn the instant the file leaves the one computer with Preeti installed.
Why legacy Nepali type and Unicode store letters so differently
Preeti belongs to a generation of 8-bit Nepali fonts built before Unicode reached Devanagari, when designers borrowed the 7-bit ASCII keyboard, with its 128 positions numbered 0 to 127, and assigned a Nepali glyph to each Latin key. It maps roughly 95 typeable positions, fewer than the 128 slots Unicode dedicates to Devanagari, so a single key sometimes has to stand in for more than one Nepali form, and complex stacked conjuncts are assembled by typing two or three keys in sequence. That design suited a 1990s typewriter-style layout, but it ties every byte to the font. Move the bytes without it and the meaning is gone.
Unicode took the opposite approach: one permanent number per character, independent of any font. A preeti to unicode pass rewrites display-bound keystrokes into those stable numbers, so the letter क is the value U+0915 on every device, whether rendered in Mangal, Kalimati, Noto Sans Devanagari, or a phone's built-in face. This is why Unicode, not Preeti, is what the Government of Nepal standardised for official electronic Nepali and what every search engine indexes. Preeti shares this ASCII-overlay trick with Hindi fonts such as Kruti Dev and Bengali fonts such as Bijoy, so each one needs its own remapping tool rather than a single universal switch.
Preeti to Unicode encoding compared, point by point
The table sets the legacy Preeti encoding beside the Unicode target so you can see exactly what the conversion changes and why search, databases, and modern apps only accept one of the two. Treat the figures as the defining properties of each scheme, not as quality scores.
Property
Preeti (legacy font)
Unicode Devanagari
What a byte stores
An ASCII keystroke position (0 to 127)
A character code point (U+0900 to U+097F)
Encoding era
1990s 8-bit font, pre-Unicode
Devanagari block added in Unicode 1.0, 1991
Readable without its font
No, shows as Latin gibberish
Yes, on any Unicode device
Searchable and sortable
No, indexes see only ASCII
Yes, indexed as real Nepali
Typeable slots used
About 95 keyboard positions
128 code points in the block
Official Nepali standard
No, legacy print and DTP only
Yes, the modern electronic standard
The one-line version for a citation
In short: Preeti hides Nepali inside about 95 ASCII keystroke slots that mean nothing to a search engine or a database, while Unicode assigns each Devanagari letter a fixed code point in the U+0900 block, defined since 1991, that every system reads natively. A preeti to unicode pass rewrites the first scheme into the second, which is the only form modern software will index, store, or display correctly.
Preeti to Unicode in 4 steps: digitize a document
The preeti to unicode flow below is a sub-minute job with nothing to install, and the steps line up one to one with the converter at the top of the page.
Paste the Preeti text. Drop the scrambled-looking Nepali into the left box, or type it there if you only have a printout. Everything stays on your device.
Press Convert. The page remaps each legacy keystroke to its Unicode Devanagari code point and writes readable Nepali into the right box in about a second.
Copy the Unicode output. Use the Copy output button to lift the converted text, ready to paste into a database field, a CMS, a spreadsheet, or a Word document in any Unicode font.
Verify the record. For anything official, read names, dates, numbers, and stacked conjuncts against the original Preeti before you publish or import, since a few legacy keystrokes are ambiguous.
Where digitized Unicode unlocks something Preeti never could
Once an archive is Unicode, capabilities that were impossible on the legacy font switch on at once, and that is usually the real reason a team converts. The clearest gain is full-text search: a database can index Unicode Nepali and return the right citizenship record or news clipping, whereas a Preeti column only ever held meaningless ASCII. The text also becomes sortable in true Devanagari order, copyable into any modern application, and readable by screen readers, which matters for accessibility and for any public portal.
We see the same migration triggers repeat across the files people bring to our team. A newsroom wants decades of Preeti-typed reporting findable on its own website. A government office is moving paper-era records into a system that only accepts Unicode. A researcher needs to run analysis over a Nepali corpus that is currently trapped in DTP files. In every case the pixels were fine and only the encoding blocked the work, so a preeti to unicode pass clears the blockage without retyping a single line.
Which legacy Nepali fonts this digitizer reads
Preeti is the dominant one, and because several other Nepali legacy families were built on the same ASCII overlay, this preeti to unicode converter reads them the same way. Kantipur, PCS Nepali, and Sagarmatha share Preeti's keyboard layout closely enough that their text usually remaps to clean Unicode without any change of setting, which is handy when an old archive mixes fonts across files. Paste the text and a correct Nepali result confirms the family.
Two honest limits are worth naming before you trust a batch. First, this tool targets the Nepali Preeti layout, so a genuinely different mapping, including most Hindi Kruti Dev material, belongs in its own converter rather than this one. Second, a few legacy keystrokes are inherently ambiguous because Preeti packs Nepali into fewer slots than Unicode provides, so half-letters and stacked conjuncts are where a damaged source can drift. Work through long documents a few hundred words at a time and proofread those specific letters, and the result is dependable enough to import into a live system.
Preeti to Unicode: questions from people digitizing archives
Reading and indexing the result
Why does my old Preeti file show as English letters?
Because a Preeti document holds ASCII keystroke positions instead of genuine Devanagari, and the Preeti font alone supplied the Nepali shapes on top. Strip that font, as any other device does, and the underlying bytes appear as scrambled Latin like g]kfn where you expected नेपाल. The data is intact; the machine is just printing the raw bytes. A conversion to Unicode maps those positions onto real code points in the U+0900 range, which then render on any phone or app with nothing installed. Reassigning the font inside Word cannot fix it either, since that restyles one view while the saved bytes remain in their keystroke layout.
Will the converted text be searchable in a database or Google?
Yes, and that is the main reason to digitize a Preeti archive. Unicode Nepali is indexed as genuine Devanagari, so once you store the converted text in a database column or publish it on a page, a query can match it, sort it, and rank it like any modern content. Preeti text is effectively invisible to search because an index only sees the Latin keystroke bytes, not Nepali, so it finds nothing meaningful. Migrating records, articles, and documents from Preeti to Unicode is what finally makes decades of Nepali writing findable, both inside your own systems and on the open web.
Mixed content and accuracy
Only part of my document converted into Nepali. Is that a bug?
No. A mixed file behaves exactly this way. Roman-script names, addresses, dates, and numerals were keyed as plain ASCII and never carried a Preeti mapping, so they survive the pass untouched while the Nepali spans are rewritten into Devanagari. Your job is just to keep the rewritten Nepali, leave those Latin tokens and figures alone, and stitch the record back together. Both the Devanagari letters and the digits land in their proper form. When a stretch you assumed was Nepali stays Latin, that stretch was likely keyed in a different scheme entirely, so verify which font produced that one span before you load it into your system.
It is an official record. How carefully should I check it?
For anything binding, treat the conversion as a draft to verify. Preeti splits half-letters and stacked conjuncts across two or three keystroke positions, and it packs Nepali into about 95 slots against Unicode's 128, so those letters, along with matras like इ, ई, उ, ऊ and र्, are where a damaged source can drift. Process the document in small chunks, then proofread proper nouns, legal terminology, calendar dates, and figures letter by letter against the original Preeti, and hold on to the source file until the Unicode checks out. For citizenship paperwork, court notices, and certificates, that careful pass is what separates a trustworthy record from a misspelled name.
Fonts, formats, and privacy
Which Nepali legacy fonts can it read besides Preeti?
Preeti leads the field, and the related Nepali families that reuse the same ASCII keyboard overlay, namely Kantipur, PCS Nepali, and Sagarmatha, are handled too. Sharing that layout means their bytes generally resolve to clean Unicode by the identical route, which is useful when one archive spans several fonts. Paste the text and the Devanagari surfaces, set for storage, web, and indexing. Should a passage still come out garbled, it was almost certainly keyed in a separate encoding, most Hindi Kruti Dev included, so inspect the original or ask its author which exact legacy font was in use.
After converting, which font do I pick in Word?
Once the text is Unicode, paste it into a modern Word document and choose any Unicode Devanagari font, such as Mangal, Kalimati, or Noto Sans Devanagari, and the Nepali reads correctly. Do not reach for legacy Preeti here, because the content is now true Devanagari code points instead of keystroke slots, and reapplying Preeti would corrupt it once more. If your goal is the reverse, putting clean Nepali back into the old Preeti layout for a print or DTP pipeline, that is a separate task handled by the Unicode to Preeti converter instead of this one.
Devices, batches, and privacy
Does it run on a phone, and is anything I paste stored?
It works on phones, and not a single character you paste leaves your handset. Because the whole conversion executes inside the browser, the Unicode result is precisely what mobile keyboards, chat apps, mail, and websites already accept, turning a stranded Nepali file into something shareable within seconds. Most phones cannot render Preeti at all, the legacy face simply is not present, yet the converted Unicode displays cleanly on Android, iOS, and every messenger. With no account and no cap, even sensitive letters, archives, and government paperwork remain private on your device throughout the digitization.
Can I convert a long document or many files in a row?
Yes. No character limit and no per-file quota apply, since every conversion is local work the browser handles. For accuracy on a lengthy record, feed it a few hundred words at a time so you can verify each batch of conjuncts and matras before continuing, then assemble the checked Unicode in your destination system. For bulk digitization, push files through back to back with no pause between them. The result is plain Unicode text, dropping directly into a spreadsheet cell, a database field, or a CMS with no reformatting needed.
How this converter is verified and sourced
Ash S, Localization Tools Engineer, maintains this preeti to unicode converter and re-tests the Nepali mapping whenever the conversion kernel changes. Last verified: 2026-06-26.
Our check is deliberately concrete. We run a spread of real Preeti material through the tool, a government-style record, a newspaper paragraph, and a mixed file with English names and dates, then we compare every converted line against the source character by character, watching the stacked conjuncts and matras most closely. Our team ships a change only after that batch reads correctly and the Unicode imports cleanly into a test database. The encoding facts above trace to the public references listed here, and we move the verified date only when this preeti to unicode converter changes in a way you would notice.
Devanagari, the script Nepali is written in and the target of this conversion.
Nepali language, the language whose legacy Preeti files this tool digitizes.