Can you get small caps in Cyrillic, Greek or Chinese? No — and here is why
Short answer: no, and no tool can do it. Unicode small capitals exist only for Latin letters. There is no Cyrillic, Greek, Arabic, Hebrew or CJK equivalent to convert into, so any generator claiming otherwise is doing something else.
This comes up constantly from people running servers or accounts in Russian, Ukrainian, Greek and Serbian, and the honest answer is worth more than a workaround that produces mojibake.
Why the gap exists
Small capitals were not added to Unicode as a typographic feature. They were added as phonetic notation — IPA symbols for linguists. Twenty-two of the twenty-six Latin small caps come from the Phonetic Extensions and IPA Extensions blocks.
The International Phonetic Alphabet is Latin-based. Its small capital letters denote specific sounds — ɢ a voiced uvular plosive, ɪ a near-close near-front unrounded vowel. There was never a reason to encode a small capital Д, because no phonetic notation needed one.
So the set stops at Latin. Not because anyone decided other scripts do not deserve it, but because the set was never about scripts in the first place. It is a side effect of the original purpose — the same reason Latin small caps has no X.
What does not work
Transliteration. Converting Привет to ᴘʀɪᴠᴇᴛ changes the language, not the styling. For a server or account name this usually reads as worse than plain Cyrillic, not better.
Look-alike substitution. Some tools map Cyrillic letters to visually similar Latin small caps. The result looks approximately right and is broken underneath: the text no longer matches searches in its own language, and screen readers announce it as the wrong language entirely. This is the same family of problem as homoglyph spoofing, just self-inflicted.
Waiting for it. Adding a full small-capital Cyrillic set would mean encoding dozens of characters whose only use is decorative, which is not how Unicode additions get justified.
What does work
Mix scripts deliberately. Use Latin small caps for the decorative parts that are not words in your language — brackets, rank labels, menu chrome, section dividers — and leave the actual language in normal letters. This is what most multilingual servers land on:
‹ ᴠɪᴘ › АлександрThe label is decoration and can be Latin. The name is a name and stays readable.
Use styles that are script-independent. Some effects apply to any script because they are combining marks or spacing rather than character substitution:
| Style | Works on non-Latin? |
|---|---|
| Strikethrough (s̶t̶r̶i̶k̶e̶) | ✅ Yes |
| Underline (u̲n̲d̲e̲r̲) | ✅ Yes |
| Wide spacing | ✅ Yes |
| Bracket wrapping | ✅ Yes |
| Small caps, bold, script, fraktur | ❌ Latin only |
The reason for the split: strikethrough and underline are combining marks, which attach to whatever base character is already there — any script, no substitution. Wide spacing inserts spaces and bracket wrapping surrounds the text, so both leave your letters untouched. Small caps, bold, script and fraktur all work by replacing each letter with a different code point, and outside Latin there is nothing to replace it with.
The first four are usually the honest answer for non-Latin text: they add visual treatment without replacing your letters with different letters.
Full-width for CJK. Full-width Latin (Ｆｕｌｌ) is a special case worth knowing — it exists precisely so Latin letters can align with CJK characters in fixed-width grids. If you are mixing English into Japanese or Chinese text, that is the block built for it.
The short version
If the text is in a non-Latin script, do not look for a small caps converter — there is nothing to find. Decorate around the text with brackets, spacing or combining marks, and leave the letters themselves alone.
If a tool does offer “Cyrillic small caps,” check what it actually emits with codePointAt. It is substituting look-alikes from another script, and the cost of that shows up in search and accessibility rather than in the preview.