To convert Base64 to hex, a decoder translates each four-character Base64 group back into its original three bytes of binary data, which are then formatted as six hexadecimal characters representing those exact same byte values. Specifically, standard Base64 represents groups of three 8-bit bytes (24 bits total) as four 6-bit characters selected from a 64-character alphabet, while hexadecimal represents each individual 8-bit byte as exactly two base-16 digits ranging from 00 to ff. The conversion is a direct, reversible translation of binary data that does not alter the underlying bytes, meaning that converting a string of canonical padded Base64 to lowercase hexadecimal yields a precise representation of the same raw byte sequence. This process is commonly used by developers to inspect encoded payloads, verify cryptographic hashes, parse serialized network protocol fields, or debug binary test fixtures. Because the translation is entirely mathematical, it does not involve any text encoding conversions like UTF-8 or ASCII interpretation, ensuring that the raw binary values remain completely unaltered.
Understanding Base64 and Hexadecimal Encodings
For beginners, working with raw binary data can be challenging because computers store information as sequences of ones and zeros. To make these bytes readable for humans and safe for text-based transmission systems, we use encoding formats. Base64 and hexadecimal are two of the most popular ways to represent binary data as text.
Base64 encodes binary data by representing every three bytes as four printable characters, which expands the data. This alphabet consists of 64 characters: uppercase letters, lowercase letters, numbers, the plus sign (+), and the slash (/). When the final group has only one or two bytes, equals signs (=) complete the four-character group as padding. Because it uses a larger alphabet, Base64 is highly compact. However, it is difficult for humans to read or map directly to individual byte values just by looking at the characters.
Hexadecimal, often called hex, represents each individual byte as exactly two digits from a 16-character alphabet (0-9 and a-f). Because each byte maps directly to two hex characters, hex is incredibly useful for inspecting binary files, protocol fields, and cryptographic hashes. If you want to understand the underlying bit shifts that occur during this translation, you can read our guide on Base64 to Hex Explained: A Byte-Level Walkthrough.
When you need to translate data between these two formats, using a strict tool ensures that no bytes are lost or modified. The standard Base64 to Hex Converter translates the same byte sequence between RFC 4648 Base64 and Base16 hexadecimal without performing any intermediate text decoding. This means your raw bytes remain exactly as they were intended, with no risk of corruption from character set assumptions.
RFC 4648 Test Vectors and Byte Mappings
The Internet Engineering Task Force (IETF) defines the standards for these encodings in RFC 4648. This specification outlines exactly how encoders and decoders must behave to maintain consistency across different programming languages and systems. To verify that a conversion tool is 100% accurate, developers use a set of official test vectors.
The table below shows these standard test vectors. It illustrates how raw ASCII text characters map to their exact hexadecimal byte values and their corresponding canonical Base64 representations:
| Raw Text | Hexadecimal Bytes (Lowercase) | Canonical Base64 Output |
|---|---|---|
| (empty) | (empty) | (empty) |
| f | 66 | Zg== |
| fo | 666f | Zm8= |
| foo | 666f6f | Zm9v |
| foob | 666f6f62 | Zm9vYg== |
| fooba | 666f6f6261 | Zm9vYmE= |
| foobar | 666f6f626172 | Zm9vYmFy |
To understand how this math works step-by-step, let us look at a single worked example converting the single character "f" to Base64:
First, we identify the hexadecimal value of "f", which is 66. In binary, the byte 66 (base 16) is represented as 01100110 (base 2).
Next, Base64 splits binary data into 6-bit groups. Since we only have 8 bits, we divide them as follows:
- Group 1: The first 6 bits are 011001, which equals 25 in decimal.
- Group 2: The remaining 2 bits are 10. We must pad this group with four zeros to make a full 6-bit block: 100000, which equals 32 in decimal.
Now, we look up these decimal values in the standard RFC 4648 Base64 alphabet table:
- Index 25 maps to the character Z.
- Index 32 maps to the character g.
Because a standard Base64 block must always consist of four characters, and we only have two characters (Zg) representing our single input byte, we append two padding characters (==) to fill the remaining slots. The final canonical result is Zg==.
Converting Base64 to Hex Online
If you have a Base64 string and need its exact hexadecimal representation, you can perform this action entirely inside your web browser. The online converter performs all calculations locally using numeric byte arrays rather than browser text coercion, meaning your input data is never uploaded to any external servers.
- Choose Base64 to hexadecimal or hexadecimal to Base64 and identify the exact source encoding profile.
- Paste canonical padded Base64 without whitespace, or hex with exactly two digits per byte and no prefix or separators.
- Run the conversion, verify the expected byte length and leading zeros, then copy the exact result.
This utility supports inputs up to 500,000 decoded bytes, which is more than enough for handling typical cryptographic keys, hashes, or encoded configuration files. Because the output is copied directly to your clipboard without any extra labels or descriptive text, you can paste the clean result directly into your terminal or code editor.
Strict Validation and Common Mistakes
Many beginners run into issues when converting Base64 to hex because different systems use slightly different variations of these encodings. Our converter uses a strict validation engine to ensure that your data is perfectly formed. This strictness prevents silent errors that could corrupt your data down the line.
One common issue is the omission of padding. Standard Base64 requires the input length to be a multiple of four characters, using equals signs (=) at the end if necessary. Some modern web APIs omit this padding or use a variant called "base64url", which replaces the plus (+) and slash (/) characters with a hyphen (-) and an underscore (_). If you attempt to feed these non-standard variants into a strict decoder, it will reject them. This is a deliberate design choice; guessing the encoding profile can easily conceal underlying data truncation mistakes. To learn how to navigate these validation constraints, read our guide on How to Convert Base64 to Hex Without Mistakes.
Similarly, the hexadecimal parser requires a clean, continuous sequence of lowercase or uppercase digits with exactly two characters per byte. It does not accept prefixes like 0x, spaces, commas, or underscores. A value like 0f is accepted as a single byte, but a standalone f is incomplete and will be rejected. This strict boundary requirement ensures that leading zeros are never lost and the resulting byte count remains perfectly accurate.
Finally, remember that neither Base64 nor hexadecimal is a form of encryption. They are simple, reversible representations of raw binary data. If you convert a sensitive credential, private key, or password, that data is still fully visible to anyone who decodes it. Always keep your sensitive payloads out of shared clipboards, untrusted logs, or public browser sessions to ensure your information remains secure.