Skip to content
BoldlyType
Part of: Fonts
How-To

Small Caps Text Generator: ꜱᴍᴀʟʟ ᴄᴀᴘꜱ to Copy & Paste

A small caps generator swaps your lowercase letters for real Unicode small-capital characters (ʙ, ᴄ, ᴅ…) that copy-paste into bios and captions because the style is baked into the character. The catch: it is a patchwork of phonetic letters, not a clean font. Two letters are weak spots — there is no small-cap X (it stays a normal x), and small-cap Q has no widely supported character, so generators substitute an o-shaped stand-in (ǫ) that looks slightly off. Use BoldlyType's free formatter, then sanity-check how it renders.

Shreyas Bagal·Jun 22, 2026·6 min

A small caps generator swaps your lowercase letters for real Unicode small-capital characters (ʙ, ᴄ, ᴅ…) that copy-paste into bios and captions because the style is baked into the character. The catch: it is a patchwork of phonetic letters, not a clean font. Two letters are weak spots — there is no small-cap X (it stays a normal x), and small-cap Q has no widely supported character, so generators substitute an o-shaped stand-in (ǫ) that looks slightly off. Use BoldlyType's free formatter, then sanity-check how it renders.

Key takeaways

  • Small caps text is real Unicode characters substituted for your letters, so the style survives copy-paste into places that strip formatting — bios, usernames, captions.
  • It is not a clean font or a single Unicode block. It is a patchwork stitched together from phonetic alphabets across three different Unicode blocks.
  • There is no Unicode small-capital X. Generators leave a normal lowercase x in your word, so any word with an X looks slightly off.
  • There is no widely supported small-capital Q either, so generators substitute an o-with-a-tail (ǫ). It renders almost everywhere but reads as an o, not a Q — words with q look subtly wrong.
  • Because the genuine small-cap characters come from scattered blocks, rendering depends on each device's font coverage: the same string can look crisp on one phone and show boxes (□) on another.
Small Caps Text Generator: ꜱᴍᴀʟʟ ᴄᴀᴘꜱ to Copy & Paste
On this page

How-to guide

Want text that looks like ꜱᴍᴀʟʟ ᴄᴀᴘꜱ and still copy-pastes into your Instagram bio, a username, or a TikTok caption? A small caps generator does exactly that. You type normal text, it hands back small-capital characters, and you paste them anywhere — the style sticks because it is baked into each character, not applied as a font on top.

But small caps has a strange backstory that explains its quirks. It is not a clean, designed alphabet. It is a patchwork of phonetic letters scattered across several Unicode blocks, and that history is exactly why two letters are imperfect: one is missing entirely, and the other has no good character to use. This post shows you the working examples and then tells you the honest truth about where it breaks.

You can convert any text to small caps right now for free — no signup, nothing stored, all in your browser.

What small caps text actually is

When you use a small caps generator, you are not applying a font. You are swapping each of your lowercase letters for a different Unicode character that happens to be shaped like a small capital.

Type hello and the tool returns ʜᴇʟʟᴏ. Those are not styled h, e, l, o — they are five separate Unicode characters (ʜ ᴇ ʟ ᴏ) that live at their own codepoints. Because the small-cap look is part of the character's identity, it travels with the text. That is why it survives in bios, usernames, and caption fields that normally strip out any formatting you try to apply.

This is the same mechanic behind bold Unicode text and other copy-paste styles. The text is plain text — it just happens to use unusual characters.

Here is the part most generators never tell you: small caps is not a single Unicode block or a tidy alphabet. It was assembled from characters added at different times, for different reasons — mostly phonetic transcription (the International Phonetic Alphabet and Americanist notation for Indigenous languages). They were never meant to be a display font. Using them for styled text is, technically, repurposing linguistics tools as decoration. It works beautifully — until it doesn't, and the patchwork origin is why.

The patchwork: an alphabet stitched from three blocks

The genuine small-caps characters were assembled across three different Unicode blocks:

  • IPA Extensions — 8 letters: B (ʙ), G (ɢ), H (ʜ), I (ɪ), L (ʟ), N (ɴ), R (ʀ), Y (ʏ). These shipped with early Unicode for phonetics.
  • Phonetic Extensions — 14 letters: A (ᴀ), C (ᴄ), D (ᴅ), E (ᴇ), J (ᴊ), K (ᴋ), M (ᴍ), O (ᴏ), P (ᴘ), T (ᴛ), U (ᴜ), V (ᴠ), W (ᴡ), Z (ᴢ).
  • Latin Extended-D — 2 letters: F (ꜰ) and S (ꜱ). This is why the small-cap S in this article's title lives in a different block from most of its neighbors.

