Small Text Generator: The Complete Guide (2026)

What small text is and how it works

Small text is ordinary text rewritten with special Unicode characters that are drawn smaller than normal letters, such as superscript letters (ᵗⁱⁿʸ), small capitals (ᴛɪɴʏ), and subscript letters (ₜₑₓₜ). A small text generator works by swapping each plain letter for its tiny counterpart, one character at a time, so the result keeps its look anywhere you can paste plain text.

That swap is the whole trick. The superscript t in ᵗⁱⁿʸ is not a t with a style applied. It is a different character, MODIFIER LETTER SMALL T at code point U+1D57, with its own name and its own entry in the Unicode Standard. An Instagram bio, a Discord display name, or a WhatsApp status cannot store fonts or formatting, but it can store any printable Unicode character. Replace the letters and the smallness travels with them.

The same mechanism powers bold and script text generators, which draw on the Mathematical Alphanumeric Symbols block. If you have read our guide to bold text and Unicode fonts, the principle is identical. The difference is where the characters live and how complete each alphabet is. Bold Unicode has a full set of letters. Small text does not, and the reasons are historical.

A short history of tiny letters in print

Printers used small letterforms long before computers. Superscript numerals mark footnotes in printed books and journals. Raised letters shorten words in abbreviations, such as the French Mlle for mademoiselle, and in ordinal numbers, where English once raised the st in 1st. Spanish still does this every day with the ordinal indicators º and ª, as in 1.º and 2.ª.

Small capitals have a separate lineage. A small capital has the shape of a capital letter and roughly the height of a lowercase one. Book typographers use them for acronyms that would otherwise shout from the page, and for the first words of a chapter, where a line of full capitals would look heavy. Good fonts draw small capitals as their own designs rather than shrinking the capitals, so the strokes keep the same weight as the surrounding text.

Subscripts belong mostly to science. Chemistry writes water as H₂O and carbon dioxide as CO₂, and mathematics uses subscripts to index variables, as in x₁ and x₂. In all of these traditions, the small form carries meaning. That is the thread that later leads into Unicode.

From phonetics to Unicode: the IPA and the Uralic Phonetic Alphabet

Most of the tiny letters in a small text generator were encoded for linguists. The International Phonetic Alphabet uses small capitals as separate symbols for separate sounds: ɢ is the voiced uvular plosive, ɴ the uvular nasal, ʀ the uvular trill, ʙ the bilabial trill, ʟ the velar lateral approximant, and ɪ and ʏ are near-close vowels. These live in the IPA Extensions block (U+0250 to U+02AF), which has been part of Unicode since version 1.1 in 1993.

The IPA also raises letters to mark how a sound is produced. A superscript h after a consonant marks aspiration, as in pʰ, a superscript w marks lip rounding, and a superscript j marks palatalization. Those modifier letters sit in the Spacing Modifier Letters block (U+02B0 to U+02FF), which is why ʰ, ʲ, ʷ, ˡ, ˢ, and ˣ are available as tiny letters today.

The biggest source is less famous. The Uralic Phonetic Alphabet, first published by the Finnish linguist Eemil Nestor Setälä in 1901, is a transcription system for Finnish, Hungarian, Estonian, Sami, and their relatives. It makes heavy use of small capitals, superscripts, and subscripts. Unicode 4.0 added the Phonetic Extensions block (U+1D00 to U+1D7F) in 2003, and the official Unicode chart for the block describes its contents as non-IPA phonetic extensions, mostly for the Uralic Phonetic Alphabet, and notes that the small capital, superscript, and subscript forms are for phonetic representations where style variations are semantically important. The same chart advises regular letters with markup for general text. Every tiny letter you paste into a bio is, in that sense, a borrowed phonetic symbol.

The Unicode blocks behind small text

A complete small text alphabet does not exist in any single block. A generator has to assemble each style from several places:

The Superscripts and Subscripts block is the only one designed for the job. It has held superscript and subscript digits and the signs + − = ( ) since Unicode 1.1, which is why exponents such as m² and 10⁶ render almost everywhere. The superscript 1, 2, and 3 sit elsewhere, in the Latin-1 Supplement, because they were inherited from the older ISO 8859-1 character set. Everything else is a patchwork of phonetic letters that happen to have the right shape.

Almost every superscript and subscript character carries a compatibility decomposition in the Unicode data. MODIFIER LETTER SMALL T is recorded as a superscript form of the plain t, and LATIN SUBSCRIPT SMALL LETTER T as a subscript form of it. Small capitals carry no such link: to Unicode, ᴛ is its own letter, not a styled t. That detail matters for search, as we will see.

Why coverage is uneven

Because the characters were encoded to serve phonetics, not decoration, each one arrived when a scholarly need justified it. The result is a set with holes. Subscript letters came in two batches: a, e, o, and x in Unicode 4.1 in 2005, then h, k, l, m, n, p, s, and t in Unicode 6.0 in 2010. A few phonetic subscripts (i, r, u, v) arrived with the Phonetic Extensions block, and j came later in Latin Extended-C. There is still no subscript b, c, d, f, g, q, w, y, or z, and no subscript capital of any kind.

Superscripts are nearly complete, with one famous gap. For most of Unicode's history there was no superscript q at all, because no phonetic system needed one. Unicode 14.0, released in 2021, finally added MODIFIER LETTER SMALL Q at U+107A5, in the Latin Extended-F block outside the Basic Multilingual Plane, along with modifier capitals C, F, and Q at U+A7F2 to U+A7F4. Unicode 17.0 added a modifier capital S at U+A7F1. These are genuine characters, but they are new, and a phone or font released before them shows an empty box where the letter should be.

