How to Make Small Text in Discord (and Why It Is Not a Font Setting)

TL;DR: Discord has no font-size setting, so “small text” is done with Unicode characters that are permanently small — superscript letters like ᵗʰⁱˢ, small caps like ᴛʜɪꜱ, or subscript digits. You paste them as ordinary text. They render small on every device because they are different characters, not a style. The cost is real: they are hard to read, screen readers handle them poorly, and not every letter has a small equivalent.

Why there is no font size control

Discord’s message composer supports a fixed set of Markdown: bold, italic, underline, strikethrough, code blocks, spoilers, and headings. There is no size parameter, and there is no client setting that changes how a message’s text is rendered relative to other messages.

That is a deliberate constraint. A chat client where every message can set its own size becomes unreadable quickly, and moderation becomes harder. So the platform omits the feature entirely rather than exposing it with limits.

What this means practically: any “small text” you see in Discord is not styling. It is different Unicode characters that happen to render at a smaller size in the same font, so the effect travels with the text into any app.

The three Unicode families that look small

Three character sets produce the effect, and they look distinctly different.

Superscript — ᵃ ᵇ ᶜ ᵈ ᵉ. Raised and smaller. This is the most commonly used for the “small text” look, and the closest to what people mean.

Subscript — ₐ ₑ ₕ ᵢ ⱼ. Lowered and smaller. Fewer letters exist, and some are missing entirely, which makes full words impossible.

Small caps — ᴀ ʙ ᴄ ᴅ ᴇ. Uppercase letterforms at lowercase height. Reads more like a stylistic choice than a size change, and is more legible than superscript at length.

Each is a genuine part of Unicode with legitimate uses — mathematics, phonetics, chemistry notation — which is why they exist and why they are stable across platforms.

The coverage problem

Not every letter has a small equivalent, and this is the limitation that ruins most attempts.

Superscript coverage is decent for lowercase but incomplete: q, w, and several others have no true superscript form, and capitals are patchy. Subscript is worse — the set is small enough that most words cannot be written at all.

When a character is missing, the generator either substitutes a normal letter, which looks broken mid-word, or skips it, which changes the spelling. Neither is acceptable in a message someone needs to read, which is why the effect works best on short phrases and fails on sentences.

Digits are the exception: superscript ⁰¹²³⁴⁵⁶⁷⁸⁹ and subscript ₀₁₂₃₄₅₆₇₈₉ are complete, so numbers always convert cleanly. That is why timestamps and counts are the most reliable use of the trick.

Where it works in Discord

The characters are plain text, so they render anywhere text renders: message content, nicknames on a server you control, channel topics, and role names.

Two places reject them. Channel names are normalised — Discord strips or replaces non-standard characters, so a superscript channel name usually collapses to plain letters or fails to save. And usernames have a restricted character set, so the trick does not survive there either.

Embedded content is a third case: text inside a link preview, an embed title, or a bot-generated field renders as the bot sends it, so the characters work only if the bot received them.

Markdown combinations still apply. Bold and italic work on these characters, since they are ordinary text. Code blocks are the exception worth knowing: inside backticks the characters display in a monospace font and the size difference largely disappears.

Readability, honestly

The reason this effect is popular is that it looks distinctive. The reason it is often a bad idea is that it is substantially harder to read, and the difficulty is not evenly distributed.

Superscript text at small sizes is roughly half the x-height of surrounding text. On a phone, at default zoom, that is below comfortable reading size. For anyone with low vision, a screen reader, or a translation tool, the text may be read character by character or skipped entirely, because assistive technology does not treat ᵗʰⁱˢ as the word “this”.

Search is affected too. Discord’s search will not match a superscript phrase against a normal one, so a message written this way becomes effectively unsearchable.

The reasonable use is decorative: a short tag in a nickname, a small label in a topic, a countdown in a message. The unreasonable use is a full sentence that someone needs to actually read, which is where most people try it and then regret it.

How to produce it without hunting characters

Typing these by hand means memorising code points, which nobody does. The practical route is a converter that maps your input to the equivalent Unicode characters.

Two checks are worth doing with any generator. First, does it mark the characters it could not convert, or does it silently substitute plain letters — the difference decides whether the output is usable. Second, does it handle spaces? Some do, using a narrow space or a normal space that renders at full size, which makes the phrase look inconsistent.

If you want the small-text styles alongside the other Unicode alphabets people use for bios and captions, a fancy text generator covers the superscript, small caps, and stylised sets in one place, which is faster than assembling them character by character.

The short version

Discord has no font size control. Small text is Unicode: superscript for the most convincing effect, small caps for legibility, subscripts for digits only. Coverage is incomplete, channel names and usernames reject it, and it is bad for readability and search — so use it decoratively and keep it short.