Add those up and you get 24 genuine small-capital letters. The remaining two — X and Q — are the problem children. There is no Unicode small-capital X at all, and no widely supported small-capital Q, so generators fall back to imperfect substitutes for both. That gap is the single most important thing to know before you rely on small caps.

Real copy-paste examples

Drop these straight into a bio or caption. Each is the small-caps version of the word above it.

  • good vibes only → ɢᴏᴏᴅ ᴠɪʙᴇꜱ ᴏɴʟʏ
  • link in bio → ʟɪɴᴋ ɪɴ ʙɪᴏ
  • content creator → ᴄᴏɴᴛᴇɴᴛ ᴄʀᴇᴀᴛᴏʀ
  • available now → ᴀᴠᴀɪʟᴀʙʟᴇ ɴᴏᴡ
  • stay soft → ꜱᴛᴀʏ ꜱᴏꜰᴛ

Notice how the F in "soft" (ꜰ) and the S characters (ꜱ) come from the Latin Extended-D block — on a font with full coverage they blend in seamlessly, but they are doing more work than they look. For a gallery of other copy-paste looks, see our aesthetic fonts roundup.

Coverage gaps: where small caps breaks

This is the honest section every small caps page should have and most skip. Small caps is genuinely useful, but it has hard limits baked into Unicode itself. The two weak letters are X and Q — and they break for different reasons.

There is no small-cap X

This is the first one. Of all 26 English letters, X is the only one with no Unicode small-capital character whatsoever. Small capitals were added to Unicode as phoneticians needed them for notation, and a small-cap X was apparently never needed — so it was simply never proposed or added.

The practical consequence: every generator passes a lowercase x straight through unchanged. So a word with an X comes out with small caps on every letter except the x:

  • example → ᴇxᴀᴍᴘʟᴇ (the x stays normal-size)
  • next → ɴᴇxᴛ
  • extra → ᴇxᴛʀᴀ

There is no fix — it is a gap in Unicode, not a flaw in any tool. If a word's appearance matters and it contains an x, rephrasing is your only option.

The Q is an o-shaped stand-in

Q is the second weak letter, but its problem is the opposite of X's. There is no widely supported small-capital Q for a generator to use, so instead of leaving a normal q in your word, BoldlyType substitutes the closest available character: ǫ, a lowercase o with a small hook (technically an ogonek). It is a well-established, well-supported character, so — unlike a missing glyph — it almost never shows as a box.

The catch is its shape. It reads as an o, not a Q:

  • queue → ǫᴜᴇᴜᴇ (the first letter scans like an o)
  • quick → ǫᴜɪᴄᴋ
  • squad → ꜱǫᴜᴀᴅ

So q-words render reliably but look subtly wrong — ǫᴜᴇᴜᴇ reads a bit like "oueue." A genuine small-cap Q character does exist in Unicode, but it was added very recently and is missing from most fonts, which is exactly why generators avoid it in favor of the dependable-but-imperfect ǫ. Treat q like x: a weak letter worth rephrasing around if its look really matters.

Boxes, tofu, and mixed sizes

Beyond X and Q, the genuine small-cap letters can still render unevenly. Because they are scattered across three blocks, rendering depends on each device having glyphs for those specific characters. A font might cover the Phonetic Extensions letters but not the Latin Extended-D ones (F and S), so some letters look like proper small caps while others show as boxes (□) or normal-size fallbacks. The same string can look crisp on your phone and broken on someone else's. This is why your fancy text sometimes shows up as boxes — and it is unavoidable with a patchwork alphabet.

Accessibility and search

The caveats that apply to all styled Unicode apply here too, and you should weigh them:

  • Screen readers may skip the characters entirely or read them as nonsense, so people using assistive technology can miss your text.
  • In-app search won't match small-caps text against normal-letter queries, so a small-caps username or hashtag may not surface when someone searches for the plain spelling.
  • Links and handles break. Never run a URL, @mention, or #hashtag through a small caps generator — many apps stop treating styled characters as a working link or tag.

