Tiny Text Generator
Convert text into small caps, superscript or subscript Unicode characters, and copy them anywhere.
Every other style
What this tool does
A tiny text generator swaps ordinary letters for smaller Unicode characters - small capitals, superscript or subscript. The result is real text rather than a font, so it copies and pastes anywhere. A few letters have no small equivalent in Unicode and are left unchanged.
Converts your text into three different Unicode ranges at once, so you can compare them and copy whichever suits. Nothing is installed and nothing is uploaded.
Where a letter cannot be converted, this tool names it and explains why, instead of emitting a blank box or silently dropping it. That is the whole difference between this and the alternatives.
Copy link builds a shareable URL with your text stored in the page fragment after a #, not a query string - so the words never travel to a server or turn up in a log, and pasting the link into a browser restores the text exactly.
Every other Unicode style this site can produce - fullwidth, bubble, double-struck, monospace and the rest - sits one click away in an expandable panel beneath the small caps, superscript and subscript results, so browsing for a different effect never means leaving the page.
How to use it
- Type or paste your text into the box.
- Look at the three styles - small caps, superscript and subscript.
- Check the warning beneath if any characters could not be converted.
- Press Copy on the style you want and paste it wherever you need it.
Why use this generator
Small text helps in bios, usernames, footnotes and formulas where formatting is not available. Unicode contains small-capital, superscript and subscript letters, so tiny text can travel as plain text.
Why we built it
We built the tiny text generator to name the characters Unicode cannot produce instead of leaving blank boxes. Try other styles with the fancy text generator and the small caps generator.
For a neighbouring job there is also the Gothic Text Generator, the Upside Down Text Generator and the Italic Text Generator.
For a neighbouring job there is also the Blank Text Generator.
Who this tool is for
- Social media users styling a bio or caption
- Designers adding footnote-style text
- Gamers choosing a username
When to use it
- Adding a small tagline or footnote to a social media bio.
- Writing superscript or subscript in a plain-text field.
- Making a username or caption stand out.
- Typing chemical formulas or exponents where rich text is not available.
Why some letters do not convert
This is the honest answer that competitors avoid giving, and it is worth understanding.
These are not fonts. A font changes how a character is drawn; this changes the characters themselves. The small capital A you get here is a distinct Unicode character with its own code point, encoded because phonetics and linguistics needed it.
That origin is exactly why the set is incomplete. The small capitals block was added for the International Phonetic Alphabet and related notations, which never needed a small capital Q or X - so neither was ever encoded. They do not exist to be used.
Superscript has the same problem in one place: there is no superscript q. Subscript is thinner still - only a, e, h, i, j, k, l, m, n, o, p, r, s, t, u, v and x exist as subscript letters.
Many generators substitute a lookalike from another alphabet for the missing letters. That produces text which renders inconsistently across devices and confuses screen readers. Leaving the letter alone is the correct behaviour, and this tool tells you when it has done so.
| Style | Missing | Complete for |
|---|---|---|
| Small caps | q, x | All other letters and digits pass through |
| Superscript | q | All other letters, all digits, + - = ( ) |
| Subscript | Most consonants | a e h i j k l m n o p r s t u v x, all digits |
Where tiny text works and where it does not
Because the output is real text, it works in almost any field that accepts typing - social media bios and posts, messaging apps, document titles, spreadsheet cells and usernames on many platforms.
It will not work where a service restricts input to a limited character set. Some platforms strip non-ASCII characters from usernames, and some payment and government forms reject them outright. If tiny text vanishes after you submit a form, that is why.
Rendering depends on the device having a font that covers these code points. Modern phones and desktops generally do. Older devices and some embedded browsers may show boxes for the less common characters - which is a limitation of the reader, not of the text you produced.
How the character count is worked out
The counter above the results does not simply read the length of the text. Small caps, superscript and subscript characters each live in the Basic Multilingual Plane - the first, oldest block of Unicode - so every one of them takes a single 16-bit code unit, the same as an ordinary letter. That is not true of every styled-text style on this site: bold, italic and cursive letters live further out in Unicode and need two code units each, which is why those tools can make a platform's character count jump.
Tiny text does not have that problem, but the count here still uses grapheme clusters rather than raw code units, counted with the browser's own Intl.Segmenter. That is the more general fix: a handful of Unicode text tools attach combining marks or pair surrogates in ways that make a plain length check misleading, and counting what a person would actually call "one character" is the only version of the number worth showing.
Accessibility, and using this responsibly
Screen readers handle these characters inconsistently. Some read a small capital A as "a", some as "latin letter small capital a", and some skip it. A bio written entirely in tiny text can be unusable for someone using assistive technology.
Search engines treat these as distinct characters too, so styled text is not matched against ordinary search terms. Keeping your important words in normal characters and using tiny text for decoration is the sensible balance.
What you give it, and what you get back
| Item | Details |
|---|---|
| Input | Any text; letters are converted, other characters are left alone. |
| Output | Small caps, superscript and subscript versions side by side. |
| Notes | Characters with no tiny form are named so you know what stayed normal. |
Issues you may run into
| What you see | Why it happens | What to do |
|---|---|---|
| Boxes or question marks appear | The reader's device or font has no glyph for these Unicode characters. | Try a different style, or test on the platform where it will be posted. |
| Tiny text is stripped when pasted | Some sites normalise or filter special characters. | Paste a shorter piece, or use a different style. |
| A screen reader reads it strangely | Assistive technology announces each special character by name. | Avoid it for anything that must be accessible, such as names, links or key information. |
Assumptions and limitations
- Small capital Q and X do not exist in Unicode and are left as ordinary letters. There is no workaround; they were never encoded.
- There is no superscript q. Subscript covers only about half the alphabet.
- Output depends on the reader’s device having a font that covers these characters. Older devices may show boxes.
- Screen readers announce these characters inconsistently, so tiny text should not carry information a reader needs.
- Some platforms strip non-ASCII characters from usernames and form fields.
Frequently asked questions
What is a tiny text generator?
It converts ordinary letters into smaller Unicode characters - small capitals, superscript or subscript. The output is genuine text rather than an image or a font, so you can copy and paste it into any field that accepts typing.
Why are some of my letters not converted?
Because those characters do not exist in Unicode. There is no small capital Q or X, and no superscript q - they were never encoded, since the phonetic notations these ranges were built for never needed them. This tool leaves them as ordinary letters and tells you which ones.
Is this a font, and why does it look different on another device?
It's real text, not a font. Each styled character is its own Unicode code point, which is why it survives copy and paste into apps that have no idea your font existed - a font would only change how normal letters are drawn on your own screen. That also explains device differences: rendering depends on the fonts installed on the reading device, and if one has no font covering a character it shows a box. The text itself is correct - that reader simply cannot draw it.
Will tiny text work on Instagram and TikTok?
In bios, captions and comments, generally yes. Usernames are less reliable - several platforms restrict those to a limited character set and will reject or strip the characters. Test before relying on it.
Can screen readers read tiny text?
Inconsistently. Some read a small capital A as an ordinary "a", others announce the full Unicode name, others skip it. Anything a reader genuinely needs should stay in ordinary characters.
Is small caps the same as lowercase?
No. Small capitals are capital letter shapes drawn at roughly lowercase height. Lowercase letters have different shapes entirely. In Unicode they are separate characters with separate code points.
Does Copy link upload my text anywhere?
No. The link stores your text after a # in the URL, which browsers treat as a fragment and never send to a server - unlike the part before the #, which is what gets logged. Opening the link just re-reads the fragment locally and rebuilds the text.
Why does the character count look different from my word processor?
This tool counts grapheme clusters - what a reader would call one character - using the browser's own text-segmentation logic, rather than raw string length. For tiny text that number matches simple letter counting almost exactly, because small caps, superscript and subscript all sit in Unicode's oldest block and need only one code unit each.