Text to ASCII / Unicode Converter
Turn letters, symbols, and Unicode characters into binary, decimal, hex, and U+ code points.
Enter digital value
Use the example or paste your own binary, text, base, or address value.
Results update locally in your browser.
Turn text into binary, decimal, hexadecimal, and Unicode code-point values. For non-ASCII characters, binary is shown by code point, not UTF-8 bytes.
Representation workspace
Cross-check formats before copying the result into code, notes, or network docs.
What this means
ASCII-safe text: 5 character(s) and 5 UTF-8 byte(s), so code points and bytes line up one-for-one. Each visible character is converted to a Unicode code point, while UTF-8 bytes show the actual byte sequence commonly used on the web and in files.
Copy output
Copy the converted formats without saving anything server-side. Use individual buttons when a destination expects one exact format.
| # | Character | Code point | Decimal | Hex | Binary code point | UTF-8 bytes |
|---|---|---|---|---|---|---|
| 1 | H | U+0048 | 72 | 0x48 | 01001000 | 48 |
| 2 | e | U+0065 | 101 | 0x65 | 01100101 | 65 |
| 3 | l | U+006C | 108 | 0x6C | 01101100 | 6C |
| 4 | l | U+006C | 108 | 0x6C | 01101100 | 6C |
| 5 | o | U+006F | 111 | 0x6F | 01101111 | 6F |
- Character
- H
- Code point
- U+0048
- Decimal
- 72
- Hex
- 0x48
- Binary code point
- 01001000
- UTF-8 bytes
- 48
- Character
- e
- Code point
- U+0065
- Decimal
- 101
- Hex
- 0x65
- Binary code point
- 01100101
- UTF-8 bytes
- 65
- Character
- l
- Code point
- U+006C
- Decimal
- 108
- Hex
- 0x6C
- Binary code point
- 01101100
- UTF-8 bytes
- 6C
- Character
- l
- Code point
- U+006C
- Decimal
- 108
- Hex
- 0x6C
- Binary code point
- 01101100
- UTF-8 bytes
- 6C
- Character
- o
- Code point
- U+006F
- Decimal
- 111
- Hex
- 0x6F
- Binary code point
- 01101111
- UTF-8 bytes
- 6F
Which format should I copy?
| Format | Best for | Watch for |
|---|---|---|
| UTF-8 bytes | byte-level debugging, files, web payloads, and protocol traces | non-ASCII characters use multiple bytes even when they look like one character |
| Unicode code points | identifying the exact character, symbol, emoji, or invisible/control character | code points are not the same as encoded bytes on disk or over the wire |
| JSON escape | placing text inside a JSON string literal | only use inside JSON/string contexts; do not double-escape already escaped text |
| HTML escape | showing characters safely as HTML entities | HTML entities are not URL encoding or JavaScript escaping |
| URL escape | query-string or path-component values | encode components, not a whole URL with slashes and separators |
- Best for
- byte-level debugging, files, web payloads, and protocol traces
- Watch for
- non-ASCII characters use multiple bytes even when they look like one character
- Best for
- identifying the exact character, symbol, emoji, or invisible/control character
- Watch for
- code points are not the same as encoded bytes on disk or over the wire
- Best for
- placing text inside a JSON string literal
- Watch for
- only use inside JSON/string contexts; do not double-escape already escaped text
- Best for
- showing characters safely as HTML entities
- Watch for
- HTML entities are not URL encoding or JavaScript escaping
- Best for
- query-string or path-component values
- Watch for
- encode components, not a whole URL with slashes and separators
Copyable escape formats
| Format | Value | Use case |
|---|---|---|
| UTF-8 bytes | 48 65 6C 6C 6F | Byte-level debugging |
| JSON escape | Hello | String literal escaping |
| HTML escape | Hello | HTML entity-safe representation |
| URL escape | Hello | Query/path component encoding |
- Value
- 48 65 6C 6C 6F
- Use case
- Byte-level debugging
- Value
- Hello
- Use case
- String literal escaping
- Value
- Hello
- Use case
- HTML entity-safe representation
- Value
- Hello
- Use case
- Query/path component encoding
Watch-outs
- Encoding details matter: ASCII, Unicode code points, UTF-8 bytes, and binary text are related but not always identical.
- Large values can be long in binary; copy carefully if using the result in code or network documentation.
- These are utility conversions, not cryptography, validation, or forensic tooling.
Notes
These are utility conversions for valid input formats. Text encoding can be nuanced: ASCII, Unicode code points, and UTF-8 bytes are not always the same thing.
Get a better answer from the Text to ASCII / Unicode Converter
- Start with the example values to see how the tool behaves.
- Swap in your own numbers, even if they are rough first-pass estimates.
- Change one input at a time so you can see what actually moves the result.
What the result means
The result shows the same data in a different digital format, such as binary, hex, text, bytes, or code points.
How to use it
Use the detail rows to see how the value is broken apart. That makes it easier to spot padding, byte, encoding, or formatting issues before pasting into code.
What can change it
Computers can treat the same-looking value differently depending on encoding, signedness, byte order, separators, and escape format.
Example to try
Convert a sample with plain letters and one emoji or accented character so you can see code points and UTF-8 bytes diverge.
Assumption to challenge
ASCII, Unicode code points, and UTF-8 bytes are related but not interchangeable. One visible character can use multiple code units or bytes.
Verify next
Confirm whether your target needs U+ code points, decimal values, hex escapes, UTF-8 bytes, JSON escapes, or HTML entities.
Key terms
ASCII
A 7-bit character set for basic English letters, digits, punctuation, and control characters.
Unicode code point
A universal character identifier written like U+0041 or U+1F600.
UTF-8 byte
The actual byte sequence used to store or transmit a Unicode character in UTF-8.
Common uses
- Encode words as binary.
- Find ASCII decimal and hex codes.
- View Unicode code points for characters.
Common questions
Is the Text to ASCII / Unicode Converter private?
Yes. CalcShelf calculators run without an account, do not save calculator entries, and do not put raw inputs into shareable URLs or analytics events.
How accurate is the Text to ASCII / Unicode Converter?
It uses common data-format rules. Encoding, byte order, separators, signedness, and escape requirements can change how a receiving system reads the same value.
What should I check after using the Text to ASCII / Unicode Converter?
Verify the expected encoding, byte boundaries, separators, escape format, and destination-system requirements before pasting into code or config.
Which calculator should I try next?
Use the related calculators below to cross-check the same decision from another angle before you act.
Method behind the estimate
Digital tools use standard base, byte, ASCII, Unicode, UTF-8, IPv4, and representation rules to convert values in the browser.
Why the detail matters
Encoding and formatting context matters. Verify byte order, padding, signedness, character encoding, and destination syntax before copying into code or docs.
Privacy guardrail
Your calculator values are for you. CalcShelf does not require an account, save calculator entries, put your numbers into shareable URLs, or use raw inputs as analytics events.
Copy or print safely
Use any copy, print, or worksheet controls as local handoff tools for your own notes, supplier calls, lender questions, or implementation checklist. They are there to help you explain the result to a human.
Before acting
Treat the result as a decision draft, not a verdict. Recheck the source numbers, run a downside case, and verify the real-world rule, quote, label, or spec that controls the final answer.
Last reviewed: May 11, 2026. See methodology and editorial policy for formulas, assumptions, rounding, review approach, and limitations. For code, data migration, security, or production systems, confirm the expected encoding and destination format.