The Unicode Character Sets Behind ˢᵐᵃˡˡ ᵗᵉˣᵗ (And Why Some Letters Are Missing)

You see small text everywhere on Instagram and TikTok: ˢᵐᵃˡˡ ᵗᵉˣᵗ ˡⁱᵏᵉ ᵗʰⁱˢ. It looks like someone shrunk regular letters. But it's not shrinking - it's a completely different set of characters.

Those aren't small "a"s and "b"s. They're superscript characters: ᵃ (U+1D43) and ᵇ (U+1D47). Different Unicode code points entirely. Understanding this explains both how small text works and why it sometimes breaks.

The Three Types of Small Text

Unicode includes three character sets commonly used for small text effects, each with different coverage and compatibility:

Notice the gaps. Subscript is missing 10 letters - nearly half the alphabet. That's not a generator limitation; those Unicode characters simply don't exist. The characters we have come from phonetic notation (IPA), mathematical typography, and historical printing conventions.

Platform Compatibility

Where does small text actually work? I tested across platforms:

The pattern: modern social platforms handle Unicode well. Email is unpredictable. SMS is a gamble based on the recipient's device.

How to Generate Small Text

A small text generator converts standard characters to their Unicode equivalents. The conversion is straightforward:

Each letter maps to a specific Unicode code point. The generator just looks up each character and returns the corresponding superscript or small cap version.

For missing letters, generators have three strategies:

• Skip: Leave the letter as regular size (looks inconsistent)
• Substitute: Use a visually similar character (might not match)
• Approximate: Use a different Unicode character that looks close (can cause rendering issues)

Practical Bio Examples

Small text works best mixed with regular text for visual hierarchy:

Numbers and Special Characters

Unicode superscript includes numbers and some symbols:

Numbers have complete coverage in both superscript and subscript - useful for dates, years, or mathematical notation.

Accessibility Concerns

Screen readers struggle with small text. Here's how common readers handle "ʰᵉˡˡᵒ":

• VoiceOver (iOS): "modifier letter small h, modifier letter small e..." - reads each character's technical name
• NVDA (Windows): Often skips characters entirely or reads them as blanks
• TalkBack (Android): Inconsistent - sometimes reads, sometimes skips

The takeaway: never put essential information in small text. If your bio says "ᶜᵒⁿᵗᵃᶜᵗ: [email protected]" in small text, screen reader users may not be able to access your contact info.

Use small text for style, regular text for substance.

Why Some Text Breaks

When small text shows as boxes (□) or question marks, the cause is usually:

1. Missing font support: The device's font doesn't include that Unicode character
2. Old operating system: Older Android/iOS versions have incomplete Unicode support
3. App-specific rendering: Some apps use limited character sets
4. Copy-paste encoding: Copying through certain apps can corrupt Unicode

If you're seeing issues, the problem is almost always on the viewing device, not how the text was generated.

Generate and Test

The safest workflow:

1. Generate your small text
2. Test it on your target platform before publishing
3. Check it displays correctly on both iOS and Android if possible
4. Keep essential keywords in regular text for searchability
5. Use small text as accent, not primary content

Small text adds visual distinction when used sparingly. Understanding that it's Unicode characters - not formatting - helps you use it effectively and troubleshoot when it doesn't display as expected.