Why are Q and X not converted?

Because those characters do not exist. The small capitals in Unicode come from a phonetic alphabet that had no use for them, so they were never encoded. Substituting a lookalike from another script would change what the text says, and dropping the letter would change the word, so it is left as it is and flagged.

How is this different from just typing in capitals?

Full capitals read as shouting and are measurably slower to read, because word shapes disappear. Small capitals keep the text quiet while still marking it as distinct. That said, a screen reader gets nothing useful from either version of this trick.

Are these the same as the small caps in a word processor?

No. A word processor applies a real typographic feature from the font, which produces properly proportioned letterforms and stays searchable and readable to assistive software. This is a substitution for places that have no such feature at all.

Which of the three is best supported?

Monospace, comfortably. It is a complete alphabet with digits, it comes from the mathematical block that has been supported everywhere for years, and it degrades gracefully. The small capitals themselves are widely but less uniformly supported on older Android devices.

Small Caps Generator

Lowercase drawn as small capitals, plus monospace and outline.

Everything runs inside your browser. Your files never leave your device.

Input

Result

The result appears here as you type.

Ask about Small Caps Generator

Questions about what this tool does, which option to pick, or what it can and cannot handle.

The question you type here is sent to an AI provider to be answered — your files and whatever you put in the tool above are not, and the assistant cannot see them. Answers are generated and can be wrong. The tool itself is not guessing: it runs deterministic code on your device.

About the Small Caps Generator

In real typography, small capitals are a separate set of letterforms cut to the height of a lowercase x, with the proportions adjusted so they do not look like shrunken capitals. They are used for abbreviations inside running text, for the opening words of a chapter, and for names in some academic styles. A proper typeface either contains them or it does not.

What this page produces is a different thing wearing the same name, and it is worth being straight about that. The characters here are borrowed from the International Phonetic Alphabet extensions, where they were encoded to represent particular speech sounds rather than to be a typographic style. They happen to be drawn as small capitals, so they serve the purpose.

Two letters are missing entirely. Unicode never encoded a small-capital Q or a small-capital X in that range, because no phonetic transcription needed them. Nothing can be substituted without changing the letter, so those two come through as ordinary lowercase and the result says so. A word containing either will look uneven, which is a real limitation rather than something to work around.

Monospace and double-struck alphabets are offered alongside, since they are wanted for similar reasons — a name that needs to look deliberate in a field with no formatting. Monospace has the full set of letters and digits and is the most reliably supported alphabet in this whole family.

The usual caveats apply: assistive software does not read any of it as text, and no search will match it.

How to use it

1Type the words you want set in small capitals.
2Look at the result for a Q or an X — those two letters have no small-capital form and stay lowercase.
3Try the monospace row if you need digits as well as letters; small caps covers letters only.
4Copy the row you want with the button beside it.
5Keep it to short runs. It gets hard to read at paragraph length.

Questions

Why are Q and X not converted?: Because those characters do not exist. The small capitals in Unicode come from a phonetic alphabet that had no use for them, so they were never encoded. Substituting a lookalike from another script would change what the text says, and dropping the letter would change the word, so it is left as it is and flagged.
How is this different from just typing in capitals?: Full capitals read as shouting and are measurably slower to read, because word shapes disappear. Small capitals keep the text quiet while still marking it as distinct. That said, a screen reader gets nothing useful from either version of this trick.
Are these the same as the small caps in a word processor?: No. A word processor applies a real typographic feature from the font, which produces properly proportioned letterforms and stays searchable and readable to assistive software. This is a substitution for places that have no such feature at all.
Which of the three is best supported?: Monospace, comfortably. It is a complete alphabet with digits, it comes from the mathematical block that has been supported everywhere for years, and it degrades gracefully. The small capitals themselves are widely but less uniformly supported on older Android devices.