Small Caps vs. Superscript vs. Subscript, Compared

"Small text" usually means one of three genuinely different things, each with its own — very different — coverage gaps. None of the three is a complete alphabet.

Small caps: 25 of 26 letters

Small capitals (drawn from several older Unicode blocks — IPA Extensions, Phonetic Extensions, and Latin Extended-D) look like tiny uppercase letters at roughly lowercase height. Every letter has an assigned glyph except X, which has no small-capital character anywhere in Unicode — it's shown as an ordinary capital X instead. Small caps is case-insensitive by design: both "Text" and "TEXT" produce the same small-cap output, since the point is a uniform look, not case preservation — which is also why this style isn't auto-reversible to its original case.

Superscript: complete for lowercase and digits, sparse for uppercase

All 26 lowercase letters and all 10 digits have an assigned superscript glyph. Uppercase is a different story: only 13 of 26 letters do (C, F, Q, S, V, X, Y, Z and a few others have no assigned superscript glyph and stay as plain capitals). If your text is mostly lowercase, superscript will look complete; if it's mostly uppercase, expect visible gaps.

Subscript: no uppercase exists at all

Subscript is the most limited of the three: Unicode has never assigned any uppercase subscript letter, in any block. Only 16 of 26 lowercase letters have an assigned subscript glyph (missing: b, c, d, f, g, q, w, y, z, and a few others); all 10 digits are supported. This is why subscript is best suited to short lowercase text — chemical-formula-style notation, not full sentences.

Side-by-side

Every unsupported letter is preserved exactly as typed, never dropped or approximated with a lookalike — see our Unicode vs. fonts explainer for why partial coverage is an honest limit of the character set, not something more styles can quietly fix.

Why these three exist as separate, incomplete blocks at all

None of the three were designed as general-purpose decorative alphabets. Small capitals originated in the International Phonetic Alphabet and related linguistic notation, where a handful of specific letters needed a small-capital form to represent particular sounds — not a full A–Z set for arbitrary text. Superscript and subscript letters exist mainly to support footnote markers, ordinal indicators, and scientific/mathematical notation (like x² or H₂O), where only certain letters ever actually appear in that position in real use. Unicode assigned characters to match those real, historical use cases — it never set out to build three complete alternate alphabets, which is exactly why coverage stops wherever the original use case did.

A worked example across all three

Take the word "EXTRA". In small caps, every letter converts except X, which stays a plain capital: ᴇXᴛʀᴀ. In superscript, only E, T, R and A have assigned uppercase glyphs while X does not (X is one of the missing uppercase superscript letters), giving ᴱX ᵀᴿᴬ with X left plain. In subscript, none of the five letters have an assigned uppercase glyph at all — since subscript has zero uppercase coverage — so "EXTRA" stays completely unstyled in subscript regardless of which letters it contains. This one word demonstrates all three coverage patterns at once: nearly-complete, partially-complete, and entirely-unstyled for uppercase.

Choosing the right one for your use case

• A stylized short label or heading (a bio line, a title): small caps reads as more of a deliberate typographic choice, with only X as a gap to be aware of.
• Footnote-style markers or ordinal-like text (referencing a numbered note, a mathematical exponent): superscript is the semantically closest match, and its full lowercase/digit coverage makes it reliable for that narrower purpose.
• Chemical formulas or similar notation (H₂O-style subscripted numbers): subscript digits are fully covered; just don't expect subscript letters beyond the 16 supported lowercase ones, and never expect uppercase.

Where each style tends to actually get used

In practice, small caps shows up most often as a stylistic choice for names, headers, or short taglines — anywhere a slightly formal, uniform look is wanted without going as bold or distinctive as a full script or circled style. Superscript sees genuine use for ordinal-style flourishes (a stylized "1st"-looking label) and footnote-style markers appended to a word. Subscript is the least commonly used of the three outside its literal chemistry/math association, precisely because its coverage gaps (no uppercase, only 16 lowercase letters) make it impractical for anything beyond short, mostly-lowercase snippets.

How the Details panel helps you decide between the three

Rather than memorizing which of the 26 letters each style covers, expand the "Details" section under any small-caps, superscript or subscript result for your own text — it states exactly which letters and digits are supported for that specific style, computed fresh from what you actually typed, not a generic table. That's a faster and more reliable check than trying to recall the exception lists above for a specific word.

Questions people actually ask

Why is X missing from small caps specifically? Unicode simply never assigned a small-capital code point for X in any of the blocks that contribute small-caps letters — it's not a rendering bug, it's an actual gap in the character set itself, the same kind of gap described in our cursive missing-letters guide for a different style family.

Can I combine small caps with superscript? Not through a single style selection here — each result applies one mapping. Manually combining copied results from two different rows is possible but untested by us for consistency across apps.

Will Unicode ever add the missing subscript uppercase letters? Possibly, but not predictably — new Unicode characters are added only through the Unicode Consortium's formal proposal process, and there's no announced plan for completing this particular set as of this writing. Existing gaps have persisted for many Unicode versions.