How to Type Nepali in Google Docs, Sheets & Forms

Rakshya runs a small health programme out of a rented room above a pharmacy in Damauli. Her job that week was simple on paper: send parents a short Nepali survey about their children's vaccination dates, using Google Forms. Keep the responses organised in a Sheet. Write a two-page summary in a Doc for her supervisor in Kathmandu.

She opened Google Forms and typed the first question in English, then stopped. Half the parents she was writing for could not read English comfortably. The form needed to be in Nepali. She had typed Nepali before, on Facebook, on WhatsApp, using some phonetic trick she'd half-forgotten. But this was Google Forms, not Messenger, and nothing on the screen looked familiar.

She tried the obvious thing first, right-clicking, checking the toolbar, looking for a language button. Nothing. She switched to a blank Google Doc to test the same idea, and there it was, a small "अ" icon appeared in the toolbar after she changed something in a menu. Sheets behaved differently again. Forms, it turned out, behaved like none of them.

If that sounds familiar, this guide is for you. Google does support Nepali typing across Docs, Sheets and Slides, officially, through a feature most people never notice called Input Tools. Forms is the odd one out, and this guide explains exactly why, and what to do about it.

What's Actually Built Into Each App

Before touching any menu, it helps to see the whole picture in one place. Google did not build Nepali support the same way into every product, and that is the entire source of the confusion Rakshya ran into.

The pattern is worth remembering: any Google product that opens inside its own editing surface, Docs, Sheets, Slides, tends to have Input Tools built directly into that editor. Anything that behaves more like a web form, Forms, Gmail's compose box, comment fields, does not. For those, you either add a browser-level extension or you type somewhere else and paste the result in.

How to Type Nepali in Google Docs

This is the cleanest of the three, and once you've done it here, Slides works identically.

How to Type Nepali in Google Sheets

Sheets has the same underlying Input Tools feature as Docs, but Google tucked the setting somewhere different, which is exactly where Rakshya got stuck for a good ten minutes.

For a roster or data-entry sheet where you are pasting the same handful of Nepali labels into many rows, typing them once on Merokalam and pasting is often faster than toggling Input Tools on and off for every cell, especially if most of your sheet stays in English and only a few columns need Nepali.

How to Type Nepali in Google Forms

This is where Rakshya's afternoon actually stalled, and it is not her fault. Forms genuinely does not have the File, Language, Input Tools path that Docs, Sheets and Slides share. It is built on a different, simpler editing framework, and Google never extended the same language menu into it.

That leaves two real options.

Rakshya, in the end, used option B. Her survey had eleven questions. She typed all eleven, plus the multiple-choice answers, in one sitting on Merokalam, then spent five minutes pasting them into the Form fields one at a time. No extension to explain to her one shared office laptop, no setting that a colleague might accidentally change later.

Why Forms Is Built Differently

It is worth understanding why Forms behaves so differently, because it explains a lot of the confusion people run into searching for a fix that does not exist. Docs, Sheets and Slides are full document editors. Each one carries its own rich text engine, and Google attached the Input Tools language layer directly to that engine years ago, the same underlying system that also powers Google Translate's typing box and inputtools.google.com.

Forms, by contrast, was built as a lighter, form-building interface sitting on top of simple web input fields, closer in spirit to a website's contact form than to a document. Google never wired the Input Tools engine into those individual question and answer fields. That is not a bug you can toggle around in a hidden settings menu, it is a structural gap between two different products, and it explains why so many people search for "Nepali typing Google Forms" specifically and land on generic Docs instructions that simply do not apply.

Nepali in Google Slides

Slides shares the exact same Input Tools system as Docs, which is easy to miss because presentations feel like a different kind of writing. Open your presentation, click File, then Language, choose Nepali, and the same toolbar icon and Ctrl+Alt+Shift+K shortcut appear inside text boxes on your slides.

The one habit worth building for Slides specifically is checking your font after typing. Devanagari text can render at inconsistent sizes next to English text in the same text box, especially in slide titles, so a quick visual check before presenting saves you from Nepali text that looks cramped or oversized on the projector.

Collaborating on Nepali Documents

