Professional display names
Small caps read as clean and understated. LinkedIn headlines, Twitter bios, and resume headings use them for a structured look that normal mixed case cannot match.
Text tool
Small Caps Generator
Type any text below and get it in small capitals, built from the Phonetic Extensions block (U+1D00) and related ranges. Lowercase letters become miniature capitals; existing capitals stay as they are. Useful for clean, professional display text.
What small caps text actually is
Small caps text is not a font. It is a mix of Unicode characters drawn as miniature capitals. Unlike bold or script, there is no single tidy block for small caps — the letters are spread across the Phonetic Extensions block (U+1D00–U+1D2B) and several nearby ranges. Lowercase a maps to U+1D00, b to U+0299, c to U+1D04, d to U+1D05, and so on. Uppercase letters are already capitals, so they pass through unchanged. When you paste ʜᴇʟʟᴏ into a headline, the app sees code points U+029C, U+1D07, U+029F, U+029F, U+1D0F and renders each as a small capital glyph. The catch is coverage: a few letters (notably x) have no dedicated small-cap code point, so the closest visual match is used, and some letters come from IPA and phonetic ranges that render slightly differently across fonts.
What small caps are useful for
Section headers in plain text
Email signatures, README files, and plain-text notes use small caps for section labels. The miniature capitals create hierarchy without bold or color.
Branding and wordmarks
Small caps approximate the all-caps logotype look used by fashion and lifestyle brands. Pasting them into a bio or caption gives that structured feel without an image.
Compact, readable styling
Small caps keep the x-height of normal text, so lines stay compact and readable. They do not blow up line height the way fullwidth or circled styles do.
Scattered code points and the coverage gaps
Small caps are unusual because no single Unicode block defines them. The letters are pulled from the Phonetic Extensions block (U+1D00–U+1D2B), the IPA Extensions block, and a handful of Latin Extended ranges. a is U+1D00, b is U+0299, c is U+1D04, working through to z at U+1D22. The good news: most of these sit in the Basic Multilingual Plane and cost 1 UTF-16 unit each, so a small-caps bio uses roughly the same unit budget as plain ASCII. The catch is consistency. Because the letters come from different blocks designed for phonetics, not display, the glyph weights and shapes vary slightly between fonts. Some letters have no dedicated small-cap code point — x falls back to a plain x, and a couple of others use the closest visual match. Most modern devices render the set, but the look is less uniform than bold or script.
Practical notes before you paste
- Small caps are spread across multiple Unicode blocks, so glyph weights vary slightly between fonts. Test on a second device.
- Uppercase letters stay uppercase — small caps only change the lowercase ones. Type in lowercase to get the full effect.
- The letter x has no dedicated small-cap code point. It falls back to a plain x, which can look out of place in all-small-caps text.
- Small caps cost 1 UTF-16 unit each, so a small-caps bio fits roughly the same character budget as plain ASCII.
- Small caps render on most modern devices, but older systems may show a few letters as boxes if the Phonetic Extensions block is missing.
- Don't use small caps inside hashtags or @mentions — the special characters break linking and discoverability.
- Small caps work well in email subject lines and signatures, but spam filters sometimes score unusual Unicode higher.
- Plain ASCII ranks better in search. Use small caps for display (bios, captions, headings), not for SEO-critical text.
Platform compatibility
Small caps render on iOS, Android, Windows, macOS, and every major browser, though glyph weights vary because the letters come from phonetic blocks rather than a dedicated display block. TikTok accepts them in display names (30-char limit), bios (80 UTF-16 units), video captions, and comments. Instagram accepts them in the name field (30 chars), bio (150 chars), captions, and comments. Discord accepts them in display names (32 chars) and per-server nicknames. Twitter/X accepts them in display names (50 chars) and tweets. LinkedIn accepts them in headlines and the name field, where the clean look is popular. Steam persona names (3–32 chars) render small caps correctly. The main place they fail is @username and @handle fields, which only allow ASCII. A few older Android builds render most letters but fall back to plain text for the less common code points.
Common questions about small caps Unicode text
Are small caps a font?
No. Each letter is a separate Unicode code point (ʜ is U+029C) that renders as a miniature capital by the system font. You are pasting different characters, not applying a font or formatting.
Why does my small caps text look slightly inconsistent?
Small caps are spread across the Phonetic Extensions block (U+1D00–U+1D2B) and several nearby ranges, not one tidy block. Because the code points were designed for phonetics, glyph weights and shapes vary between fonts.
Why is the letter x not a small cap?
There is no dedicated small-cap code point for x in Unicode. The closest visual match is a plain x, so that is what gets used. A couple of other letters also rely on the nearest available character.
Do small caps work in LinkedIn headlines?
Yes. LinkedIn accepts the characters in the name field and headline, and the clean, structured look is popular there. Small caps cost 1 UTF-16 unit each, so they fit the field limits comfortably.
Why do some small caps render as boxes on older devices?
Some older Android builds and budget Windows machines ship system fonts that do not cover the full Phonetic Extensions block. Update the OS, switch to a font like Noto Sans, or fall back to plain text for those users.
Will small caps hurt my SEO?
Yes, if they sit in page titles, headings, or any text you want indexed. Search engines normalize Unicode, but styled characters may not be weighted the same. Use small caps for display, not for SEO-critical content.