Subscript in Google Docs and Microsoft Word: The Complete Guide
Microsoft Word has a real subscript button. Google Docs has a keyboard shortcut. Both apps also accept Unicode subscript pasted from a generator, which is the only path that works for the letters that don’t have a proper subscript. This is the full reference for when to use which.
The general small-caps companion is the small caps in Google Docs guide, and the Unicode reference is the subscript letters list.
Microsoft Word: the proper built-in
Word exposes subscript as a character-formatting option. Selecting text and applying subscript changes the rendering, not the underlying character. The text remains a normal “H” or “2”; it is just drawn lower and smaller.
How to apply:
- Windows shortcut:
Ctrl + Shift + =(the=is the+key, unshifted) - macOS shortcut:
⌘ + Shift + = - Menu path: Home tab → Font group → Subscript button (x with a small 2 below it,
X₂)
How to clear: Apply the same shortcut or button to the same text. The format toggles off.
What it does well:
- It works for any letter or digit. There is no coverage gap.
- It renders with the document’s font, so the subscript matches the surrounding typography.
- It survives spellcheck and grammar check.
- It exports cleanly to PDF.
- It is accessible — screen readers announce subscript correctly.
What it does not do:
- It does not survive copy-paste into a plain-text field. If you copy
H₂Ofrom Word and paste it into Notepad, you getH2O. The format is lost. - It is document-bound. The subscript is part of the .docx file, not part of the character. It cannot be used in a bio, a chat, a comment, or anywhere outside a Word document.
Best for: documents that stay in Word. Reports, papers, theses, anything that is exported to PDF from Word.
Google Docs: the workaround, sort of
Google Docs has a subscript menu item under Format → Text → Subscript, and a keyboard shortcut (Ctrl + , on Windows, ⌘ + , on macOS). It applies a character-formatting subscript, the same way Word does.
How to apply:
- Menu path: Format → Text → Subscript
- Shortcut:
Ctrl + ,(Windows) /⌘ + ,(macOS) - Clear: Apply the same menu item or shortcut again
What it does well:
- It works for any character. No coverage gap.
- It renders with the document’s font.
- It survives spellcheck.
- It exports cleanly to PDF via the Google Docs export flow.
What it does not do:
- It does not survive copy-paste into a plain-text field, the same as Word. The format is document-bound.
- It is slightly less reliable in collaborative editing — two users with the subscript applied at once can sometimes fight over the format.
- The keyboard shortcut is easy to hit by accident if you are doing heavy formatting in Google Docs; the undo button is your friend.
Best for: documents that stay in Google Docs. Collaborative drafts, classroom assignments, internal reports.
The Unicode alternative — works in both, and survives the paste
The third path is to type (or paste) the actual Unicode subscript characters: ₀ ₁ ₂ ₐ ₑ ₕ ᵢ ⱼ ₖ ₗ ₘ ₙ ₒ ₚ ᵣ ₛ ₜ ᵤ ᵥ ₓ. The Subscript Generator gives you the full set; the Tiny Text Generator gives you subscript alongside small caps and superscript in one view.
How to apply:
- Generate the subscript text.
- Copy.
- Paste into the Google Doc or Word document.
- The characters appear as subscript, in the document’s font.
What it does well:
- It survives copy-paste out of the document, into a chat, a bio, a comment, an email.
- It renders identically on every modern device.
- The pasted text is searchable by its subscript form (and only its subscript form, which is the caveat).
What it does not do:
- It has a coverage gap. The subscript letters that do not exist in Unicode — b, d, f, g, q, y, z — cannot be rendered as true subscript via paste.
- It does not match the surrounding typography as cleanly as Word’s built-in, because the subscript characters are coming from a different code-point family than the document’s regular letters. The visual result is usually fine; a typographer would notice the stroke-weight mismatch.
- Spellcheck ignores it. The pasted word is not recognised as an English word.
Best for: documents that need subscript to survive copy-paste out of the document, or for the small subset of cases where you want subscript to look the same in Word, in chat, in a bio, and on a printed page.
When to use which
The decision is simple once you name what you are doing.
| If you are… | Use… |
|---|---|
| Writing a Word document that stays in Word | Word’s built-in subscript (Ctrl + Shift + =) |
| Writing a Google Doc that stays in Google Docs | Docs’ subscript menu (Format → Text → Subscript) |
| Writing a document that needs to be pasted into a chat, a bio, an email, a comment | Unicode subscript from the Subscript Generator |
| Writing a chemical formula in any of the above | Unicode subscript — the source text matters and the formula must be searchable elsewhere |
| Writing a mathematical sequence in any of the above | Unicode subscript — same reason |
| Typing subscript letters that don’t have Unicode coverage (b, d, f, g, q, y, z) | The built-in — Unicode cannot render these as true subscripts |
The rule of thumb: built-in for documents that stay in the document. Unicode for anything that has to travel.
The hybrid pattern
For long documents that mix chemical formulas and running prose — a chemistry textbook chapter, a recipe blog post in Google Docs — the practical approach is to use the built-in for the running prose (so it matches the document’s typography) and paste Unicode for any formula that needs to be quoted or shared elsewhere. The two renderings look almost identical to a casual reader; the difference is in what happens when the text is copied.
The honesty section
Built-in subscript and Unicode subscript look almost the same. The difference is in what the underlying text is. A Word subscript H₂O is the text “H2O” with subscript formatting applied. A Unicode subscript H₂O is the text “H” + U+2082 + “O”. The rendering is the same in Word. Outside Word, only the Unicode version survives.
Built-in subscript is more accessible. A screen reader will say “H two O” for both the built-in and the Unicode version (most readers are smart about the formula case). For non-formula uses, the built-in is more reliably announced as “subscript” by the reader; the Unicode version is often announced by character name (“subscript two”), which is louder and less natural.
Search behaves differently. A Word document containing built-in subscripts is searchable by the unformatted text (“H2O”). A document containing Unicode subscripts is searchable only by the subscript form. If you ever need to find “H2O” via Ctrl+F, the built-in wins. If you need to find it outside the document, the Unicode wins.
Quick recap
Word has a real subscript button (Ctrl + Shift + =); Google Docs has a menu item (Format → Text → Subscript). Both apply document-bound formatting that does not survive copy-paste out of the document. Unicode subscript from the Subscript Generator is the only option that survives the paste and works outside the document, at the cost of a coverage gap for the letters that do not have proper Unicode subscripts. Use built-in for documents that stay in the document; use Unicode for anything that has to travel.