Skip to content
Nepali tool

Unicode → Preeti

The reverse mapping, with the lossy cases documented rather than hidden.

Nothing you type is sent anywhere. This runs entirely in your browser — no upload, no server round-trip.

Real Unicode Devanagari, shown in Mukta.

Shown in the Preeti font. Pasted into a system without Preeti installed, it will look like Latin gibberish — that is expected.

Your text is saved to this browser only, so it's still here if you come back. Nothing is ever sent to a server.

How to use it

  1. 1

    Paste your Unicode text

    Paste normal Unicode Devanagari (Nepali) text into the left box.

  2. 2

    Read the Preeti result

    The right box shows the Preeti-encoded equivalent, for pasting into old Preeti-only documents or systems.

  3. 3

    Check the warning, if any

    If a character has no Preeti equivalent, it is listed so you know before you paste the result elsewhere.

Questions people ask

Why would I convert Unicode back to Preeti?

Mostly for compatibility with older systems, templates or print layouts still built around the Preeti font — some government forms, older DTP files and legacy software still expect Preeti-encoded text.

Is the result identical to what I would have typed originally?

Almost always visually, not always byte-for-byte. A few Preeti keys are alternate shortcuts that draw the same glyph, and some conjuncts have both a dedicated key and a two-key spelling. The output settles on one of them, and renders identically to the original — see the note above the result.

What does the warning about unmapped characters mean?

It lists any character in your input that has no Preeti equivalent at all — most often a Devanagari character outside what Preeti's font was designed to display. That character is left unchanged in the result rather than silently dropped.

Converting modern Nepali text back to Preeti

Most of the time, the traffic runs the other way — old Preeti content getting modernised into Unicode. But some workflows still need the reverse: a print layout built years ago around Preeti, a template that only accepts that encoding, or a legacy system that has not been upgraded. This tool handles that direction too.

It is worth understanding the shape of the problem before relying on it for anything exact: several distinct Preeti keystrokes can produce the visually identical Devanagari glyph, so going from Unicode back to Preeti cannot always recover the exact original keys — only a Preeti encoding that renders identically. For the overwhelming majority of everyday text this makes no visible difference at all; it shows up only where Preeti offers two ways to type the same conjunct, and the tool has to pick one.

When you'd use this

Preparing modern, correctly-typed Nepali content for a legacy system, print template or old CMS that still expects Preeti. Testing how existing Preeti-based tooling handles new content without retyping it by hand.

Limitations

This converter targets the Preeti font specifically. Other legacy Nepali fonts — PCS Nepali, Kantipur, Sagarmatha and others — use different character mappings and are not supported here.

Plan a meeting

No pitch. Bring the problem and we'll work out the shape of it.

I'm usually tied up Mon–Fri, 8am–5pm. Weekday evenings from 5pm, and any time at weekends.

Next good slots

How long do you need?
Offer a second time (optional)

Optional — only if you'd rather I called.

A couple of sentences is plenty.

Goes straight to my inbox. Never shared.