Convert UTF-8 to Hexadecimal

Base 16. Each UTF-8 byte (0-255 decimal) becomes a 2-character hexadecimal token (00-FF). ASCII characters get 1 byte → 2 hex chars; multi-byte characters expand proportionally.

Yes. “Hex” and “Hexadecimal” mean the same thing. Both tools produce identical output and accept the same input. They exist as separate slugs because users search both terms. If you find a behaviour difference, it’s a bug – please report it.

UTF-8 multi-byte sequences are extracted via TextEncoder. 🌍 (U+1F30D) becomes 4 hex tokens: F0 9F 8C 8D. Naive implementations that loop charCodeAt would see UTF-16 surrogate pairs (D83C DF0D) instead – wrong output.

Concatenates N consecutive bytes into single tokens before separator. Useful for visualising 16-bit (group=2), 32-bit (group=4), or 64-bit (group=8) words.

Strips braces, commas, 0x prefixes, colons, all whitespace. Remaining characters must be hex (0-9, A-F, case-insensitive) and the count must be even. Invalid UTF-8 byte sequences throw via fatal mode.

No. UTF-8 has no endianness (RFC 3629 design) – it’s a byte stream, not multi-byte integers. Endianness only applies to UTF-16 / UTF-32. If you need byte-order options, your data probably isn’t UTF-8.

Exactly 2 hex characters per byte (plus separator chars if any). So encoding overhead is 2× the UTF-8 byte count. ASCII text doubles in size; mixed Latin roughly 2.6×; emoji ~8× the input character count.

No. The conversion runs entirely in your browser – nothing is sent to a server, logged, or stored, and the tool keeps working offline once the page has loaded.

200,000 characters. Hex output peaks at 2× plus separators.

The Bytes tool exposes hex, decimal, AND binary plus prefix options. This Hexadecimal tool is hex-specific with 5 output formats for direct paste into different contexts.