About TextGlyphs
TextGlyphs is an independent reference and tool for text symbols — the copy-and-paste Unicode glyphs, small text, cursed text and aesthetic combos people use to decorate messages, bios and posts on Instagram, TikTok, Discord and anywhere else that accepts plain text. This page explains who we are, how we test what we publish, and the standards we hold ourselves to.
Page last reviewed: 15 August 2026. The render-support notes were last re-tested against live apps in July 2026, and are re-checked at each major platform update.
What TextGlyphs is
TextGlyphs is a browser-based instrument for decorating plain text. Everything on the site is built around one idea: the marks you copy are real Unicode characters, not pictures, so they survive a paste into almost anywhere that accepts text — a caption, a username, a chat message or a profile bio. We curate those characters into tappable sets, add small-text and cursed-text transformers, and document where each glyph actually renders.
We are a tool-first site, not a link dump. Where most symbol sites paste thousands of characters onto one endless page, we group them by use, explain what they are, and show honestly where they break.
The site published its first pages in July 2026 and is actively maintained; every change we ship to the tools is written up in our patch notes, so you can see exactly what moved and when. If you want the short version of how copying and pasting symbols works in practice, start with the text symbols FAQ.
Who writes this
Content on TextGlyphs is produced by the TextGlyphs editorial team — an organisation, not a single named author. We write about Unicode, typography and platform text support. When a claim depends on a person’s individual credentials we say so; we never invent an author, a photograph or a qualification to look more authoritative than we are.
Our expertise is practical rather than academic: we work with the Unicode character set every day, and we test glyphs on real apps and devices before we tell you they work.
How we verify render support
The single most useful thing a symbol site can tell you is where a character actually shows up and where it arrives as an empty box. That answer is not a promise — it changes with every operating-system and app update — so we treat it as evidence, not opinion:
- We paste each set into current builds of the platforms people ask about most — Instagram, TikTok, Discord, iOS and Android — and record what we see.
- Support notes carry the month they were checked, because a glyph that works today can regress after an update.
- Where a character is standardised we cite the source of record, the Unicode Consortium at unicode.org, rather than paraphrasing from memory.
How we document a glyph
Every character we publish is identified by its Unicode code point, its official character name and the Unicode version that introduced it — not by a nickname we made up. That is what lets you verify a glyph against the official Unicode charts instead of taking our word for it.
Here is the same record we keep internally, for six characters that appear across the site:swipe the table →
| Glyph | Code point | Official Unicode name | Block | Added in | Why it matters |
|---|---|---|---|---|---|
| ★ | U+2605 |
BLACK STAR | Miscellaneous Symbols | Unicode 1.1 | Old and near-universal — safe almost anywhere text is accepted. |
| ♡ | U+2661 |
WHITE HEART SUIT | Miscellaneous Symbols | Unicode 1.1 | A text character, not the ❤️ emoji — it inherits your font’s colour instead of rendering as a picture. |
| ᴀ | U+1D00 |
LATIN LETTER SMALL CAPITAL A | Phonetic Extensions | Unicode 4.0 | Small caps is the one “fancy text” style that survives NFKC normalisation, so it holds up in fields that quietly rewrite your input. |
| ⠀ | U+2800 |
BRAILLE PATTERN BLANK | Braille Patterns | Unicode 3.0 | Renders as a blank but is not a space, which is why it survives forms that strip or collapse ordinary spaces. |
| ㅤ | U+3164 |
HANGUL FILLER | Hangul Compatibility Jamo | Unicode 1.1 | The other popular “invisible” character — but NFKC normalisation collapses it, so it fails exactly where U+2800 holds. |
| a̶ | U+0336 |
COMBINING LONG STROKE OVERLAY | Combining Diacritical Marks | Unicode 1.1 | A combining mark, shown here attached to a plain a — it has no shape of its own, and it is the mechanism behind strikethrough and stacked “cursed” text. |
Two of those rows explain a difference most symbol sites never mention: U+2800 and U+3164 both look like nothing on screen, yet they behave differently the moment a platform normalises your input. It is the sort of detail you only find by pasting them into real forms, which is why our small text generator and cursed text generator are built on characters we have checked rather than on whatever looked good in a chart.
Editorial standards
- Real characters only. Every glyph we publish is a genuine, copyable Unicode code point. We never show a symbol as an image you cannot copy.
- No fabricated numbers. We do not invent usage statistics, ratings or copy counts. Any counter you see reflects activity on your own device.
- Honest about limits. If a glyph is unreliable on a platform, we say so instead of hiding it.
- Corrections welcome. Text support shifts constantly. If something has stopped rendering where we said it would, tell us on the contact page and we will re-test and update the note. We answer editorial mail within five business days.
Independence and non-affiliation
TextGlyphs is an independent site. The glyphs and symbols we document are part of the public Unicode standard and are not owned by us. Platform names such as Instagram, TikTok, Discord and others are trademarks of their respective owners; TextGlyphs is not affiliated with, endorsed by, or sponsored by any of them, and we reference them only to describe where characters do and do not display.
Your text stays yours
The instrument runs entirely in your browser. Text you type, patches you save and the copies you make are processed on your own device — we do not need an account and your compositions are not uploaded to build these tools. For the full detail, including the third-party services the site relies on, see our privacy policy; the rules for using the site are in our terms of service. Anything else — a correction, a glyph that stopped working, a request — reaches us through contact.