Unicode Character Finder

The Unicode Character Finder is a searchable library of special characters — arrows, mathematical symbols, Greek letters, currency signs, punctuation, and emoji — with each entry showing its code point and HTML entity. Search by keyword, click a card to copy the character, and paste it anywhere text is accepted. It is for writers who need an em dash or a proper quotation mark, developers who need the entity for a symbol, and anyone who has ever hunted through a character map for a single glyph.

How to Use

1. Search or browse. Type a keyword such as “arrow”, “check”, or “sigma”, or filter by category.
2. Click a card to copy the character to your clipboard.
3. Read the details on the card: the code point (U+2192), the character name, and the HTML entity where one exists.
4. Paste into a document, a chat, a design tool, or a code editor. For markup, use the provided entity rather than the raw symbol if the file’s encoding is uncertain.

Worked Examples

Example 1 — typographic punctuation. A writer replacing three hyphens with a proper em dash searches “dash”, copies — (U+2014), and pastes it into the draft. Because a real em dash is a single character, it reflows correctly and does not break at a line end the way three hyphens do. The same library supplies the curly quotation marks “ ” and the ellipsis …, which look right in published prose where straight quotes look like code.

Example 2 — a math note. A student writing up an assignment needs the summation symbol ∑, the infinity sign ∞, and the Greek letters α and β. Copying them from the finder keeps the notation consistent; typing approximations such as “sum” or “inf” would not render as mathematics.

Example 3 — markup for a symbol. A developer adding a right arrow to a page can either paste → directly, which works in a UTF-8 document, or write → / →, which works regardless of the document encoding. The card shows both forms, so the choice is explicit rather than a guess.

Code Point, Glyph, and Byte: Three Different Things

These three terms are often used interchangeably, and keeping them apart explains most confusion about special characters.

• Code point — the character’s identity, a number in the Unicode standard written as U+ plus hexadecimal, such as U+00E9 for é. It never changes.
• Glyph — the visual shape a font uses to draw the code point. Different fonts, and different operating systems for emoji, draw the same code point differently.
• Byte sequence — how the code point is stored in a file. UTF-8 encodes U+00E9 as two bytes and the em dash U+2014 as three; UTF-16 uses different bytes for the same characters.

So a character can be identical in identity, different in appearance, and variable in storage size — all at once. Understanding that layering is what makes an “encoding problem” tractable: the code point tells you what the character should be, and the bytes tell you what actually got written.

Where to Paste What

• Prose and documents: paste the character itself. Word processors, note apps, and email all accept Unicode directly.
• HTML and email templates: the named entity (→) is readable; the numeric entity (→) works even in older or misconfigured encodings. Both render the same character.
• CSS: use the \2192 escape inside a content property, or paste the character directly in a UTF-8 stylesheet.
• Code strings: paste the character if the file is UTF-8, or use the language’s escape (\u2192 in JavaScript and Python, \u{2192} in some others) when a pure-ASCII source is required.
• Social media: paste directly; platforms handle Unicode and will render the character if the viewer’s font supports it.

Common Mistakes

• Using lookalike ASCII. A straight quote " is not a curly quote “, and three periods are not an ellipsis. Search for the specific character instead of approximating it with keyboard characters.
• Assuming a copy failed because the paste looks empty. Some characters are invisible — the zero-width space U+200B, the non-breaking space U+00A0, and the soft hyphen U+00AD. They occupy no visible width by design; check the character count if unsure.
• Mixing encodings. A file saved as Latin-1 with a UTF-8 character inside produces mojibake. Save as UTF-8 and declare the encoding in the document head.
• Trusting the entity name to exist. Only a subset of characters has a named entity; for the rest, the numeric form 中 always works.
• Expecting every font to draw every symbol. Rare mathematical and historic script characters need a font that covers them; a missing glyph is a font limitation, not a data error.

Features

• Searchable library of symbols across multiple categories, with keyword matching
• Each entry shows the code point, name, and HTML entity
• One-click copy to the clipboard
• Covers arrows, math, Greek letters, currency, punctuation, and symbols
• Works offline after loading, with no account
• 100% client-side — nothing is uploaded

Use Cases

• Writing: Em dashes, curly quotes, bullets, and proper ellipses.
• Mathematics: Summation, integrals, infinity, and Greek letters.
• Web development: HTML entities and CSS escapes for symbols.
• Social media: Arrows, stars, checkmarks, and decorative symbols.
• Language learning: Accented and non-Latin characters for study material.

Related Tools

• ASCII Table
• HTML Encoder/Decoder
• Text to Binary
• Emoji Picker