Unicode Code Point Inspector

Inspect Unicode code points, encoded bytes and pinned names, blocks and scripts locally.

Inputs stay on your device No sign-up Free to use
How this works

The tool runs in this browser. Your file or text is not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.

Privacy details

Inspect input controls

Showing an example. Edit to see your own.

Processed in your browser. Your inputs stay on this device.

How to use Unicode Code Point Inspector

  1. Paste text or enter explicit code points.
  2. Choose the input mode and inspect the code points.
  3. Review encodings, Unicode names and any surrogate or script hints.

Example: Unicode Code Point Inspector

A local worked example using the inputs and settings below for unicode code point inspector.

You add
Input kind: "text" Text or code points: "A😀é"
You get
Inspected 4 code points using Unicode 17.0.0. 1 | A | U+0041 | LATIN CAPITAL LETTER A | Lu | Basic Latin | Latin | 0041 | 41 2 | 😀 | U+1F600 | GRINNING FACE | So | Emoticons | Common | D83D DE00 | F0 9F 98 80 3 | e | U+0065 | LATIN SMALL LETTER E | Ll | Basic Latin | Latin | 0065 | 65 unicode-code-points.json

Options

Text mode
The tool inspects the entered sequence without normalization. A visible accented letter can consist of one code point or several.
Code-point input
Use the supported code-point form for explicit inspection. Names, blocks and scripts come from the pinned Unicode 17 dataset.

Supported inputs and limits

Up to 4,096 UTF-16 input units or 1,024 entered code points. Names/categories/blocks/scripts use Unicode 17.0.0. Unpaired surrogates are flagged. Input is inspected without normalization or modification. Mixed-script hints are review aids, not confusable detection, glyph coverage or security certification.

Where your input is processed

This tool processes your input in this browser. Your text and files are not uploaded to UseFreeTools. Check this tool's limits for anything it may save on your device.

A code-point record does not describe a glyph

Fonts can combine or omit characters, and several code points can form one visible grapheme. Unpaired surrogates are flagged rather than interpreted as ordinary characters. Mixed-script hints call for review; they do not establish impersonation or safe rendering.

Questions about Unicode Code Point Inspector

Is a character always one code point?

No. A displayed symbol can contain several code points.

Does a mixed-script hint prove spoofing?

No. Many legitimate strings use multiple scripts; review the actual text.

Does this normalize the text?

No. It reports the entered code points without changing them.

Project manager: Tony Hines · Content updated 4 October 2026 · Report a problem