Three ways to make text small
None of the three covers the full alphabet — a handful of letters have no small form and fall back to look-alikes. The tiny text generator on our home page lists every letter in all three styles with the gaps marked.
What people mean by "small text"
Three different questions arrive at this page, and only two of them have an answer.
- "Make my bio font smaller." Not possible, by anyone. Font size in a bio, caption or chat window belongs to the app. No generator changes it, including this one.
- "I want letters that look small." This is the answerable version, and it is what the tool does — it swaps your characters for different characters that are drawn small.
- "I want tiny symbols for decoration." Also answerable, but superscript and subscript serve that better than small caps. Pick by how much you need it read versus seen.
The distinction matters because it predicts what will break. Font size is styling, so it never survives a paste. Characters are content, so they survive everywhere the characters themselves are allowed — which is most places, with the specific exceptions below.
Where small text fits — field by field
These are the fields people actually paste into, with the limit each one enforces. Verified 2026-08-18; platforms change them without notice.
| Platform | Field | Limit | Accepts small text |
|---|---|---|---|
| Bio | 150 | Yes | |
| X (Twitter) | Bio | 160 | Yes |
| TikTok | Bio | 80 | YesSome accounts now report 160 — 80 is the safe assumption. |
| Discord | About Me | 190 | Yes |
The limits are counted in characters, not bytes, which is the good news — see the next section for why that distinction decides whether your text fits.
The character budget
The common worry is that converting to small text will blow past a bio limit. For two of the three styles it will not, and the reason is worth understanding because it also explains the one case where it does.
Platforms count text in UTF-16 code units. Nearly every small text character is one unit, exactly like a normal letter, so the count does not move. The exception is characters outside the Basic Multilingual Plane, which take two units each.
| Style | 26 letters cost | vs. plain | UTF-8 bytes |
|---|---|---|---|
| Small Caps | 26 chars | same | 67 (2.6×) |
| Superscript | 26 chars | same | 70 (2.7×) |
| Subscript | 32 chars | +6 | 84 (3.2×) |
So: small caps and superscript are free. If your text fitted before, it fits after. Subscript costs extra — the letters c, d, f, g, w, z have no true subscript form and borrow from the mathematical script block, which sits outside the BMP. Each one of those letters adds a character. A 140-character bio with a dozen of them will overflow a 150-character field.
The byte column is the part that catches people out elsewhere. Small text roughly triples in UTF-8, so a system that limits by bytes rather than characters — some SMS gateways, older web forms, database columns sized in bytes — will accept far less than you expect. The counter in the tool shows both numbers for this reason.
If it does not fit
When the counter goes red, there are three fixes in order of how little they cost you:
- Switch subscript to small caps. If you were using subscript purely for the look, this reclaims one character for every c, d, f, g, w or z, and gains legibility at the same time.
- Convert only part of the line. A small caps label followed by normal text reads better than a fully converted bio anyway, and normal characters are what search and screen readers need.
- Cut words, not characters. Trimming a word removes several units at once; hunting for individual characters to delete rarely gets you there.
Worth knowing before you experiment: platforms differ in what they do with overlong input. Some truncate silently at the limit, which can cut a two-unit character in half and leave a replacement box at the end. Others refuse to save and show a generic error. Neither tells you the real cause, so check the counter first.
Where it fails silently
Small text rarely produces an error message. It just does not do what you expected, which is harder to debug.
Usernames reject it outright
Handles are the single most common disappointment, and it is not a bug. Every major platform restricts them to an ASCII whitelist:
| Platform | Length | Allowed characters |
|---|---|---|
| 30 | a–z 0–9 . _A period cannot start or end the name, and two in a row are rejected. | |
| TikTok | 2–24 | a–z 0–9 . _No spaces. Changeable only once every 30 days, so a failed attempt is costly. |
| Discord | 2–32 | a–z 0–9 . _Lowercase only. Cannot start or end with . or _, and no two in a row. The display name above it is a separate field with no such restriction. |
Not one of those whitelists includes a small text character, so there is no trick or workaround — the field will refuse it every time. What people usually want is the display name sitting above the handle, which is a separate field with no character restriction.
Search stops working
ꜱᴍᴀʟʟ ᴛᴇxᴛ and "small text" are unrelated strings to a computer. Platform search will not match them, hashtags built from small text will not group with the normal-text version, and browser find-in-page skips it. Converting a business name in a bio makes that bio unfindable by anyone searching the name.
Screen readers cannot read it
These characters come from phonetic notation, so assistive software may announce them by their technical names, mangle them, or skip them. Behaviour differs across NVDA, JAWS and VoiceOver and none of it is dependable. Keep anything a reader needs — links, instructions, your actual name — in normal characters.
Autocorrect gives up
Spellcheck does not recognise the text as words, so typos pass through unflagged. Proofread before converting rather than after.
FAQ
Small caps and superscript take exactly as many characters as your original text, so if it fitted before converting, it fits after. Subscript is the exception: six letters (c, d, f, g, w, z) each count as two characters instead of one. The tool above shows the live count against whichever platform field you pick.
Username fields are not text fields in the normal sense. Instagram, TikTok and Discord all restrict handles to lowercase letters, digits, periods and underscores — an ASCII-only whitelist. Every small text character falls outside it, so the save silently fails or the field refuses the input. Bios, display names and captions have no such restriction, which is why the same string works there.
Usually not. Most platforms count UTF-16 code units, and small caps and superscript characters are one unit each, same as a normal letter. Where it does cost more is in byte terms: the same text takes roughly two and a half times the bytes in UTF-8, which matters for SMS gateways and older forms that limit by bytes rather than characters.
No, and no tool can change font size in a bio or caption — that is set by the app, not by your text. Small text works by substituting different characters that happen to be drawn small. The practical difference: font size resets when you paste elsewhere, while these characters travel with the text.
No. To a computer, ꜱᴍᴀʟʟ and small are unrelated strings, so platform search, hashtags and browser find-in-page will all miss it. Keep your name, brand or any keyword you want found in normal characters, and use small text for the decorative parts.