Small capitals have their own gap: there is no Latin small capital X. The small capital F and S were added in Unicode 5.1 in 2008 in Latin Extended-D, and the small capital Q only in Unicode 11.0 in 2018, so even these can render as boxes on older systems.

Many generators hide the holes by substituting lookalikes from unrelated scripts: a Greek beta for subscript b, a Chinese tone mark for subscript c, a Canadian Syllabics character for superscript q. They look close enough at a glance, but they mean something else, sort as something else, and are announced as something else by assistive technology. The TextKit Small Text Generator takes the stricter path. It uses only genuine small forms, leaves the recent additions out for rendering reliability, keeps any unconvertible letter as plain text, and tells you exactly which characters those are.

How platforms handle small text

Bios and display names. Instagram, TikTok, X, and Discord store bios and display names as Unicode text, so all three styles paste in cleanly. Handles are different. The @ username on each of these platforms is restricted to a small ASCII set of letters, numbers, and a few symbols such as underscores or periods, so tiny letters are rejected there.

Messaging apps. WhatsApp messages, statuses, and the About line accept these characters, and so do Discord messages. Both apps have their own lightweight formatting for bold and italic, which makes small text most useful for what that formatting cannot do: a superscript footnote marker, a unit like km², or a chemical formula like H₂O.

Character limits. Bios are short, and every tiny letter counts as one character, the same as a plain letter. The small forms all sit inside the Basic Multilingual Plane, so each takes one UTF-16 code unit, unlike Mathematical Bold letters, which take two. If you are fitting a bio into a strict limit, check the result with the Character Counter or read the character count guide for how platforms measure length.

Rendering. Because the letters come from different blocks, fonts draw them with slightly different heights and weights. In some fonts the superscript i and n sit a touch higher than their neighbors. That unevenness is normal and is a good reason to keep small text to a word or two.

Accessibility: what screen readers hear

A sighted reader sees a tiny word. A screen reader sees a sequence of characters with official names. Depending on the software and its verbosity settings, a word in small text can be read aloud with names such as modifier letter small t, spelled out letter by letter, or skipped entirely. None of those outcomes delivers the word the author meant.

The W3C Web Content Accessibility Guidelines frame the principle in success criterion 1.3.1, Info and Relationships: information conveyed through presentation should be programmatically determinable or available in text. Small text does the opposite. It encodes a visual effect as a change of character identity, so the meaning a sighted reader gets is not what assistive technology receives.

The practical rule is simple. Treat small text as decoration. A tiny tagline under a name, a small caps label, or a footnote marker costs little. Your name, your links, your call to action, and anything a reader must understand should stay in plain text. The same caution applies to the other Unicode tricks on TextKit, from bold letters to the blank characters covered in our invisible text guide.

Search and SEO: why tiny text is hard to find

Search works by matching characters, and ᵗⁱⁿʸ is not the character string tiny. Whether the two ever match depends on normalization. Unicode defines a normalization form called NFKC that folds compatibility characters back to their plain equivalents, and because superscripts and subscripts carry compatibility decompositions, NFKC turns ᵗⁱⁿʸ into tiny. Small capitals carry no decomposition, so NFKC leaves ᴛɪɴʏ untouched.

Which systems apply NFKC, and when, varies. Search engines do not publish a character-by-character account of how they treat these letters, and in-app search on social platforms is even less predictable. The safe assumption is that a word written in small text may not be found by someone searching for the plain word. Hashtags written in tiny letters are a particular trap, because they may not join the plain hashtag at all.

For a web page, the conclusion is firm: never put titles, headings, product names, or any words you want to rank for in small text. For a bio, keep your searchable name in plain letters and use small text only for the decorative part.

Alternatives: real formatting and when to use it

Whenever you control the formatting, use it instead of Unicode small text. In HTML, the <sup> and <sub> elements raise and lower any text, including q and every accented letter, while leaving the underlying characters plain and searchable. MDN's reference for <sup> notes that it is meant for typographical conventions such as exponents, superior lettering, and ordinal numbers, not for purely decorative styling.

For small capitals on the web, CSS offers font-variant-caps: small-caps, which uses the font's own small capital designs when they exist. In word processors such as Word and Google Docs, the superscript, subscript, and small caps options do the same job. Some Markdown flavors, such as Pandoc's, support a superscript syntax, although CommonMark itself does not.

Real formatting scales with the reader's font size, works with every letter, and keeps meaning intact for screen readers and search. Unicode small text is the fallback for places that offer no formatting at all: social bios, usernames on platforms that allow Unicode, chat apps, spreadsheet cells, and plain-text fields.

How to use the Small Text Generator

Open the Small Text Generator, type or paste your text, and all three styles appear at once: superscript, small caps, and subscript. Each output has its own Copy button and its own character count. Under each box, a coverage note lists any character that could not be converted, such as q in superscript, x in small caps, or accented letters in every style, so you know exactly what your reader will see.

Before you commit a new bio, paste it into the app, save it, and check it on a second device. If a box appears, switch styles or choose a different word. For case changes such as Title Case or UPPERCASE in plain letters, the Case Converter guide covers the options that keep your text fully searchable.