Unicode Text Editor · Unicode 17 Character Library

This editor lets you style plain text wherever formatting is normally not possible.

Instagram, Facebook, X — bios, posts, captions
WhatsApp & Telegram — messages, group names, status texts
SMS & messengers — emphasis without formatting tools
Website headers & titles — standout headlines
Contacts on your phone — structured names & notes

And much more—explore what works for you.

FONT

Select a font and write as you normally would. You can also format individual letters or words independently.

BULLETS

Add bullets at the beginning of a line to create lists. Bullets are applied to all selected lines, or to a single line if your caret is placed inside that line. Clicking the same bullet again removes it. Clicking a different bullet replaces the current one. You can also remove bullets manually using Backspace.

TEXT EDITOR

Write just like in any standard text editor. You can insert glyphs and emojis at any position in the text.

COPY

Copy the entire text content and use it anywhere you like. Try it — even in places where you would never expect styled text to work.

CLEAR

Clear the entire content of the text field.

SAVE

Save your text and manage your templates. You can save, overwrite, rename, duplicate, and organize your entries as needed. This allows you to build your own collection of reusable text templates.

WRITE

Click the pen to edit the template in the text editor.

DUPLICATE

Duplicate the template

DELETE

Delete the template

WHATSAPP & TELEGRAM

Send the text directly to the WhatsApp or Telegram app installed on your device. This eliminates the need for manual copy & paste.

LIB

A comprehensive Unicode 17 library of characters, symbols and standardized emoji sequences.
Use PROOF to explore 60,734 curated entries: 59,332 verified single code points and 1,402 standardized sequences assessed from verified component coverage (see PROOF).
Or switch to GLOBAL to explore the library’s full display-oriented Unicode 17 catalog.

Characters are displayed using system fonts or self-hosted fonts, depending on the selected mode. Font coverage varies by character and platform. The hosted fonts are used under their respective open-source licenses; the applicable license terms must be respected when fonts are downloaded or embedded elsewhere.

GLYPHBOARD

In PROOF mode, the Glyphboard contains 59,332 single-code-point entries verified against the default system fonts of four documented reference environments, plus 1,402 standardized sequences assessed from verified component coverage. This describes these four documented reference collections and is not a guarantee for every device, app or later system version. Hovering over an entry displays a small info tooltip with relevant character details.

SEARCH

Search by keywords to display related characters, symbols and emoji.

CATEGORIES

Select a main group and a sub-group to explore the associated characters, symbols and emoji.

FAV

Collect your favorite characters, symbols and emoji. Add items from the library with a single click. You can remove individual characters from the Favorites board at any time.

ZOOM ±

Adjust the glyph size for optimal visibility.

GlyphType™ does not profile users, follow them across the web or monetize their attention. There are no behavioral fingerprints, advertising profiles or dark patterns. What you type stays in your browser and is never transmitted to GlyphType servers. Text is passed to another application only when you explicitly use a sharing function. A non-identifying aggregate action counter is currently used to understand general usage; it does not record text content, search terms or personal identifiers.

This approach is rare today — not because it is difficult, but because it requires restraint. Most platforms trade user data for growth. We deliberately chose not to.

Unicode characters are text, not images.
Characters are stored and transmitted as Unicode-encoded text. Their identity is defined by one or more Unicode code points; for example, U+1F600 identifies this emoji: 😀. A glyph is the visible form produced by a font and rendering system.

Whether a character becomes visible depends on the fonts and rendering system available on the receiving device. Missing font coverage usually produces an empty box or another missing-glyph shape, often called “tofu.” The replacement character � instead usually indicates that text could not be decoded correctly.

Because Unicode, fonts, and operating systems evolve over time, a character may render correctly on a modern device but fail on an older one — even though the same code point was sent.

In short: Just because a character is visible on your device does not mean it will work everywhere.

Not all characters in Unicode are meant to be mixed freely.

Some scripts (such as Arabic, Devanagari, or Bengali) use combining marks that are designed to work only with letters from the same script. These combinations follow Unicode and script-specific shaping rules and are normally rendered correctly by suitable fonts and text engines. Actual results may still vary with font and application support.

Other characters — for example decorative, mathematical or stylistic letters — do not belong to those writing systems. Some combinations are technically representable as Unicode sequences but may be linguistically inappropriate, visually unstable or poorly supported.

GlyphType blocks combinations known to be unreliable for the selected transformation.

This improves consistency and avoids known unstable constructions, but it cannot guarantee linguistic correctness or identical rendering in every application.

Unicode assigns code points to characters used by scripts, symbols and emoji and provides a common basis for interpreting encoded text across platforms, languages and systems. The current standard is Unicode Version 17.

Unicode strictly separates meaning from appearance: a code point defines what a character is — not how it looks. Visual rendering is provided by fonts and operating systems.

