Preeti to Unicode Converter

Convert old Preeti font into readable Nepali Unicode for web, mobile, and email. प्रीतिबाट युनिकोडमा।

Preeti text (paste/type)
Unicode output

Legacy Devanagari keyboard layouts

A reference for the old Devanagari typewriter layouts, Kruti Dev 010, Remington, and Inscript. When Nepali text was typed in the Preeti legacy font, recover it to readable Unicode with the converter above; this pad is only a layout reference.

Devanagari
keyboard

These are the old Devanagari typewriter layouts, Kruti Dev 010, Remington, and Inscript, kept here as a typing reference. When Nepali text was typed in the Preeti legacy font, recover it to readable Unicode with the converter above. Anything you type on this pad stays out of the recovery panel above.

Devanagari glyph ASCII keystroke
Reference pad Stays out of the recovery panel
q
w
k
h
w
c
g
x
n
t
M
ks
s
~
िf
q
i
j
d
r
p
V
a
e
u
o
y
l
;
'k
Shift

Maintained by , working with the Unicode2KrutiDev team. The Preeti and Kantipur recovery paths are checked against real Nepali office and newsroom files before they ship.

पुरानो नेपाली फाइलका लागि

What preeti to unicode actually recovers

The preeti to unicode tool reads old Preeti Nepali typing and rebuilds it as real Unicode you can put on a website, open on a phone, search in Google, or drop into Word. It is free, with no sign-up and no limit. प्रीतिमा टाइप गरिएको पुरानो नेपाली फाइल फेरि पढ्न मिल्ने बनाउँछ। You paste the scrambled-looking text, the readable Nepali appears beside it, and from there the recovered file behaves like any modern document, no Preeti font required.

Most people open the tool because an old Nepali file suddenly looks wrong on a new computer or phone. The fastest way in is to match the symptom you see to its cause and fix. Every card below is one of the recovery situations readers most often hit, from district office clerks to newsroom archivists. In each one a preeti to unicode converter is doing the same quiet job: turning the keystrokes the old font hid back into letters a modern phone can read on its own.

Six symptoms, and the fix for each

Find the symptom your old Nepali file shows, read why it happens, and do the fix. These are the cases that never paste cleanly on the first try.

Problem: Nepali shows as English everywhere

If the file reads as g]kfn or ;dfrf/, it holds Preeti keystroke bytes and the Preeti font is not installed on this device. Paste the whole thing into the input box; the readable Nepali Unicode appears beside it, then copy that out. Nothing is corrupted, the device is simply printing the raw bytes.

Only part of the text turned into Nepali

Common in a mixed file: it carries Preeti alongside plain English names, dates, and figures. That is correct behaviour, English words and numbers were never Preeti, so leave them and recover only the Nepali parts, then rejoin everything.

Common issue: text copied from a PDF

PDF copy adds stray line breaks and re-orders glyphs before you ever paste, so the input arrives messy through no fault of the recovery. Clean the obvious broken spacing in the input box first, then recover; fix the source spacing rather than the Nepali output.

Matras or half-letters sit wrong

Preeti encodes इ, ई, र् and stacked conjuncts across 2 to 3 key positions, and a damaged source loses that order. Recover, then read those specific letters against the original line by line before you trust a name or legal term.

You need the result for a website or app

Preeti is invisible to browsers, search, and most phones; only Unicode is portable. Recover to Unicode once and reuse it anywhere, this is exactly the job Unicode was built for, so the same text drops into any CMS or social post. One trip through a preeti to unicode converter is usually all an archive needs before it stops depending on a single installed font to stay readable.

You are not sure the file is even Preeti

Kantipur, PCS Nepali, and Sagarmatha look almost identical on screen but share Preeti's ASCII layout. Paste it anyway; these related families recover the same way, and a clean Nepali result confirms the family. Because the byte map is shared, the same preeti to unicode converter handles Kantipur or PCS Nepali text without any change of setting.

data versus display

Why a preeti to unicode pass is the only real fix

One idea explains every symptom above, and it is also why a font swap never works where recovery does.

