Encoding desk

Unicode Code Point

Map one Unicode scalar value to U+ notation, decimal, and hexadecimal forms.

Unicode Code Point: Find the numeric Unicode identity of a single scalar value. Unicode Code Point reports U+ notation alongside decimal and hexadecimal forms. Use it to distinguish similar-looking characters or identify a pasted symbol, remembering that one visible symbol can contain several scalars. Runs 100% locally in your browser with zero server file uploads.

Runs
In your browser
Cost
Free · no sign-up
Availability
Ready to use
Character → U+ / local workbenchLocal processing

Runs entirely in your browser

16 character input · one Unicode scalar result

Result

Ready

Surrogate code points are not Unicode scalar values and are rejected.

Identity mapping and a worked lookup

Let c be the entered scalar and N its Unicode code point. Report decimal N, hex N in uppercase, and U+ followed by at least four hex digits. Input 😀 has N = 128512 = 1×65536 + 15×4096 + 6×256 + 0×16 + 0, giving hex 1F600. The exact result is U+1F600\nDecimal: 128512\nHex: 0x1F600. The symbol itself is not repeated in this direction’s output. Decimal and hex describe the same N rather than separate encodings The Unicode inspector helps inspect multiple-scalar sequences rejected by this single-scalar field.

Scalars, surrogate halves and display

Unicode’s core specification (https://www.unicode.org/versions/latest/core-spec/) distinguishes scalar values from UTF-16 surrogate code points. Values U+D800–U+DFFF are rejected, as are strings containing zero or multiple scalars. U+0000 is valid even though it is invisible. The field has a 16-code-point length guard, but that does not permit a sixteen-character lookup. All accepted code points lie at or below U+10FFFF and fit exactly in a JavaScript Number; the large-integer precision issue of general base conversion does not arise. Glyph shape still depends on the selected font.

How to use it

  1. Enter the value in the format shown below.
  2. Run the conversion and check the result against your source convention.
  3. Copy or download the output in the form required by your destination.

Privacy & limitations

Conversion runs in your browser. Your values and results are not uploaded.

Related tools

Frequently asked questions

Why is my single emoji rejected as more than one character?

Some displayed emoji are sequences, including flags, skin-tone variants and families joined by zero-width joiners. This field accepts one scalar, not one visual grapheme. Separate the sequence into its component scalars with a Unicode inspector, then look up each component here.

Are é and e followed by an accent the same input?

They may look identical, but the first can be one scalar U+00E9 while the second has U+0065 followed by U+0301. The second form is rejected as multiple scalars. No normalisation is applied before the lookup, so the tool reveals the entered representation rather than choosing a canonical spelling.

Does the decimal result tell me a byte value or string length?

It is a scalar’s numeric identifier. For 😀 it is 128512, while its UTF-8 representation needs four bytes and its JavaScript string occupies two UTF-16 code units. These measures answer different questions. Use Text to Hex for bytes rather than treating the decimal identifier as an encoded byte.

Free tool · runs in your browser · no account required