b2KIT

Unicode Character Lookup

Search Unicode characters by name, code point, or block with copy-to-clipboard and encoding display.

Tested tool guide Tested browser tools Checked August 16, 2026

What Unicode Character Lookup does, with a checked example

Unicode gives every character three separate identities: a code point like U+03A9, a formal name like GREEK CAPITAL LETTER OMEGA, and a glyph. This tool accepts any one of them - a name fragment, a hex code point, or a block name - and returns the matching records: the rendered character, its official name, its block, and the byte sequences it produces in UTF-8 and UTF-16, each with one-click copy. What most users get wrong: the glyph is not the identity. Visually identical characters such as OMEGA (U+03A9) and OHM SIGN (U+2126) are distinct code points, and only the name or the code point tells them apart.

Worked example

A concrete input and expected output from the current implementation.

Input

U+03A9

Expected output

Ω | GREEK CAPITAL LETTER OMEGA | U+03A9 | Block: Greek and Coptic | UTF-8: CE A9 | UTF-16BE: 03 A9

U+03A9 is the Greek capital omega. Because 0x03A9 (937) falls in the two-byte UTF-8 range (U+0080 to U+07FF), its bytes are 11001110 10101001, written CE A9. UTF-16 stores the code point directly as one 16-bit unit, 03 A9 in big-endian order.

How the result is produced

1

Search fields

Name search matches substrings of official names, case-insensitively: 'omega' finds GREEK CAPITAL LETTER OMEGA (U+03A9) and GREEK SMALL LETTER OMEGA (U+03C9). Code point search accepts hex in common forms - 03A9, U+03A9, u+03a9. Block search takes block names such as 'Greek and Coptic' or 'Emoticons' and returns every character in the range. Multiple matches are listed together, each with its full record.

2

The record

For a matched character the tool shows the glyph, the official name, the code point, and the hex byte sequences the character produces in UTF-8 and UTF-16. Copy buttons put the actual character on the clipboard, not an escaped form, so pasting into an editor, an HTML file, or an API payload inserts the real glyph. The byte display is where assumptions surface: omega is two bytes (CE A9) in UTF-8, not one.

Good uses

  • You half-remember a symbol - a letter with a ring, a circled number - and need its exact code point to enter into code, a document, or a layout.
  • You are about to write a string to a file or API and need to confirm its byte size in UTF-8, especially for emoji and other supplementary-plane characters.
  • You received text with suspicious punctuation - a 'hyphen' that is not U+002D, or straight quotes that might be curly - and want to identify the real characters before the text hits a system with a narrow charset.

Limits and checks

  • Name search matches official names only. Informal descriptions fail or misfire: what people call 'the pi symbol' is officially GREEK SMALL LETTER PI, and 'heart' matches a dozen heart-named characters at once. Use a code point to pin down one character.
  • A bare number is ambiguous. '937' read as hex is U+0937 (DEVANAGARI LETTER SSA); read as decimal it is U+03A9 (omega). Prefix with U+ to force one interpretation, and verify the returned code point rather than trusting the glyph.
  • A defined character can still display as a box. Results render with whatever fonts the browser has; rare scripts and old CJK extensions may show as missing-glyph placeholders, and even a character that renders here may not render on a user's device. The lookup proves the code point exists, not that it displays everywhere.

Common questions

Why does a one-letter search return so many results?

Name matching is substring-based and case-insensitive, so any official name containing that letter is a match, and common letters appear in hundreds of names. Narrow the query with more of the name ('e with acute'), switch to a code point (U+00E9), or use block search to browse a bounded range.

Why does the same character show different bytes in UTF-8 and UTF-16?

They are independent encodings of one code point. Omega (U+03A9) is two bytes in both - CE A9 in UTF-8, 03 A9 in UTF-16BE. An emoji like U+1F600 is four bytes in UTF-8 (F0 9F 98 80) and a surrogate pair, also four bytes, in UTF-16 (D8 3D DE 00). Neither is wrong; choose what your consumer expects.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools