Small Text Generator

Make tiny superscript, subscript, and small-caps text.

Style

Input

Small Text Output

ˢᵐᵃˡˡ ᵗᵉˣᵗ ¹²³

Characters: 14Words: 3

About small text

Unicode includes dedicated superscript, subscript, and small-capital letterforms used in math, chemistry, and typography. This tool maps your characters onto those glyphs, so the “tiny” text is plain Unicode that pastes into bios, captions, and messages without any formatting. Note that a few letters lack a subscript or superscript form and are left unchanged. Everything is generated locally.

Built and maintained by Meet Shah · Last updated 5 August 2026

What this tool is used for

Adding a superscript or subscript character in a field with no formatting.
Styling a footnote marker in a plain-text context.
Producing small caps for a label that must sit quietly beside larger text.
Making a caption visually secondary in a social post.
Testing how a field handles the superscript Unicode ranges.

Frequently Asked Questions

Which Unicode characters produce small text?: Three separate sets: superscripts (U+2070-209F), subscripts, and small capitals from the Phonetic Extensions block (U+1D00 onwards). They were encoded for phonetics and mathematics, not styling, which is why coverage is uneven.
Why are some letters missing?: Because the blocks were never designed as a complete alphabet. Superscript q has no character at all, and small-cap X is borrowed from elsewhere — so any 'small text' converter is stitching together sets that were never meant to combine.
Is small caps here the same as CSS font-variant?: No, and the CSS version is better wherever you control the styling: font-variant: small-caps renders real typographic small capitals, keeps the text searchable, and remains readable to screen readers. Unicode substitution is for places with no CSS.
Does it actually reduce the font size?: No — the glyphs are simply drawn smaller within a normal-size character cell. Line height and selection behaviour are unchanged, which is why small text often looks vertically misaligned next to normal text.
Where is it typically used?: Social bios, usernames and chat where styling is unavailable. Because the characters are semantically wrong, avoid it anywhere the text must be searched, sorted or read aloud.
Is it usable in a username or handle?: Often not — many platforms restrict handles to ASCII, and those that allow more may normalise it back. It is generally accepted in display names and post bodies, which is where it appears in practice.
Does it change the actual font size?: No. The characters are drawn small by design at whatever size the surrounding text uses, so they do not scale independently and cannot be made larger without replacing them.
What is the accessibility cost?: Real. Screen readers may announce the characters oddly or skip them, and the small glyphs are harder to read for anyone with low vision — with no way to enlarge them, since they are content rather than styling.

Common errors and gotchas

Assuming full alphabet coverage, since the superscript and subscript ranges have real gaps.
Using it for anything a screen reader must read, where the characters are announced poorly.
Expecting search to match, since these are distinct characters.
Using it for mathematical notation, which needs proper markup rather than lookalike characters.
Relying on consistent rendering, when many fonts lack these glyphs.