The rule of thumb: small caps is safe for decoration — a bio flourish, a username accent, a caption keyword — but not for body text, links, or anything that has to be searchable or fully accessible. Keep the load-bearing parts of your text in plain letters and let the small caps decorate around them.

The honest one-liner

A small caps generator is a find-and-replace machine. It looks up each of your letters in a table of Unicode small-capital characters and hands back the look-alikes, which is why the style survives a copy-paste anywhere. Just remember the two weak letters: X stays a normal x because Unicode has no small-cap X, and Q comes out as an o-shaped ǫ because there is no dependable small-cap Q to use. Test in the app you are targeting, and pick wording that steps around x and q when the look has to be perfect.

Ready to put this into practice?

Browse all formatters

Sources

Spotted an error? Email hello@boldlytype.com — we update guides quarterly and welcome corrections.

Frequently asked questions

Latest questions readers ask us about this topic.

What is a small caps generator?

A small caps generator is a free tool that converts your normal lowercase text into ꜱᴍᴀʟʟ ᴄᴀᴘꜱ — uppercase letter shapes drawn at roughly lowercase height. It does this by substituting each letter for a real Unicode character, not by applying a font. That distinction matters: because the styling is baked into the character itself, the small caps travel with the text when you copy and paste it into an Instagram bio, a username field, a TikTok caption, or anywhere else that normally ignores formatting. BoldlyType's formatter does this in your browser instantly, with no signup and nothing stored. Type on the left, copy the small-caps version on the right, paste it where you want it. The same mechanic powers bold, italic, and other Unicode styles.

Does small caps text work everywhere, or will it show boxes?

It works in most modern apps, but it is not guaranteed everywhere. Small caps are scattered Unicode characters rather than a font feature, so whether they display correctly depends on the device, app, and font having a glyph for each specific character. When a glyph is missing, you get a box or tofu (□) instead, or letters fall back to mismatched sizes. The same string can look perfect on your phone and broken on someone else's older device. This unevenness is a direct result of the patchwork origin — the letters come from several different Unicode blocks added in different years. Always paste a test into the actual app before you commit. If you see boxes, that platform or font simply lacks coverage for those characters.

Why does the X in my word stay normal-sized?

Because there is no Unicode small-capital X — at all. Of the 26 English letters, exactly one (X) has never been encoded as a small capital. Small capitals were added to Unicode as phoneticians needed them for notation, and a small-cap X was apparently never needed, so it was never proposed or added. Twenty-five letters have small-cap forms; X does not. Every small caps generator handles this the same way: it passes your lowercase x through unchanged. So a word like "example" renders with small caps on every letter except the x, which stays a normal-size lowercase letter and looks slightly out of place. There is no fix — it is a genuine gap in Unicode itself, not a bug in the generator. If a word's look matters and it contains an x, consider rephrasing.

Why does the Q look like an o with a tail?

Because there is no widely supported Unicode small-capital Q for a generator to use, so it substitutes the closest available stand-in: ǫ, a lowercase o with a small hook (an ogonek). On BoldlyType, typing "queue" returns ǫᴜᴇᴜᴇ. The upside is that ǫ is an old, well-supported character, so it almost never shows as a box. The downside is the shape: it reads as an o, not a Q, so words with q look subtly wrong (ǫᴜᴇᴜᴇ scans like "oueue"). A genuine small-cap Q character does exist in Unicode but was added very recently and is missing from most fonts, which is why generators avoid it. Treat q, like x, as a weak letter — and rephrase if a q-word's appearance really matters.

Are these the same as the small caps in Word or CSS?

No, they are a different mechanism entirely. Word processors and CSS create small caps with a typographic feature — font-variant: small-caps or the OpenType smcp feature — which tells the font to render real capitals at a smaller size. That is styling applied on top of normal letters; copy the text into a plain field and it reverts to normal case. A small caps generator instead swaps in distinct Unicode characters that are small caps permanently. The upside is they survive in places that strip formatting, like social bios and usernames. The downside is they are technically phonetic letters being repurposed as a display alphabet, so coverage is uneven and accessibility suffers. For documents, use the real OpenType feature; for social fields, use the Unicode characters.

Why do small caps look uneven or mixed-size sometimes?

