Skip to converter
MyKrutiDev

Englishहिंदी

How to Convert a Whole Word File from Kruti Dev to Unicode

Copying a long document into a converter page by page loses its tables and formatting and takes an afternoon. You can convert the whole .docx at once instead, with the layout intact and without uploading it anywhere.

By MyKrutiDev teamUpdated

Open the tool: Kruti Dev to Unicode Converter

What you need

A Word file in .docx format (or a plain .txt) typed in Kruti Dev, up to 20 MB. You do not need Kruti Dev installed, and nothing is uploaded: the file is opened and converted by your browser.

  1. Open the Upload Word file tab on Kruti Dev to Unicode.
  2. Drop in the .docx (or .txt). It is read in your browser, not uploaded.
  3. Kruti Dev runs are converted. English, tables, images and formatting are kept.
  4. Download the converted copy and check names and figures against the original.
Converting a whole Word file: only the Kruti Dev text changes.

Step by step

  1. Open Kruti Dev to Unicode and choose the Upload Word file tab above the text boxes.
  2. Drag your .docx onto the box, or press Choose file.
  3. Choose the Hindi font the converted file should use.
  4. Press Download converted file. You get a new .docx and your original is not changed.

The summary tells you how many paragraphs and tables were converted. If part of the file was already Unicode, it says so and leaves that part as it is.

What is kept and what changes

  • Changes: text in Kruti Dev becomes Unicode Hindi, with the matras and reph put in Unicode order.
  • Kept: English text, numbers, tables, images, headers and footers, bold, italic, sizes, alignment and page layout.
  • Font: converted text gets the Unicode font you chose, so it shows correctly on any computer.

Old .doc files, PDFs and scans

  • .doc (Word 97-2003): open it in Word and use File → Save As → Word Document (.docx), then convert the .docx. The same goes for password-protected files: remove the password first.
  • PDF: text copied from a PDF typed in Kruti Dev is usually still Kruti Dev keys, so it can be pasted into the converter - but PDFs often break lines and spacing. If you have the original .docx, use that instead.
  • Scanned pages: a scan is a picture, not text. It needs Hindi OCR first. A converter cannot read it.

Check before you rely on it

Read the converted file against the original, and give names, figures and dates special attention. Two things are worth knowing. English detection is a best guess - Kruti Dev stores Hindi as English letters, so an unusual English name can be converted by mistake. And a file typed in another font (Chanakya, or a Kruti Dev variant other than 010) will convert with some letters wrong, so check the font name in Word before you start.

A five-minute check of the result

  1. Page count. The converted file should have about the same number of pages. A big difference usually means a font substitution, not lost text.
  2. First lines of each page. Read them against the original.
  3. Anything left unconverted. Kruti Dev text that was not converted still reads as English letters. Use Word's Find (Ctrl+F) for common Kruti Dev words such as dk, gS and vkSj: in a converted file they should not appear.
  4. Names, numbers and dates, one by one.

Converting many files

The converter takes one file at a time, and each takes a few seconds. For a folder of documents, keep the originals in one folder and save each converted copy into another with the same name, so nothing is overwritten and you can always go back. If a file is too large, split it into parts in Word and convert each part.

Going the other way

If an office template needs Kruti Dev, Unicode to Kruti Dev converts a Unicode .docx the same way and sets Kruti Dev 010 on every converted paragraph. And if you just need the text in Mangal, Kruti Dev to Mangal does the conversion for pasted text.