Discord Small Text Generator
Discord small text comes in two forms: subtext built with a special prefix, and Unicode characters that look like tiny letters. They behave differently. This guide covers all four styles in the generator, where each one works, and why some letters refuse to shrink.
Subtext versus Unicode look-alikes
Discord subtext is a real formatting feature. A line that starts with `-#` and a space renders smaller than normal message text. It is still your normal letters, just displayed at a smaller size by Discord.
Small caps, superscript, and subscript are not formatting. They are separate Unicode characters that happen to look like small letters. Discord sees them as plain text. That means they work in more places, but they also depend on the font and device that renders them.
Neither option is a custom font. Discord does not let you load a font into chat. The only built-in small text is subtext.
Discord subtext with the -# prefix
Put `-# ` at the very start of a line, followed by a space, and Discord renders that line as subtext. The prefix must be at the start. Leading spaces before the `-#` usually stop it from working, and a missing space after it can leave the marker visible.
Each line needs its own prefix. If you paste a paragraph, only the lines that begin with `-#` become small. Blank lines can stay blank. The generator prefixes every non-empty line and leaves empty lines alone so paragraph spacing survives.
Subtext works in messages and forum posts. It does not change your display name, nickname, bio, or username. It is a message style, not a profile style.
Unicode small caps
Small caps replace each letter with a Unicode character that looks like a small capital. The text stays readable as words, but it has an even, compact look. It is popular for labels, status lines, and aesthetic bios.
Uppercase and lowercase input both map to the small-cap glyphs in this tool, so `HELLO` and `hello` produce the same visual result. Punctuation and spaces pass through unchanged. Some fonts render the small-cap letters with slightly uneven heights, which is normal for Unicode look-alikes.
The letter Q uses a rare small-cap glyph that some older devices may not have. If the Q in your text shows as a box, try a different word or use normal text for that part.
Superscript and subscript
Superscript characters sit above the normal baseline, like the exponent in a math formula. Subscript characters sit below it, like the numbers in a chemical formula. Both are useful for short labels, version numbers, and playful formatting.
Coverage is partial. Superscript has forms for most letters and all digits, but some letters have no common superscript character and stay normal. Subscript is more limited: letters such as b, c, d, f, g, q, w, y, and z have no common subscript form, so they remain full size.
That mixed result is not a bug. Unicode simply does not include a subscript version of every letter. If the output looks uneven, use the style on a word that avoids the missing letters, or switch to small caps.
Worked examples
Start with the line `Server update at 8 PM`. Here is what each style produces.
Subtext: -# Server update at 8 PM Small caps: ꜱᴇʀᴠᴇʀ ᴜᴘᴅᴀᴛᴇ ᴀᴛ 8 ᴘᴍ Superscript: ˢᵉʳᵛᵉʳ ᵘᵖᵈᵃᵗᵉ ᵃᵗ ⁸ ᵖᵐ Subscript: ₛₑᵣᵥₑᵣ ᵤₚdₐₜₑ ₐₜ ₈ ₚm
Reading the results
The subtext version is still ordinary text in the message. Copying it elsewhere keeps the `-#` markers, and a client that does not understand subtext will show them literally.
The small caps version reads as words because the letter shapes stay close to normal capitals. The superscript version is smaller and more decorative, and the subscript version has a few full-size letters where Unicode has no subscript glyph.
For a label such as `update`, subscript produces `ᵤₚdₐₜₑ`, with a normal d in the middle. That is expected. Use a different word if the mixed size bothers you.
Where each style works
Subtext works in messages and forum posts. It does not work in usernames, display names, nicknames, or bios. If you paste it into a name field, the `-#` appears as literal characters.
Unicode small caps, superscript, and subscript work almost anywhere plain text is accepted: messages, display names, server nicknames, bios, and many channel topics. Support depends on the field's character filter and the font used by the viewer.
Usernames are the exception. Discord handles only allow lowercase letters, numbers, underscores, and periods, so none of these Unicode styles can be used in an @handle. You can use them in the display name that appears next to the handle.
Server names and channel names have their own rules and may reject or normalize unusual characters. Test on a small server before changing a public name.
Readability and screen readers
Small text is harder to read for everyone, and it can be worse for people with low vision. Use it for secondary information, not for rules, warnings, or anything a member must understand to participate safely.
Screen readers may read Unicode small caps letter by letter, skip them, or pronounce them as different characters. Subtext is still normal text, but some readers announce the `-#` prefix or treat the line as a heading. Neither style is a reliable way to convey structure.
Do not use tiny text to hide content from moderation. It is still readable, and hiding rules or warnings in small text is a good way to confuse members.
Troubleshooting
If subtext does not render, check the start of the line. There should be no spaces before `-#`, and there should be one space after it. If the line is inside a code block, the marker will stay visible because code blocks do not apply markdown.
If you copy from a word processor, you may bring along smart quotes, non-breaking spaces, or a hyphen that is not the standard `-`. Retype the prefix in the Discord message box if the style refuses to apply.
If some letters in superscript or subscript stay full size, Unicode has no glyph for them. That is expected. Try small caps instead if you need a uniform look.
If a display name is rejected, remove the Unicode style and try a shorter string. Some filters reject characters that look like confusables, even when the same characters work in a message.
Practical ways to use small text
Subtext is a good fit for a secondary line under an announcement, such as a note about the timezone or a reminder to read the pinned message. It keeps the main text prominent without adding another paragraph.
Small caps work well for short labels in a bio, such as `interests` or `currently playing`. Superscript and subscript are better for playful accents and short words, not for a full paragraph.
Keep the effect intentional. A message that mixes normal text, subtext, small caps, and superscript in every line is harder to scan than one that uses a single style for a single purpose.
Explore more discord tools on Tolz.me.