Rakshya was not the only person touching these files. Her supervisor needed to open the Doc, a colleague needed to edit the Sheet, and parents needed to read the Form. A few things are worth knowing before you share.

Anyone opening a document you've typed in Nepali sees it correctly without doing anything on their end, because Unicode is universal. They do not need Nepali set as their own language, they do not need Input Tools enabled, they just need a normal, modern browser or the Google app. This is the single biggest advantage Unicode has over the old Preeti-font era, when a document could look perfect on your computer and completely broken on someone else's.

Spell-check may underline Nepali words in red even when they are spelled correctly, since Google's dictionary support for Nepali is thinner than for English. Ignore it, or right-click and choose "Ignore" for the session. Comments and suggested edits work normally in Nepali text, the collaboration layer does not care what script the words are in.

If you're working with a diaspora team spread across Kathmandu, Sydney and Dallas, remind everyone that the Input Tools toggle is per-document, not a permanent account setting. A colleague opening the same Doc on their own laptop needs to switch on Input Tools themselves the first time they want to type Nepali into it, even though they can already read what you wrote without changing anything.

Comparing the Effort: Steps Per App

Numbers make this easier to plan around. Here is roughly how many steps each method takes the first time you set it up, versus every time after that.

A Quick Phonetic Reference

Whichever method you use, phonetic Nepali typing follows the same basic logic: spell the word the way it sounds in English, and let the software convert it. A few examples make the pattern click faster than any explanation.

For a much deeper look at phonetic versus Preeti-layout typing and which one suits Lok Sewa exam preparation, see Merokalam's Nepali typing methods comparison. This guide sticks to the Google-specific mechanics.

Numbers, Dates and Punctuation

Nepali documents rarely stay purely alphabetic for long, dates, ages, phone numbers and prices show up constantly, and this is where people using Input Tools for the first time often get tripped up. Google's phonetic Input Tools generally leave plain digits alone, typing 2083 stays as 2083 rather than converting to Devanagari numerals, which is usually what you want for anything that needs to sort or calculate correctly in a Sheet.

If you specifically need Devanagari numerals, ० १ २ ३ ४ ५ ६ ७ ८ ९, for a formal document, a certificate, or a printed notice, typing them phonetically is inconsistent across tools. The more reliable route is copying them once from a reference source, or using the Merokalam typing tool's output directly where numerals typed inside Nepali sentences convert correctly, then reusing that snippet wherever you need it again.

Punctuation mostly behaves as expected, standard commas and periods carry over from English typing without special handling, though formal Nepali writing sometimes uses the purna viram (।) instead of a period. Both Google's Input Tools and Merokalam's tool support typing this correctly as part of normal Nepali sentence flow.

Keyboard Shortcuts Worth Remembering

None of these shortcuts need memorising immediately. Most people land on one habit, native toggling in the app they use daily, paste-and-go for everything else, and stop thinking about the mechanics within a week.

Fixing the Most Common Problems

A surprising share of "Nepali typing isn't working" reports trace back to one of a small handful of causes, almost never something broken on your computer specifically. Working through the table below in order usually finds the culprit within a minute.

Which Method Actually Fits Your Situation

How Rakshya Finished Her Week

The survey went out in Forms using the paste method. The roster stayed in Sheets, mostly English column headers with Nepali names typed through Sheets' own Input Tools, since she was going to be updating that sheet for months and it made sense to learn the toggle once. The final report to Kathmandu was written straight in Docs with Input Tools switched on for the Nepali quotes she'd collected from parents, and left in English for the rest.

Three documents, three different typing habits, and none of it needed installing anything on a laptop she shares with two other staff. That mix, native tools where you'll use them often, paste-and-go where you won't, is really the whole strategy this guide is trying to hand you.

Frequently Asked Questions

Final Verdict

Google really did build Nepali typing into Docs, Sheets and Slides, properly, officially, for free. Most people never find it because the setting hides one menu deeper than expected, and because Forms breaks the pattern entirely with no equivalent menu at all.

Learn the native toggle for whichever app you open most often. For everything else, especially Forms, especially on a shared computer, especially when you just need one clean paragraph, typing it once on Merokalam and pasting will always be faster than explaining a menu path to your future self.