At a small cyber near Babarmahal, a man walks in with a pen drive and a slightly worried face. He has a 42-page land agreement typed years ago in Preeti. The pages look perfect on the old computer at home. But when he opens the file on his phone, the Nepali turns into strange Roman letters and symbols.
The shopkeeper tries the usual trick. “Preeti font install garna parcha,” he says. It works on one machine, then breaks again in email, WhatsApp and Google Docs. The man is frustrated because the file has tables, signatures, witness names and land measurements. He does not want to retype the whole thing.
This is a common Nepali document problem in 2026. Old Word files from government offices, schools, law firms, newspaper archives, ward offices, land brokers and local NGOs are still trapped in Preeti. The text looks Nepali only when the Preeti font is installed. Under the surface, the computer sees Roman characters, not real Devanagari Unicode.
The good news: you can convert a .docx file from Preeti to Unicode without losing formatting. The Merokalam Preeti to Unicode Converter lets you import DOC, DOCX and TXT files, convert Preeti text in the browser, and export Word or PDF while keeping paragraphs, alignments, tables, bold, italic and font sizes in place. The conversion runs locally in your browser, so your file is not uploaded to a server.
This guide shows the exact workflow. It also explains why formatting breaks, how to avoid the common mistakes, and what to check before submitting a converted file to a government portal, newspaper CMS, school assignment system or legal office.
First, What Is the Real Problem with Preeti?
Preeti is not bad. It helped Nepal type Nepali long before Unicode became normal. Many typing institutes in Putalisadak, Bagbazar, Narayangarh, Butwal and Biratnagar trained thousands of people on Preeti. Government notices, court documents, school question papers and newspaper layouts used it for years.
The problem is technical. Preeti is a legacy font. It uses English character positions to draw Nepali glyphs. For example, your document may show “नेपाल” visually, but the actual stored text is not Unicode Devanagari. When the font is missing, the illusion disappears.
Unicode works differently. Unicode stores the real Devanagari character. That means the word नेपाली stays नेपाली on Android, iPhone, Windows, Mac, Google Docs, email, social media, websites and PDFs.
| Feature | Preeti Font | Nepali Unicode |
|---|---|---|
| How text is stored | Roman key positions styled by Preeti font | Real Devanagari Unicode characters |
| Works on mobile | Usually breaks unless font support exists | Works on Android and iPhone by default |
| Google indexing | Search engines cannot properly read it | Searchable and SEO-friendly |
| Copy paste | Often becomes symbols or Roman fragments | Stays readable almost everywhere |
| Long-term archive | Depends on old font files | Future-safe and platform independent |
| Best use in 2026 | Only for opening old documents | All new digital work, websites, forms and submissions |
g]kfnL efiff, it is probably Preeti or another legacy font. If it remains नेपाली भाषा, it is already Unicode.Why .docx Conversion Is Harder Than Plain Text
Plain text conversion is simple. You paste Preeti into the left box and copy Unicode from the right box. But a .docx file is not just text. It contains paragraphs, styles, table cells, lists, headers, footers, page breaks, bold words, italic phrases, colours and alignment settings.
When people convert by copy and paste only, Word formatting can collapse. A three-column table may turn into plain lines. Numbered lists may break. Headings may lose font size. Signature blocks may move.
For a poem, that might be annoying. For a legal deed, tender document, newspaper layout or school report, it can be a serious problem.
The Correct Workflow: Keep Formatting While Moving to Unicode
The safest workflow is to preserve the document structure first and convert the text inside it. Merokalam’s converter is built for this. It can import .docx files, convert Preeti text, and export Word or PDF while keeping original layout structure intact.
Which Export Format Should You Choose?
Many users get confused at the export step. The right format depends on what happens after conversion. A land office draft, school question paper and blog post do not need the same output.
| Need | Best Export | Why | Watch Out |
|---|---|---|---|
| Editable Word file | Word .docx | Keeps paragraphs, tables and alignment while allowing edits | Use a Unicode font like Nirmala UI, Kalimati or Mangal after export |
| Final document to send | Looks the same on phones and computers | Proofread before export because PDF is harder to edit | |
| Website or blog post | TXT or copy Unicode | Clean text for CMS, SEO and social sharing | You may need to recreate headings and tables in your editor |
| Government portal field | Copy Unicode text | Direct paste into forms without font dependency | Paste plain text if the portal has formatting issues |
| Archive conversion | Word PDF | One editable copy and one locked viewing copy | Keep original Preeti file as historical backup |
Formatting Preservation: What Is Kept and What Needs Checking?
When imported .docx files are exported as Word or PDF, the converter is designed to keep the document structure. That includes paragraphs, alignment, tables, bold, italic and font sizes. Still, some documents have messy formatting from years of edits, copy-paste and printer shop fixes.
Common Preeti DOCX Problems and Fixes
Most conversion issues come from the source file, not the converter. Old documents often have mixed fonts, broken tabs, manual spacing and copied symbols. Use this table when something looks wrong.
| Problem | Likely Cause | Quick Fix | Best Practice |
|---|---|---|---|
| Some words remain broken | Document uses mixed fonts like Preeti, Kantipur and Sagarmatha | Select the broken section and convert separately if needed | Check font names in Word before conversion |
| Table columns shift | Original table uses tabs or spaces instead of real table cells | Convert text, then rebuild table in Word | Use actual Word tables for official documents |
| Heading looks too large or too small | Font size inherited from old Preeti styling | Select heading and apply a Unicode font and size | Use Word styles after conversion |
| Matras look odd in a few words | Non-standard typing shortcut or old keyboard habit | Proofread and manually correct those words | Check names, legal terms and uncommon conjuncts carefully |
| PDF output cuts page edge | Original margins were too narrow | Set margins to Normal in Word before PDF export | Use A4 size for government and school documents |
| Phone still shows boxes | Viewer app or font issue | Open in Google Docs or Word mobile, use Nirmala UI or Kalimati | Export PDF for final sharing |
Real Scenario 1: Converting a Land Agreement
Let’s return to the man at Babarmahal cyber. His land agreement was in a Word file with two main tables: buyer/seller details and land area. The headings were bold. The land measurements were written in ropani, aana and paisa. A normal copy-paste conversion would turn the table into messy lines.
The better workflow was simple. He first duplicated the file. Then he uploaded the .docx to the Merokalam converter. After conversion, he exported a new Word file. The table cells remained in place. Then he checked every measurement using the land measurement tool because one old line used “3 aana 2 paisa” while another used square feet.
| Item to Check | Why It Matters | Tool or Method |
|---|---|---|
| Kitta number | A single digit error can cause legal confusion | Manual proofread against Lalpurja |
| Land area | Old documents mix ropani and sq ft | Land Measurement Converter |
| Names | Matra mistakes change names | Compare with citizenship documents |
| Amounts | Loan and sale values must match bank papers | Manual cross-check |
| Signatures and witness lines | Layout must remain printable | Export Word, inspect print preview |
Real Scenario 2: A School Question Paper
A teacher in Pokhara had a class 10 Nepali question paper typed in Preeti. The file included multiple choice questions, long-answer sections and a marks table. When she pasted it into Google Docs, the Nepali broke and the numbering became unstable.
She used DOCX import instead of copy paste. After conversion, she exported Word and changed the font to Nirmala UI. The numbering stayed mostly intact. She only needed to check question numbers and section headings. The final PDF was shared in the school Viber group and opened properly on parents’ phones.
Real Scenario 3: A Blogger Moving Old Articles to WordPress
A Nepali blogger in Chitwan had 150 old articles typed in Preeti. His goal was not to preserve Word page layout. He wanted Google to read the content. For him, the best workflow was different.
He imported each .docx file, converted it, then exported plain text or copied the Unicode output into WordPress. After that, he rebuilt headings, images and links inside the CMS. This made the posts searchable and mobile-friendly.
Before and After: What Good Conversion Looks Like
Here is a simplified example of what happens during conversion.
g]kfnL efiffdf k|:t't k|ltj]bg
After, Unicode output:
नेपाली भाषामा प्रस्तुत प्रतिवेदन
The visible improvement is obvious, but the real benefit is deeper. The Unicode output can be searched, copied, indexed, read by screen readers, shared on WhatsApp, pasted into Google Docs and archived safely.
Which Nepali Fonts Should You Use After Conversion?
After conversion, your text is Unicode. That means you no longer need the Preeti font. In Word, choose a Devanagari-compatible Unicode font. These fonts work better for modern files and PDF export.
| Font | Best Use | Notes |
|---|---|---|
| Nirmala UI | Modern Word documents and office files | Common on Windows, clean rendering |
| Kalimati | Government-style Nepali documents | Popular in Nepal, familiar look |
| Mangal | General Devanagari documents | Good compatibility, slightly traditional |
| Noto Sans Devanagari | Websites and digital publishing | Excellent readability on screens |
| Noto Serif Devanagari | Books and formal PDFs | Traditional print-like appearance |
For official submission, avoid decorative fonts. Use readable Unicode fonts and keep font size between 11 and 14 depending on the document type. If you export PDF, check the file on at least one phone before sending.
Manual Paste vs DOCX Import: Which Should You Use?
Both methods are useful. The right one depends on whether layout matters.
• You are preparing text for Facebook, email or CMS
• Formatting is not important
• You want quick copy and paste
• You are checking if a file is Preeti or Unicode
• The file has headings and page layout
• You need Word or PDF export
• It is a legal, school, office or publication file
• You do not want to rebuild formatting manually
Mobile Workflow: Convert a Word File from Your Phone
Many Nepali users do not sit with a laptop. They receive old documents in Viber, Messenger, Gmail or WhatsApp and open them on Android phones. The mobile workflow is slightly different, but it works.
- Download the .docx file to your phone.
- Open the Merokalam Preeti to Unicode Converter in Chrome.
- Tap Import Doc.
- Choose the file from Downloads, Drive or WhatsApp Documents.
- Wait for conversion to finish in the browser.
- Review the output on screen.
- Export Word or PDF.
- Share the new Unicode file back through WhatsApp, Gmail or Drive.
Batch Conversion for Offices and Publishers
What if you have 100 files? A municipality office may have old notices. A publisher may have manuscripts from 2005. A law firm may have deed templates in Preeti. Batch conversion needs a clean process.
Do not dump everything into one folder and convert randomly. Create a small workflow.
| Folder | Purpose | Example File Name |
|---|---|---|
| 01 Original Preeti | Keep untouched source files | notice-2077-original.docx |
| 02 Converted Unicode Word | Editable Unicode output | notice-2077-unicode.docx |
| 03 Final PDF | Final shareable copies | notice-2077-final.pdf |
| 04 Proofread Notes | Track corrections and errors | notice-2077-notes.txt |
| 05 Published | Files uploaded to website or archive | notice-2077-web.txt |
Convert five files first as a test. If results look good, continue in batches of 10 or 20. For books, convert chapter by chapter. This makes proofing easier and prevents one messy file from slowing the entire project.
Proofreading Checklist After Conversion
A converter saves time, but the human eye still matters. Here is a practical checklist used by editors and office staff.
- Check all personal names against citizenship, passport or office records.
- Check all dates, amounts, invoice numbers, kitta numbers and phone numbers.
- Check land measurements and convert units if needed.
- Check table headers and merged cells.
- Check half letters and conjuncts such as क्ष, त्र, ज्ञ and श्र.
- Check punctuation, especially danda marks and quotation marks.
- Open the final file on one phone and one computer before sharing.
Website Publishing: Why Unicode Is Non-Negotiable
If you run a Nepali blog, news portal, NGO site or local business website, publishing Preeti text is like hanging a beautiful signboard inside a locked room. It may look correct to you, but search engines cannot reliably understand it.
Unicode text can be indexed, searched and shared. That means Google can understand your Nepali title, meta description and article body. Users can search for a phrase from your article. Social media previews work better. Screen readers and translation tools have a better chance of processing the text.
| Website Task | Preeti Result | Unicode Result |
|---|---|---|
| Google indexing | Weak or broken | Readable and indexable |
| Search inside website | Often fails | Works normally |
| Social sharing | May show garbage text | Displays Nepali correctly |
| Mobile readability | Depends on legacy font | Works by default |
| Copy quotes | Breaks for readers | Readers can copy clean text |
Security: What Happens to Your File?
Many users ask a fair question: “If I upload a Word file, will someone read it?” In Merokalam’s converter, conversion runs locally in your browser. That means the file is processed on your device, not sent to a server database. This matters for legal drafts, client records, exam papers and internal office notices.
Still, follow smart file habits. Do not convert confidential documents on a public cyber computer unless necessary. If you do, delete downloaded files and clear the browser download history. Use your own laptop or phone for sensitive documents.
• Use your own device for legal, bank or personal documents.
• Keep the original Preeti file as backup.
• Export both Word and PDF for important documents.
• Rename files clearly after conversion.
• Delete temporary copies from public computers.
File Naming System That Saves Future Headaches
Most Nepali offices lose time not because conversion is hard, but because files are named badly. You will see names like final.docx, new final.docx, final final 2.docx and ram sir corrected.docx. After conversion, use a clean naming system.
| Bad File Name | Better File Name | Why Better |
|---|---|---|
| final.docx | ward-notice-2085-unicode-v1.docx | Shows topic, year, format and version |
| agreement new.docx | land-agreement-bhaktapur-kitta-1234-unicode.docx | Easy to search later |
| paper.docx | class-10-nepali-question-paper-2085-final.pdf | Clear for students and admin staff |
| book converted.docx | novel-chapter-03-unicode-proofread.docx | Good for publishing workflow |
When Not to Use Automatic Conversion Alone
Automatic conversion is excellent for normal typed text, but some documents need extra care.
- Scanned PDFs: If the document is an image scan, a Preeti converter cannot read it directly. You need OCR or manual typing first.
- Mixed language forms: If English, Nepali and symbols are heavily mixed, proofread more carefully.
- Math and science papers: Formulas, symbols and diagrams may require manual adjustment.
- Highly designed brochures: Text boxes, columns and artistic layouts may need design software cleanup.
- Non-Preeti legacy fonts: Kantipur, Sagarmatha and Himali may not map exactly like Preeti.
Quick Decision Tree
Use this decision tree before starting.
| Your Situation | Recommended Action |
|---|---|
| Need to convert a full Word file with tables | Use DOCX import and export Word |
| Need a final signed document for sharing | Use DOCX import, proofread, export PDF |
| Need text for website or social media | Paste or import, copy Unicode or export TXT |
| File is a scanned image | Use OCR or manual typing first, then convert if needed |
| File has mixed fonts | Convert section by section and proofread |
| Working on land papers | Convert DOCX, then verify units using Land Measurement Converter |
Frequently Asked Questions
Can I convert a .docx file directly?
Yes. Open the Merokalam Preeti to Unicode Converter and click Import Doc. The tool supports Word .docx import and can export Word or PDF while keeping structure such as paragraphs, tables, bold text and alignment.
Will tables stay intact?
For real Word tables, yes in most cases. If the original “table” was made with spaces and tabs, you may need to rebuild it after conversion.
Does the file upload to Merokalam servers?
No. The converter is designed for client-side processing. That means the file is handled inside your browser and your document is not stored in a database.
Can I convert old .doc files?
The tool supports DOC import, but very old files may behave better if you first open them in Word or LibreOffice and save them as .docx. Then upload the .docx.
Why does a word still look wrong after conversion?
The source may contain non-standard typing, a different legacy font, mixed symbols or a manual shortcut. Correct the word manually and check similar words in the document.
Which font should I use after converting?
Use Nirmala UI, Kalimati, Mangal, Noto Sans Devanagari or another Unicode Devanagari font. Do not keep using Preeti after conversion.
Can I use this for government forms?
Yes, Unicode is the right choice for digital forms and portals. For official submissions, always proofread and export PDF if the layout must not change.
Can I convert Unicode back to Preeti?
This guide is about Preeti to Unicode. For reverse conversion, use Merokalam’s Unicode to Preeti Converter if your printer or old workflow still requires Preeti.
Final Checklist Before You Send the Converted File
1. Original file backed up
2. Correct file imported into the converter
3. Unicode output reviewed
4. Names and numbers checked
5. Tables checked on desktop and phone
6. Font changed to Unicode-compatible font
7. Word copy saved for editing
8. PDF copy exported for sharing
9. and units verified if the document is property-related
Converting a Preeti .docx file to Unicode is not just a technical cleanup. It is a rescue mission for old Nepali documents. Your Word file becomes readable on phones, searchable on Google, safe for archiving and easier to share with people who do not have Preeti installed.
The main lesson is simple: if layout matters, do not rely on copy and paste alone. Use DOCX import. Export Word if you need to edit. Export PDF if the file is final. Proofread important fields. For land papers, use the land measurement tool to verify units. For web content, use clean Unicode text so Google and readers can actually understand it.
That man at the Babarmahal cyber left with two files: one editable Unicode Word document and one PDF. His phone displayed Nepali correctly. The tables stayed in place. The land measurements were checked. And the old Preeti document finally became future-ready.