This converter displays the same bytes in different representations: Unicode text, hexadecimal, binary, decimal, octal, Base64 or Base64URL. Conversions operate on the actual input bytes so that characters and numeric values are not confused.
The text café does not always occupy four bytes. In UTF-8, é uses two bytes. Selecting the correct character encoding is therefore essential when reproducing an exact value.
One byte is represented by two hexadecimal digits or eight bits. The ASCII letter A, for example, is 41 in hexadecimal and 01000001 in binary.
Base64 represents bytes with printable characters. Base64URL replaces + and / so the value can be used more safely in URLs and tokens.
UTF-16LE and UTF-16BE make byte order visible. Latin-1 is suitable only for characters available in ISO-8859-1. The 32-bit little-endian and big-endian modes group bytes into four-byte integers and show how their order changes the numeric value.
Automatic detection is a convenience, not proof: a short alphanumeric string may be valid text, hexadecimal or Base64. Select the source format explicitly whenever the conversion must be reproducible.
A small file can be loaded to inspect its bytes or export them in another format. The tool does not parse it as a document; it works with the raw binary content. The displayed size limit prevents excessively large output.
This converter works with bytes across UTF-8 text, binary, hexadecimal, decimal, octal and Base64. Select the input format explicitly when automatic detection could be ambiguous, especially for digit-only strings.
Hello → hexadecimal 48 65 6c 6c 6fc3 a9 → UTF-8 text éHello → Base64 SGVsbG8=Hexadecimal uses two characters for each byte. Base64 is more compact and represents bytes with a 64-character alphabet.
A string such as 1010 could be binary, decimal or plain text. Select the source format to prevent incorrect automatic detection.
Yes. Non-ASCII characters are converted to their UTF-8 bytes before binary, hexadecimal, decimal, octal or Base64 representation.