64 Base64Toolkit
Language:

Base64 to Hex

See the raw bytes behind any Base64 string. Live, bidirectional, 100% client-side.

Base64 and hexadecimal — two views of the same bytes

Base64 and hex are both text representations of binary data. Converting between them never changes the underlying bytes — it just changes how you look at them. Hex is the format of choice for debugging: two characters per byte, space-separated, so you can spot a stray 0A newline at the end of a secret, recognize a 25 50 44 46 PDF header, or compare checksums byte by byte. This converter works in both directions: edit either side and the other updates live. Hex input is flexible — spaces, colons, 0x prefixes and line breaks are all accepted.

Going the other way from a hex dump you found in logs? Use Hex to Base64, or decode the text with Base64 Decode.

Frequently Asked Questions

How do I convert Base64 to hex?

Paste the Base64 string into the left box. Each decoded byte is shown as a two-digit hexadecimal value in the right box, live as you type. Editing the hex side converts back to Base64.

Why view Base64 as hex?

Hex shows you the exact bytes. That is how you spot file signatures (89 50 4E 47 = PNG), invisible characters like trailing newlines (0A) that break Kubernetes secrets, BOM markers (EF BB BF), and encoding bugs that are impossible to see as text.

What is the difference between hex and Base64?

Both represent binary as text. Hex uses 2 characters per byte (100% overhead) and is easy for humans to read byte-by-byte; Base64 uses ~1.33 characters per byte (33% overhead) and is more compact for transport. Hashes and MAC addresses are usually hex; transported payloads are usually Base64.

Related Tools