ASCII to Hex Converter

Each character has a numeric code point; the tool renders that number in base 16. In UTF-8 mode the string is first encoded to UTF-8 bytes (via TextEncoder) and every byte becomes a two-character hex token.

No. All conversion runs entirely in your browser. Your text is never uploaded, cached, or tracked, and the tool works offline after the page loads.

Yes. The default “Code points” mode uses codePointAt so 😀 becomes 1F600 (not two surrogate halves), and 中 becomes 4E2D. For byte-level work pick the UTF-8 mode instead – 😀 then expands to four bytes F0 9F 98 80.

Yes, 100% free with no cap on input length or number of encodes. No sign-up, no premium tier, no watermark.

Yes. HTML, CSS, and JavaScript are self-contained. Once the page has loaded, you can turn off Wi-Fi and keep encoding – useful on air-gapped machines.

Code-point mode renders one hex value per visible character, which is what most programming contexts think of as a “character code”. UTF-8 mode renders each byte of the string’s UTF-8 serialisation – useful when you need the exact wire format or are building a uint8_t[] from a string.

The 0x prefix makes each token a C/JS/Go/Rust-style integer literal, so you can drop them directly into source code. The JSON-array separator wraps the whole output in ["48","69"] – paste-ready into a JSON file or a JS array literal.

Hex dumps (Wireshark, xxd, hex editors) traditionally use lowercase. Programming-language literals (C, Go, JSON-like) often prefer uppercase after 0x. The tool defaults to lowercase; flip the toggle when your target tool expects otherwise.

They are skipped, not guessed, and the count shows up in the red warning bar and in the stats line. For example in Strict ASCII mode, é is skipped with a count of 1 – switch to Code points or UTF-8 mode to include it.

Use the sibling Hex to ASCII converter. It accepts the same mode set and will round-trip cleanly for any input encoded here, including emoji.