The Unicode system consists of clearly separated ranges. For web, messaging, and social media, only certain parts are relevant and visible. The breakdown below shows which parts are included in GlyphType and which are intentionally excluded.

The structural values below are deterministic and reproducible from the cited Unicode reference files (Blocks.txt, emoji-test.txt and emoji-sequences.txt) using the project’s documented inclusion rules.

Structure of the Unicode space (Unicode 17)

Basis: Blocks.txt (303,808 code point positions) and the block names present in expose/lex/*.json.

✅ Included Unicode categories (337 blocks)

1. Modern writing systems

The catalog includes a broad range of currently used alphabets and syllabaries, including:

Latin (including all Extended blocks)
Arabic
Cyrillic
Greek
Hebrew
Indic scripts (Devanagari, Tamil, Bengali, Gujarati, Gurmukhi, etc.)
Southeast Asian scripts (Thai, Lao, Khmer, Myanmar, Javanese, Sundanese …)
African and indigenous writing systems

→ Included in the catalog; visible font coverage varies

2. East Asian writing systems (CJK)

CJK Unified Ideographs (including Extensions A–J)
Compatibility and radical blocks
Kana (Hiragana, Katakana, Extensions)
Hangul (Jamo, Syllables, Extensions)
Tangut, Khitan, Nushu, Yi environment (without Yi PUA dependencies)

→ Included in the catalog with Source Han, Noto and specialist font mappings where available

3. Historic & extinct scripts

Ancient scripts (Phoenician, Ugaritic, Old Persian, Old Italic, Runic …)
Medieval and regional writing systems
Archaeological special blocks (Cuneiform, Egyptian Hieroglyphs incl. Extended-A)

→ Included in the catalog; embedded-font mappings are recorded where available

4. Symbols, signs & notations

Mathematical operators & alphanumerics
Technical symbols
Arrows, geometric shapes, frames
Music notation, chess, game symbols
Legacy computing symbols
Ornamental symbols & dingbats

→ Broadly represented in the catalog; embedded-font coverage varies

5. Emoji & pictographs (glyphic)

Emoji code points
Symbol and pictograph blocks
Transport & map symbols
(Emoji entries are cataloged separately; presentation and sequence rendering remain application- and platform-dependent.)

❌ Categories intentionally outside the display-oriented scope (9 blocks)

These ranges are outside the project’s interoperable display scope for different technical reasons:

1. UTF-16 surrogates

High Surrogates
Low Surrogates
High Private Use Surrogates

→ no displayable characters

2. Private Use Areas (PUA)

BMP PUA
Supplementary PUA-A
Supplementary PUA-B

→ no defined semantics, font-dependent, not interoperable

3. Technical special-purpose blocks without glyph value

Variation Selectors

→ functional or structural, not intended for display

Context

GlyphType focuses on the display-relevant and interoperable areas of Unicode. Entries without confirmed embedded-font coverage remain identifiable in the catalog but may not render visibly.

The project’s scope is defined by its included catalog areas; it does not represent every position in the theoretical Unicode code space.

Fonts are the concrete rendering layer for Unicode code points. While Unicode defines which characters exist, fonts determine which of those characters can actually be rendered visibly.

GlyphType uses a combined font base made of:

Google Noto Fonts (broad, systematic Unicode coverage)
BabelStone Fonts (very rare, historic, and technical blocks)
Adobe Source Han (high-quality CJK coverage for Han ideographs)

This combination covers an unusually large portion of the visible Unicode space, and intentionally goes beyond individual system fonts.

Why not all Unicode code points are covered by fonts

Not every defined Unicode code point automatically has a glyph:

Some code points are purely functional (e.g., control or direction marks)
Others are allocated for private use and have no standardized, interoperable meaning
Some exist formally even though no font designer has created a glyph yet
Historic, rarely used, or newly added characters are often implemented with delay

Font coverage is therefore not static but a continuous process driven by: Unicode versions, font updates, and vendor priorities.

Structure: Unicode vs. font coverage

Pie chart – character coverage by fonts

The following split shows two clearly separated layers:

✅ Included catalog (unique single code points)

Unique single code points contained in the project’s current Unicode 17 catalog. Controls, private-use characters, surrogates and noncharacters are intentionally outside the display-oriented scope.

🎨 Mapped to embedded fonts

Catalog code points present in the union of the current embedded-font coverage maps for the Noto, BabelStone and Source Han collections.

Not every cataloged code point is automatically rendered. The figures below compare one deduplicated catalog set with the current embedded-font coverage maps.

All shares in the chart are calculated deterministically from the current catalog files and their corresponding embedded-font coverage maps.

Context

GlyphType does not claim theoretical completeness, but practical visibility. What is shown is:

Unicode‑conformant
accompanied by explicit embedded-font coverage data
deterministically calculated
independently inspectable from the catalog and documented source data

Unicode defines possibilities — fonts define reality.