A Preeti file does not store Nepali letters at all. It stores English keystroke positions, the same 26 keys your fingers pressed, and the Preeti font paints a Nepali shape over each. Data and display are two separate things, glued by that one font.

The glue holds on the office machine where Preeti is installed. The instant the file moves, by email, to a phone, into a browser, onto a government portal, the font is gone and the raw keystrokes show through. That is when you see g]kfn instead of नेपाल. Nothing is corrupted; the device just reads the bytes literally. This is why changing the font in Word never fixes the file: it repaints one screen while the stored data stays in the old keystroke form.

What Unicode stores instead

Unicode stores the actual character, राष्ट्र, as code points in the Devanagari block U+0900 to U+097F, 128 positions defined by the Unicode Standard since version 1.0 in 1991. So the letter is the letter on every device. To convert preeti to unicode is to rewrite that data from keystroke positions into true Devanagari, which is why the result reads correctly on the roughly 90 percent of phones with no Nepali font, in search, and in any Unicode font. Recovery fixes the data; a font change only fixed one screen.

Where a recovered file still needs your eyes

Preeti packs Nepali Devanagari onto about 90 ASCII positions, fewer than the 128 Unicode provides, so a few letters carry more ambiguity. Stacked conjuncts and the half-forms Preeti splits across 2 or 3 key positions are where a damaged source can drift. For a chat message this never matters; for a citizenship record, a court notice, or a published name it does, so recover those in blocks of 200 to 300 words and read the conjuncts and matras against the original first.

Preeti to unicode converter example: legacy Preeti Nepali shown as scrambled Latin letters on the left, recovered into readable Nepali Unicode on the right.
The left side is what every modern device shows for a Preeti file. The right is the same content after a preeti to unicode pass.

The preeti to unicode recovery, step by step

  1. Paste the broken-looking Nepali into the input box above, or type it on the Preeti keyboard if you only have a printout.
  2. The readable Nepali Unicode appears beside it as you go. There is no convert button to press and no length limit.
  3. Copy the Unicode out, or download it as a Word or text file for an archive.
  4. Use it anywhere, a site, an email, a form, a phone message, or a Word document in any Unicode font. No Preeti install needed.
  5. For anything official, read names, dates, numbers, and matras against the original before you submit or publish.

What this is checked against

The public standards behind Nepali Devanagari on the modern web. Unicode defines the 128 code points of the U+0900 block; Nepali is written in Devanagari, the same script as Hindi; Preeti is one legacy font layered on the ASCII keystroke positions. Every recovery a preeti to unicode converter performs is measured against these published charts, so a restored archive maps onto real Devanagari rather than a guessed approximation.

About this preeti to unicode converter

A recovery desk for old Preeti Nepali files: turn them into Unicode that works on websites, search, phones, and modern documents.

Main converter hub

Who reaches for it

Clerks, students, teachers, and editors whose old Nepali file has stopped displaying on a new phone or laptop. Preeti was the standard for over 20 years, so much of Nepal's written record still sits in it, and this preeti to unicode converter is the step that brings each file back into a readable, shareable form.

Answers people land here for

  • Why does my old Nepali show as English letters?
  • How do I get a Preeti file onto a website or phone?
  • Why a font change in Word never really fixes it
  • What to double-check before publishing recovered text

If this was not the direction you needed

This page recovers Preeti into Unicode. If your text is already readable Nepali and you need it back in a legacy layout instead, the reverse tool is below.

Unicode to Preeti Converter The opposite job: take readable Nepali Unicode and turn it back into Preeti legacy output for Word, DTP, and older Nepali documents.

Pick the right tool for your file

Recovering an old Preeti file? The symptom cards above are the right place. When the source is a scrambled legacy document, a preeti to unicode converter is the recovery direction you want, and the reverse tool only makes sense once your Nepali is already clean Unicode. Already have clean Unicode Nepali and need legacy output, or working with Hindi Kruti Dev instead? These two are the quick jumps.

Recovery questions, answered

The questions Nepali users ask most when an old Preeti file stops working, answered plainly.

Why does my old Nepali text show as English letters?