Because the alphabet is stitched together from several Unicode blocks added across different years. Eight letters (B, G, H, I, L, N, R, Y) come from the IPA Extensions block; fourteen more (A, C, D, E, J, K, M, O, P, T, U, V, W, Z) come from Phonetic Extensions; and F and S come from Latin Extended-D. A given font may include glyphs for some of these blocks but not others, so a few letters render as proper small caps while others fall back to normal size or boxes. The small-cap S in this article's title, for example, lives in a different block from most of its neighbors. When you see a mix of heights, that font simply has partial coverage. Test in the target app and pick wording that avoids the weakest letters, x and q.

Related questions

The sub-questions readers ask next — answered, with where to go.

They're symbols, not fonts. A 'fancy font' generator doesn't change your typeface — it swaps each letter for a look-alike character from a different Unicode block (𝗮 is a different code point than a). Because the styling lives in the characters themselves, it travels with the text when you copy and paste, which is why it survives into Instagram or LinkedIn where real custom fonts don't. The trade-off is that the text is no longer plain letters, so treat it as decoration for short phrases, not body copy.

Try every style at once

That's a missing-glyph fallback. When an app or older device doesn't have a glyph for a rarer Unicode style (some scripts and decorative blocks), it renders a box (▯) or question mark instead. Sans-serif bold and italic are the most widely supported; bold script, fraktur and double-struck are the most likely to break on older Android keyboards or low-end devices. Always preview on a phone before you post, and keep the safe styles for anything that matters.

Use the safe social styles

Yes. Neither editor has a bold button because both are plain-text by design, but both render Unicode. Generate the bold text, copy it, and paste it straight into the bio field — the bold survives. Keep it to one emphasised phrase rather than a whole bold bio, since a wall of bold reads as shouting and is harder for screen readers. Links and @handles should stay in plain characters so they remain tappable.

Open the bold generator

Bold Unicode (𝗯𝗼𝗹𝗱) is for emphasis and hooks — the first thing a reader's eye lands on. Italic Unicode (𝘪𝘵𝘢𝘭𝘪𝘤) signals nuance: titles, product names, quotes and wry asides. Both come in sans and serif variants, and there's a combined sans bold-italic for text that's both. The rule is the same for each: use them on a single word or phrase, never for full paragraphs, and never on links or hashtags.

Open the italic generator

Related in this series

See all in Fonts

Explore the topic cluster

More tools and guides across this topic cluster.

StyleText Generator (20+ styles)Type once, see every Unicode style at once.StyleBold Text Generator𝗕𝗼𝗹𝗱 Unicode that pastes into any bio or post.StyleItalic Text Generator𝘐𝘵𝘢𝘭𝘪𝘤 for titles, quotes and asides.StyleLowercase / Small-Caps FormatterThe soft, understated aesthetic look.StyleSocial Text FormatterStyles tuned to paste cleanly into any feed.CounterCharacter CounterCheck limits before fancy text eats your budget.

Get the next post.

Craft notes on writing for the internet. One short email, every other week. No spam.

Keep reading

Superscript & Subscript Generator: Tiny Text to Copy-Paste
How-To

Superscript & Subscript Generator: Tiny Text to Copy-Paste

Tiny raised "ᵗⁱⁿʸ ᵗᵉˣᵗ" and dropped subscript come from scattered Unicode blocks built for math and phonetics — not social bios. Here's how a superscript generator actually works, copy-paste examples, and the letters that quietly break.

Shreyas Bagal·Jun 22, 2026·8 min
Read article
Vaporwave Text Generator: Aesthetic Wide Fullwidth Text
How-To

Vaporwave Text Generator: Aesthetic Wide Fullwidth Text

The wide, spaced "ａｅｓｔｈｅｔｉｃ" vaporwave look isn't added spaces or a font — it's fullwidth Unicode characters, each one a distinct code point that occupies a full character cell. Here's exactly what that means, real copy-paste examples, the coverage gaps (no fullwidth space, double-width rendering, boxes on some devices, character-limit weighting on X), and how to make it without breaking accessibility.

Shreyas Bagal·Jun 22, 2026·7 min
Read article
Gothic Text Generator: Blackletter & Old English to Copy-Paste
How-To

Gothic Text Generator: Blackletter & Old English to Copy-Paste

"Gothic," "blackletter," "fraktur," and "Old English" all name the same angular Unicode style. Here's how a gothic text generator builds it, real copy-paste examples, why plain Fraktur secretly stitches characters from two Unicode blocks — and the honest list of where it breaks.

Shreyas Bagal·Jun 22, 2026·7 min
Read article