Contact TextGlyphs
You can reach the TextGlyphs editorial team at contact@textglyphs.com. That single address handles everything: a text symbol that stopped rendering in Instagram, TikTok or Discord, a correction to something we published, a content removal request, or a copyright claim. We read every message and reply within five business days.
Last updated: 13 August 2026
Email us
There is one inbox and no contact form, because a form would give you no record of what you sent. Write to contact@textglyphs.com and you keep the sent copy.
- Response time: within five business days. Render reports and copyright claims are handled first.
- Language: English is best. We will do our best with other languages, but a reply may take longer.
- No account needed: the site has no logins, so there is nothing to verify before you write — see our privacy policy for what we do and do not keep.
What to include, by type of message
The single biggest reason a report stalls is that we cannot reproduce it. Character problems are specific to a device, an app version and a font, so the details below are what actually let us act on the first reply rather than the third.
| Your message is about | Put this in the subject | Include in the body |
|---|---|---|
| A symbol that shows as an empty box | Render report |
The page URL, the glyph pasted as text (not a screenshot), the app or site you pasted it into, and your device and OS version. |
| A factual correction | Correction |
The page URL, the sentence you are challenging, and what it should say — a link to the Unicode charts settles most of these instantly. |
| A removal request | Removal request |
The exact URL, the passage or file, and why it should come down. |
| A copyright claim | Copyright claim |
The work you own, where it appears on this site, proof you hold the rights, and how to contact you. |
| Anything else | A plain description | Whatever context you have. There is no wrong way to send this one. |
Reporting a glyph that no longer renders
This is the most valuable email we receive. Our support notes are dated because they expire: a character that displayed correctly last month can turn into an empty box after a single operating-system update changes which fonts ship by default. We cannot test every build of every app, so a report from a device we do not have is genuine evidence.
Paste the character itself into your email as text. A screenshot tells us the glyph failed on your screen but not which code point it was, and two visually similar symbols often come from different Unicode blocks with completely different support. If you can tell us the code point — the U+xxxx value shown next to each character on the site — that removes the last of the guesswork. When we confirm a regression, the support note is re-tested and updated, and the change is listed in our patch notes.
Corrections and fact challenges
If we have published something inaccurate about a character, its name, its Unicode version or where it works, tell us and we will fix it. We do not quietly edit a page and pretend the error never happened: a substantive correction changes the “last reviewed” date on the page, and the standards we hold ourselves to are set out on our about page. Common questions about copying and pasting are answered first in our text symbols FAQ, which is worth a look before you write.
Content removal requests
Write to the address above with the exact URL and the passage in question, and say plainly what you want removed and why. We assess every request on its merits and reply within the same five business days, whether the answer is yes or no.
One thing to know before you write: the individual characters on this site are part of the public Unicode standard. Nobody owns U+2605 or the letter A, so a request to remove a standard character as such is not something we can act on. Requests about text we wrote, an image we made, or material a third party contributed are a different matter and are taken seriously.
Copyright claims
If you believe material published on TextGlyphs infringes your copyright, email contact@textglyphs.com with the subject Copyright claim. Please identify the work you own, the specific URL where it appears, the basis for your claim to the rights, and a way to reach you. Include a statement that you are acting in good faith and that the information you have given is accurate.
We act on valid claims by removing or amending the material rather than by arguing about it. If we think a claim is mistaken — most often because the item is a Unicode character or a fact rather than a creative work — we will say so and explain why. Your use of the site is governed by our terms of service.
Who operates TextGlyphs
TextGlyphs is an independent website operated by a private individual, publishing under the editorial identity TextGlyphs editorial team. It is not a company, and it is not affiliated with, endorsed by or sponsored by Instagram, TikTok, Discord, Apple, Google, the Unicode Consortium or any other organisation whose name appears on the site. Platform names are the trademarks of their respective owners and are used only to describe where characters do and do not display.
We do not publish under an invented human byline, a stock photograph or a qualification we do not hold. Correspondence is answered by the same person who writes and tests the pages.
What we cannot help with
- Account problems on other platforms. If a username or bio was rejected, that is the platform’s rule, not ours — we have no access to your account anywhere.
- Recovering text you did not save. Everything the tools produce stays in your own browser and never reaches us, so there is no copy on our side to send you.
- Changing what Unicode contains. New characters are decided by the Unicode Consortium at unicode.org; we document the standard, we do not set it.
- Making a font appear on someone else’s device. Whether a glyph displays depends on the fonts installed there. We can tell you honestly where it works — and the TextGlyphs symbol library is built around characters with the widest support — but we cannot install anything for you.