CodesBeautify

Base64 to Hexadecimal Converter

Turn a Base64 string into the hexadecimal byte values it actually represents.

Base64
Hexadecimal
Runs locally in your browser

About the Base64 to Hexadecimal Converter

Base64 hides the bytes behind an alphabet of 64 printable characters, which is exactly what you do not want when you are checking a file signature, comparing a digest against a reference value, or pasting a payload into a C array. This converter decodes the Base64 back to raw bytes and prints each one as two hexadecimal digits, so U2hpcA== becomes 53 68 69 70.

Six separator styles cover the usual destinations. Continuous digits suit a checksum comparison, spaces suit a hex dump you read by eye, colons match the notation used for MAC addresses and certificate fingerprints, and the 0x and \x styles paste straight into source code. Uppercase digits are one checkbox away for people who follow the RFC style used in specifications.

A leading data:...;base64, prefix is stripped automatically, padding is repaired when it is missing, and both the standard and URL-safe alphabets are understood, so a JWT segment works without editing. If the string contains a character outside the alphabet the tool names it rather than guessing. The byte count in the status line is a quick sanity check: a SHA-256 digest should read 32 bytes, an MD5 digest 16. Go the other direction with Hex to Base64.

How to use

  1. Paste the Base64 string into the left pane, with or without a data URI prefix.
  2. Pick a separator that matches where the hex is going: colons for fingerprints, 0x for code.
  3. Tick Uppercase digits if your reference value uses capitals, then copy the result.

Common questions

How many hex digits should I expect?
Two per byte. Three Base64 characters carry roughly two bytes, so a 44 character Base64 string with padding usually gives 64 hex digits.
Can I paste a JWT segment?
Yes. URL-safe characters and missing padding are both handled, so a header or payload segment converts without editing it first.
Why does my hash not match the reference?
Check the case and the separator first. The digits are identical either way, so compare the continuous lowercase form on both sides.
Does it work on binary data such as an image?
Yes. The bytes are never interpreted as text, so image, archive and certificate data all convert cleanly.