About TextLib
A copy-paste library for Unicode characters, and the people and sources behind it
TextLib is a reference and copy-paste library for Unicode characters — symbols, emoji, kaomoji, decorative alphabets — plus a set of small text tools that transform what you type into those characters.
The site exists because the useful parts of Unicode are scattered. The standard itself is a set of code charts written for implementers, not for someone who wants a heart that renders the same on an iPhone and a Windows laptop. Most sites that fill that gap give you a wall of glyphs with no indication of what each one is called, what its code point is, or where it will silently fail. We try to give you all three.
Where the character data comes from
Every character on this site is real Unicode text, never an image. Names and code points follow the Unicode Standard — so "★" is listed as Black Star, U+2605, because that is what the standard calls it, even though most people search for "star symbol".
The groupings are ours, and they are editorial rather than technical. Unicode organises characters into blocks by historical and technical accident: the arrow you want may sit in Arrows, Supplemental Arrows-A, Supplemental Arrows-B, Miscellaneous Symbols and Arrows, or Dingbats. Nobody searching for an arrow thinks in blocks. So our collections are grouped by what people actually look for, and each page states the code point so you can always trace a character back to the standard.
Why the tools run in your browser
The text tools — case conversion, the font and style generators, the counters — run entirely in your browser. There is no API call, no upload, and no server-side processing of anything you type. You can verify this yourself: open your browser's network tab, type into any tool, and watch that no request is made.
This is a deliberate design choice rather than a privacy slogan. Text people run through a converter is often a draft, a password-adjacent string, or something not meant to be published yet. Sending it to a server would create a log we have no business holding. Keeping the work client-side means there is nothing to log, nothing to leak, and the tool keeps working if our server is down.
The practical trade-off: the transforms are limited to what fits in a browser bundle, and very large inputs are bounded by your device rather than by us.
What TextLib is not
It is not a font site. Nothing here installs a typeface or changes how your device renders text. The "fonts" in our generators are Unicode characters that happen to look like styled letters — Mathematical Bold Capital A (U+1D400) instead of a bold A. That distinction matters, because it is exactly why styled text works in an Instagram bio but is rejected by some username fields, mangled by screen readers, and ignored by search inside a document.
It is also not an emoji encyclopaedia. Where a character has genuine cultural or historical background we write it up, but for most glyphs the honest answer is that it exists, here is what it is called, and here is where it will and will not render.
Accuracy, and how to report an error
Unicode support differs by operating system, by application, and by font. A character that renders correctly on your machine may show as a tofu box (□) on someone else's, and that is a property of their font coverage rather than of the character. Where we know a glyph is unreliable on a common platform we say so on the page.
We get things wrong. If a character is mislabelled, a code point is incorrect, or something renders as an empty box where we claim it works, tell us at [email protected] and we will fix the page. Corrections are the most useful message we receive.
Who runs TextLib
TextLib is operated by Luis Riedhammer, Föhrenweg 2, 58638 Iserlohn, Germany. Full legal details are in the imprint, and email reaches us at [email protected].
The site is free to use and carries no account system — there is nothing to register for and no user data to store. See the privacy policy for what is and is not collected.