How to Make Real ꜱᴍᴀʟʟ ᴄᴀᴘs Text for Bios and Social Profiles
Turn plain text into small caps that paste into any bio or post. These are real Unicode glyphs, not a font, with notes on gaps and screen readers.
How to Make Real ꜱᴍᴀʟʟ ᴄᴀᴘs Text for Bios and Social Profiles
You have probably seen a profile where the bio reads in those calm, even letters that look like capitals shrunk down to the height of lowercase. That style is called small caps, and it has a quiet, typeset feeling that plain text and ALL CAPS both miss. The catch is that Instagram, TikTok, Discord, and X give you a single text field with no font picker. You cannot style the words. So how does anyone get small caps into a bio that only accepts plain text?
The answer is Unicode. Instead of styling letters, you swap each letter for a separate character that already looks like a small cap. The Small Caps Generator does that swap for you and hands back text you can copy and paste anywhere a plain string is allowed.
Small caps are characters, not a font
This is the part that trips people up, so it is worth being precise. There are two completely different ways to get small caps on a screen.
The first is the CSS rule font-variant: small-caps. It tells the browser to render lowercase letters using small-capital forms. It works beautifully, but only inside a web page you control, where you can ship a stylesheet. The moment that text leaves the page, into a copied string, a username field, or a chat box, the styling falls away and you are left with ordinary letters. The look lived in the CSS, not in the text.
The second way, the one this tool uses, is to pick real Unicode characters that are shaped like small caps. The small-cap A is the actual code point U+1D00 (ᴀ), pulled mostly from Unicode's phonetic-extension blocks. Because the appearance is baked into the character itself, it travels with the text. Paste it into a bio, a CSV cell, a filename, or a database field and it keeps its shape. Nothing needs a stylesheet, because there is no styling involved at all. The one requirement is that the device reading the text ships a font with these glyphs, which nearly every modern phone and browser does.
So when you copy small caps from this tool, you are not copying a font. You are copying letters that happen to look the way they do.
A worked example
Take the word toolora and run it through the converter. Out comes:
ᴛᴏᴏʟᴏʀᴀ
Each of those is a distinct character. The first one, ᴛ, is U+1D1B. They are not a styled version of the lowercase word, and they are not the uppercase word made small. They are seven separate Unicode points sitting in a row that read as one word in small caps. If you select that line and paste it into an X post, every one of those code points goes along for the ride, unchanged.
Compare the three versions of the same word so the difference is obvious:
- plain: toolora
- ALL CAPS: TOOLORA
- small caps: ᴛᴏᴏʟᴏʀᴀ
ALL CAPS reads as shouting. Plain text reads as nothing in particular. Small caps land in the middle, capital letterforms at a softer height, which is exactly why bios and section labels lean on them.
The gaps in the small-caps alphabet
Unicode was never tidied into a clean, complete small-cap alphabet, so there are holes. Two letters matter in everyday use: s and x have no dedicated small-capital glyph at all. There simply is no assigned character for them.
A good generator handles that honestly rather than faking it. This one leaves s and x at their normal lowercase size instead of substituting a wrong-looking box or a random lookalike. In practice that reads fine, because a lowercase s already sits close to small-cap height. The word caps comes out as ᴄᴀᴘs and still looks consistent. The word six becomes sɪx, which is correct, not a bug. If you ever paste those words and notice the s or x looks slightly different, now you know why.
One more gap worth flagging: the small-cap Q is the rarer character ꞯ (U+A7AF), which some older fonts may not carry. On most current systems it renders fine, but a very old device might show a fallback box for that single letter.
How I actually use it
I keep a couple of bios that I treat as design surfaces, and small caps are the one accent I reach for again and again. The first time I tried it I expected to fight the platform, the way you do with most "fancy text" tricks. Instead I typed my tagline, hit copy, pasted it into the field, and it just held. No setting to flip, no styling to lose. I have since used it for a section label in a shared doc that gets exported to plain text, and the label stayed in small caps through the export, which a CSS version would never have survived. The trick that made it click for me was realizing I was moving characters, not formatting, so there was nothing for the destination to strip.
An accessibility caveat you should respect
Here is the cost, and it is real. Screen readers do not expect letters from Unicode's phonetic blocks to be standing in for ordinary text. Depending on the reader, your small-cap word might be read out oddly, spelled letter by letter in a confusing way, or skipped entirely. To a sighted reader ᴀᴜʀᴏʀᴀ is just "aurora" in a nice style; to someone using assistive technology it can be noise.
So treat small caps as decoration, never as load-bearing information. Do not put your real name, a phone number, a coupon code, or anything someone genuinely needs to read in small caps alone. Keep a plain-text version of any critical content. A subtle accent on a heading is fine. A whole paragraph of vital instructions in small caps is not. The same caution applies to most stylized Unicode text, including the glyphs from a broader fancy text generator or stacked superscript and subscript characters, which carry the same readability trade-off.
When small caps are the right call
Reach for small caps when you want a calm, deliberate accent in a field that only takes plain text: an Instagram or TikTok bio, a Discord status or channel name, an X post, a Twitch panel, a stream title. They survive plain-text fields because they are plain characters. They show the same on desktop, web, and mobile because the appearance is in the character, not in any app setting.
Reach for something else when the text must be machine-readable, searchable, or read aloud. In those cases keep it plain, and if you only need to flip between sentence case and title case, an uppercase and lowercase converter is the safer tool. Small caps are a finishing touch, not a foundation.
Type a word, watch it turn into small caps, copy it, and paste it wherever you like. Just remember it is Unicode doing the work, gaps and all.
Made by Toolora · Updated 2026-06-13