Because a Preeti file stores English keystroke positions, not real Devanagari, and the Preeti font is what used to paint Nepali over them. On any device without that font, the raw keystrokes show through as scrambled Latin such as g]kfn instead of नेपाल. The bytes are correct for Preeti but meaningless to everything else. Recovering the file to Unicode rewrites those positions into true Nepali characters, which then display on every phone, browser, and app with nothing to install. This is also why simply changing the font in Word never really fixes it: that only repaints the screen while the stored data stays in the old keystroke form.

Does it work from text I copied out of a PDF?

Yes, with one caution. Paste the copied Preeti text and the readable Nepali appears as usual. The wrinkle is that copying from a PDF often adds stray line breaks and shuffles glyphs before you ever paste, so the input can arrive messy through no fault of the recovery. Tidy the obvious broken spacing in the input box first, then recover. If a line still reads oddly afterwards, repair it at the source and paste again rather than hand-editing the Nepali, since the spacing problem came in with the PDF copy, not the recovery itself. For scanned documents, check names and dates against the original page.

Will the recovered text appear in Google search?

Yes. Unicode Nepali is fully indexable, so once you recover old Preeti content and publish it as Unicode, search engines read, index, and rank it like any modern page. Preeti itself is effectively invisible to search, because crawlers see only the Latin keystroke positions, not real Nepali, so they find nothing meaningful. This is exactly why recovering archives, articles, and records to Unicode is what finally makes decades of Nepali writing discoverable online. The same recovered text is also copyable and works with screen readers, which helps accessibility and lets the content be reused across other sites and apps.

Which Nepali legacy fonts can it read?

Preeti is the common one, and the tool also reads the related Nepali legacy families built on the same ASCII keystroke layout, such as Kantipur, PCS Nepali, and Sagarmatha. Because they share that layout, text from them usually recovers to clean Unicode the same way Preeti does. Paste it and the Devanagari appears, ready for web, mobile, and search. If a passage still looks wrong, the source is probably on a genuinely different mapping, so check the original file or ask whoever made it which exact legacy Nepali font was used, then recover with that confirmed.

Only part of my document turned into Nepali. Is that a bug?

No, that is correct behaviour for a mixed file. Names, addresses, dates, and figures were typed as ordinary characters and were never Preeti, so they pass straight through unchanged while the Nepali passages recover. The fix is simply to recover the Nepali parts, leave the English and the numbers as they are, and rejoin everything. Devanagari and Western digits both come across the way they should. If something you expected to be Nepali stayed in English, that section may not have been Preeti to begin with, so confirm the source font for just that part.

It is a court notice. How careful do I need to be?

For anything binding, treat the recovery as a draft to verify, not a finished file. Preeti splits half-letters and stacked conjuncts across several key positions, so those, along with matras like इ, ई, उ, ऊ, and र्, are where a damaged or oddly typed source can drift. Recover the document in short blocks, then read names, legal terms, dates, and numbers against the original Preeti, letter by letter. Keep the original until you have confirmed the Unicode. For affidavits, citizenship paperwork, and certificates, that line-by-line check is the difference between a usable record and a wrong name.

Does it run on a phone, and is anything I paste saved?

Yes to the phone, and nothing you paste is saved or shared. The recovery runs in any phone browser, and the Unicode output is exactly what mobile, WhatsApp, email, and websites expect, so an old Nepali file becomes shareable in seconds. Preeti cannot display on most phones because the legacy font is not installed, but its recovered Unicode reads perfectly on Android, iOS, and every messaging app. There is no sign-up and no limit, so even private letters, records, and official paperwork stay confidential while you recover them. Just paste, copy the Nepali result, and use it normally.

I need it back in Word. Which font do I pick after recovery?

Once you have recovered the text to Unicode, you can paste it straight into a modern Word document and pick any Unicode Devanagari font, such as Mangal, Kalimati, Noto Sans Devanagari, or Preeti Unicode, and the Nepali will read correctly. You do not pick legacy Preeti; that font would scramble the new Unicode, because the data is now real Devanagari rather than keystroke positions. If you instead need the file to go back into the old Preeti layout for a DTP workflow, that is the opposite job, so use the Unicode to Preeti page rather than this one.