Base64 Hex array encoder/decoder

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from Base64 Hex array encoder/decoder

Base64 Hex array encoder/decoder converts hexadecimal byte arrays to Base64 text. Hexadecimal and Base64 both describe bytes, but group those bits differently and use different character alphabets. Every byte needs two hexadecimal digits. Encoding the literal text 48656c6c6f produces a different Base64 string from encoding the bytes it describes. Inspect byte boundaries and any separators or prefixes accepted by the input control before converting. Use the worked example to understand what a successful result looks like, then compare it with a small sample of your own input. Keep the original available until you have checked the output in its destination. Conversion establishes a representation; it does not establish that the underlying information is correct or that the receiving application accepts every supported feature.

Guide updated October 13, 2026

How to use this tool

1. Enter or load hexadecimal byte arrays using the input controls. Begin with the worked example or a small sample for which you know the expected result.
2. Review any available conversion options, then inspect the Base64 text result. Resolve a reported parse error at its source before attempting to reuse the output.
3. Check the example below against your own data. Inspect byte boundaries and any separators or prefixes accepted by the input control before converting.
4. Copy or save the resulting Base64 text content using the controls provided, then validate it in the application or parser that will actually consume it.

SEE IT IN PRACTICE

A worked example

48 65 6c 6c 6f

SGVsbG8=

The hexadecimal bytes spell Hello in ASCII. Base64 encodes those same bytes; it does not encode the printed hex digits as text.

Text digits are not the bytes they name

The two hex characters 4 and 1 describe the single byte 0x41 only when interpreted as hexadecimal. If treated as text, they represent two separate character bytes. This distinction explains many unexpected Base64 results. Count the intended input bytes and test a one-byte value before converting a long key, digest, or protocol fixture.

Leading zero bytes count

Hexadecimal 00 41 describes two bytes, whereas 41 describes one. The initial zero byte is part of a binary payload and must survive conversion even though a numeric representation might discard it. Keep an even number of hexadecimal digits and inspect how the input handles spaces or prefixes. Base64 padding reflects the byte count, not the number of visible hexadecimal digits, so the correct grouping is essential when comparing a test vector.

When this tool is useful

• Prepare binary test vectors while retaining a separate copy of the source.
• Use a small example to troubleshoot byte-array representation mismatches and identify a representation mismatch.
• Create compact forms of hexadecimal payloads without manually rewriting every field or symbol.

Tips for a better result

• Every byte needs two hexadecimal digits. Encoding the literal text 48656c6c6f produces a different Base64 string from encoding the bytes it describes.
• Inspect byte boundaries and any separators or prefixes accepted by the input control before converting.
• After changing formats, compare meaningful values rather than whitespace alone. Read the Base64 text output with its intended parser when exact types or escaping matter.

Frequently asked questions