How This Unicode Lookup Works
This unicode character lookup takes any character, emoji, or code point and returns its full identity: the code point in U+XXXX notation, its decimal and hex values, an approximate character category, JavaScript and HTML escape sequences, and both its UTF-8 byte sequence and UTF-16 representation. As a unicode to utf-8 converter, it correctly handles the full range up to U+10FFFF, including characters that require a UTF-16 surrogate pair or multiple UTF-8 bytes.
Three Ways to Look Up a Character
Text mode analyzes every character in a string at once (up to 100), useful for scanning a whole word or emoji sequence. Single character mode expects exactly one character, ideal when you already have the exact glyph. Code point mode works as a character code point finder that accepts U+XXXX notation, a 0x-prefixed hex value, or a plain decimal number, useful when you already know the numeric code point but not what character it represents.
Understanding UTF-8 and UTF-16 Encoding
UTF-8 represents each code point as 1 to 4 bytes depending on its value, ASCII characters take 1 byte, while characters requiring more range (like accented letters, CJK ideographs, or emoji) take 2 to 4. UTF-16, used internally by JavaScript strings, represents code points at or below U+FFFF directly as one 16-bit unit, but code points above that (most emoji, for example) require a surrogate pair, two 16-bit units combined, this utf-8 utf-16 converter shows both representations side by side so the difference is visible at a glance.
Common Uses
Debugging text encoding issues (mojibake, incorrect byte counts, unexpected surrogate pair splitting) is the most common use for this unicode character info tool. Looking up an emoji code point lookup for documentation or code comments, generating a unicode escape converter output for embedding a character in source code or HTML, and general curiosity about how a specific character is represented internally are common secondary uses.
What This Tool Doesn't Do
The unicode character category shown is an approximation based on common code ranges, not a lookup against the full official Unicode Character Database, so it can be inaccurate for characters outside the ranges it specifically recognizes. It also doesn't include the official Unicode character name (that requires a much larger name database this tool doesn't ship), and text mode caps analysis at 100 characters per request rather than processing arbitrarily long input.