Unicode to Krutidev only works if you name the right font
An old print shop or a legacy Hindi template still wants Kruti Dev, not Unicode.
You paste Unicode Hindi and the converter maps it to Kruti Dev codes. Apply the Kruti Dev font to see the words.
If the Hindi comes out scrambled
If you change the font back to Mangal without converting, the text will look like nonsense. Keep the Unicode original.
The other Hindi font tools are on the font tools page.
Why Unicode to Krutidev is its own job
Unicode to Krutidev sits on this site because Unicode and Krutidev are not interchangeable, even when they look similar in a file list. An old print shop or a legacy Hindi template still wants Kruti Dev, not Unicode. Websites, phones, and current Word need Unicode, not a legacy font encoding. Old Indian office documents were typed in Kruti Dev and fall apart in Gmail or on a phone.
You paste Unicode Hindi and the converter maps it to Kruti Dev codes. Apply the Kruti Dev font to see the words.
The Unicode file you already have
Unicode Hindi is the text you get from Google and modern Windows. The letters are real Hindi characters. Running Unicode through a Kruti Dev or Devlys converter scrambles real Hindi.
Keep a Unicode copy. Legacy-font text is not safe to paste on the web.
What a Krutidev result is for
The download has to be Krutidev, because that is the format the next step named. Old Indian office documents were typed in Kruti Dev and fall apart in Gmail or on a phone. Mapping Kruti Dev to Unicode makes the words survive a font change.
Work on a copy. Compare a line you can read before you convert the file.
How to tell that Unicode to Krutidev worked
Unicode to Krutidev is worth using only when Krutidev is what the next step actually named. An old print shop or a legacy Hindi template still wants Kruti Dev, not Unicode. What you get from Unicode to Krutidev: You paste Unicode Hindi and the converter maps it to Kruti Dev codes. Apply the Kruti Dev font to see the words. Before you trust it: If you change the font back to Mangal without converting, the text will look like nonsense. Keep the Unicode original. The text stays in the browser. Try one line you can check before a whole document. Do not paste passwords. A second pass rarely helps. If the first Krutidev file is rejected, read the error from the program that rejected it. Another conversion of a bad result usually makes the file worse, not more compatible. When you are done, you should still have the Unicode original and one Krutidev download that you have opened. If those two are the same kind of failure, this was the wrong tool and the page above is the place that says so. Legacy Hindi fonts are not Unicode. Unicode to Krutidev only works if you name the font the text was actually typed in. The wrong mapping produces words that look like Hindi and say something else. Convert one sentence you can read, compare it, then do the rest. Keep a copy of the original document.
Here is the decision for Unicode to Krutidev. You start with Unicode and you stop when a real program accepts Krutidev. Once text is Unicode, any normal Hindi font can display it, including Mangal. The source must actually be Kruti Dev. The wrong mapping produces the wrong words. If those two sentences describe a tradeoff you do not want, do not convert. Renaming the extension by hand will not do this job. Running the tool twice on its own output will not do it either.
If you change the font back to Mangal without converting, the text will look like nonsense. Keep the Unicode original.
A related step, if you still need one, is Krutidev to Unicode.
Other jobs start from the homepage, where each tool is named for the conversion it actually does.