Unicode Inspector
Verify that the source string contains the character or sequence you intend to represent. Open the Unicode Inspector.
Code Point Converter
Code Point Converter is a browser utility that turns characters into code points, escapes, and bytes. Translate the same Unicode text into code-point notation, numeric HTML references, JavaScript escapes, CSS escapes, and raw UTF-8 bytes without mixing the rules of those formats.
Output syntaxesSix
Numeric baseHexadecimal
Original retainedLiteral UTF-8
Analyze your own text
Try a sample:
Maximum 2,000 characters · no upload
Enter text or choose a sample to generate a detailed report.
One character, several representations
A code point, an encoded byte sequence, and a language escape are related descriptions—not interchangeable strings. The converter labels each layer so it lands in the correct context.
- U+ notation identifies abstract Unicode scalar values in documentation.
- UTF-8 represents those values as bytes for files, databases, and network traffic.
- HTML numeric references instruct an HTML parser to emit characters.
- JavaScript and CSS escapes follow the grammar of their own languages.
1Identity★ · U+2605
2Source syntax★ · \u{2605}
3UTF-8 encodingE2 · 98 · 85
A1 byte©2 bytes★3 bytes🚀4 bytes
Representation chooser
Use literal text when the whole pipeline is reliably UTF-8. Reach for an escape only when its surrounding grammar or diagnostic task calls for one.
| Output | Example for ★ | Where it belongs | Common mistake |
|---|---|---|---|
| Literal | ★ | UTF-8 HTML, source, or content | Saving the file under a legacy encoding |
| Code point | U+2605 | Specifications, tickets, and documentation | Pasting U+2605 and expecting a glyph |
| HTML hex | ★ | HTML character data or attribute values | Using it inside CSS as though syntax were shared |
| JavaScript | \u{2605} | Modern JavaScript string literals | Dropping the braces for a non-BMP value |
| CSS | \2605 | CSS strings, identifiers, or generated content | Forgetting that a trailing space can terminate the escape |
| UTF-8 | E2 98 85 | Hex dumps and encoding diagnostics | Treating displayed hex bytes as literal page text |
Worked conversions across byte widths
UTF-8 is variable-width. ASCII occupies one byte, while other Unicode scalar values require two, three, or four bytes.
| Character | Code point | UTF-8 bytes | HTML hexadecimal |
|---|---|---|---|
| A | U+0041 | 41 | A |
| © | U+00A9 | C2 A9 | © |
| ★ | U+2605 | E2 98 85 | ★ |
| 🚀 | U+1F680 | F0 9F 9A 80 | 🚀 |
A clean conversion workflow
Follow the sequence from evidence to policy. Each stage guards against a different class of Unicode mistake.
Identify the destination
Decide whether the value is going into content, documentation, JavaScript source, a stylesheet, or a byte-level investigation.
Convert the complete sequence
Preserve every code point in emoji and combining sequences. Converting only the visible base changes the result.
Copy the labeled output
Use the representation whose grammar matches the destination; do not transplant escaping rules between languages.
Round-trip the result
Parse or render the destination, then inspect the recovered text to confirm that the original code points survived.
Questions people ask about code point converter
Should I replace every symbol with an HTML entity?
Usually no. Literal Unicode is readable and dependable in a correctly declared UTF-8 document. Numeric references are useful for specific markup constraints, invisible values, or ASCII-only tooling.
Why does an emoji need more than four hexadecimal digits?
Many emoji sit above the Basic Multilingual Plane. JavaScript's brace form expresses the full scalar value directly; older UTF-16 escape notation requires a surrogate pair.
Are UTF-8 bytes the same as a code point?
No. A code point is an abstract number such as U+2605. UTF-8 encodes that number into one to four bytes; the black star becomes E2 98 85.
Can I use the CSS escape in JavaScript?
Do not assume so. CSS and JavaScript define different tokenization and escape termination rules. Select the output expressly labeled for the destination language.
Build the surrounding knowledge
Foundations
Unicode Code Points, UTF-8, UTF-16, and UTF-32 Explained
A hands-on explanation of U+ notation, scalar values, code units, byte sequences, and the encoding mistakes that produce broken text.
Read the guide →EngineeringUnicode Symbols in HTML, CSS, and JavaScript
Use literal UTF-8 characters and escapes correctly in HTML, CSS, JavaScript, attributes, and structured data without creating encoding problems.
Read the guide →Emoji & renderingWhy Unicode Symbols Show as Boxes, Tofu, or Question Marks
Diagnose boxes, tofu, and missing glyphs by separating Unicode character support, font coverage, shaping, fallback, and encoding failures.
Read the guide →Move to the next diagnostic
Normalization Checker
Compare normalization forms before encoding when equivalence rules belong at an upstream text boundary. Open the Normalization Checker.
Standards behind this tool
The browser output is designed as a practical diagnostic, while normative definitions belong to the standards publishers below.