Text Faces

What text faces are built from

Text faces, also called kaomoji, are assembled from characters that were never intended for the purpose. A typical face draws on Japanese kana for the eyes or mouth, mathematical operators for the arms, and ordinary punctuation for the structure.

This is why they cannot be typed directly on any keyboard and why copying is the standard way to use them. It is also why they are so expressive - the available character set is enormous compared with the handful of symbols a Western emoticon uses.

Some faces additionally use combining marks, the same mechanism behind cursed text, to place elements above or below the base characters. The lenny face is the best-known example, using combining marks to position its eyebrows.

Those combining marks have a practical consequence: a face that appears to be eight characters may be twelve or more codepoints, which matters wherever a character limit applies.

Character limits and rendering

In Discord, faces count against field limits by codepoint rather than by visual width. A face with combining marks can therefore cost noticeably more than it appears to, and a 32 character nickname can be exhausted by a face plus a short name.

Many faces also use fullwidth characters, which occupy roughly double the horizontal space of a Latin letter. This means a face can overflow the visible area of a nickname or channel name well before the character limit is reached - the visual constraint bites first.

Rendering depends on font coverage across several blocks. Mainstream systems handle this fine, but minimal font installations produce fallback boxes for parts of the face, which usually looks worse than no face at all.

Faces built from combining marks share the overlap problem of cursed text: the marks are drawn outside the normal line box and can overlap adjacent lines. In a dense member list this is why some servers discourage them.

The backslash rule and where faces fit

The most frequent complaint about text faces on Discord is that an arm goes missing. This is markdown behaving as designed: the backslash is an escape character, so Discord removes it and displays whatever follows literally.

Doubling the backslash fixes it - Discord consumes the first and shows the second. This applies only where markdown is parsed, meaning message bodies. In nicknames and bios, which do not parse markdown, the single backslash works fine, which is why the same face can behave differently in different fields.

Beyond the mechanics, faces suit conversational use better than persistent fields. A face at the end of a message conveys tone without the visual weight of an emoji, and it scrolls away.

In persistent fields - nicknames, channel names, server names - the width and overlap costs accumulate and affect other people's view of the server, which is why simpler faces without combining marks are the safer choice there.

Tips for using text faces

• Symbols and emoticons are ordinary unicode characters, which means they render everywhere text renders: Discord, browsers, emails, spreadsheets and mobile keyboards.
• Symbols with spacing glyphs (such as dingbats or decorative bullets) can affect text alignment in code blocks and tables, so test a symbol in context before committing.
• Using a symbol as a bullet or divider is a quick way to structure long Discord messages without markdown headings, which are not supported in normal chat.
• On mobile, unicode symbols often live one or two keyboard pages deep. Copying from a directory like this one is faster than hunting through emoji pickers.

These tips apply no matter whether you are decorating a personal profile, organising a server or publishing a guide. The principle stays the same: start with clean, readable content, then add styling in small, reversible steps so your text keeps working everywhere it is pasted.

How to get started with text faces

1. Find the symbol you need. Browse the page and click any symbol to copy it. Symbols are grouped by theme, so start with the group that matches your purpose.
2. Paste into context. Insert the symbol where it will be used - a nickname, a channel name, a bio, a message or a document. Symbols render inline with the surrounding text.
3. Combine sparingly. Use one or two symbols per line to keep things clean. Overusing decorative characters makes text harder to read and can trigger moderation filters on some servers.

The whole workflow takes under a minute for most people. Because everything runs locally in the browser, there is no account to create, no upload step and no waiting for a server to respond. The results are plain text that you can paste anywhere and adjust later.

Common mistakes and how to avoid them

• Retyping a face instead of copying it. The characters come from several unicode blocks and none of them are on a standard keyboard.
• Pasting a face containing a backslash into a Discord message without doubling it. Discord's markdown eats the backslash and the face loses a limb.
• Underestimating the character cost. Faces using combining marks count as more than one character each, so a single face can consume a large share of a nickname limit.
• Using tall faces with combining marks in a member list, where they overlap neighbouring entries and are often treated as disruptive.

Frequently asked questions

Text Faces | key points to remember

Text Faces is part of a larger collection of free tools on this site. The related tools below cover adjacent topics, and everything runs directly in your browser - no accounts, no installs, no data leaving your device.

If a technique on this page does not behave as expected, the quickest fixes are: check the character limit of the field you are editing, make sure the text is not inside a code block, and preview it in the exact place where it will be used. Most rendering quirks come from one of those three sources, and most are resolved in seconds.

Related keywords: text faces, text face copy paste, lenny face, shrug text face, cute text faces, ascii faces, Symbols & Emoticons.