Hex to Base32 Converter

Paste a hexadecimal string into this hex to base32 converter and you get back a Base32-encoded string that survives email, QR codes and voice dictation. Under the hood your hexadecimal input becomes raw binary data, which is regrouped into 5-bit chunks and mapped to a 32-character alphabet, so a value like B7E151 turns into W7QVC=== in one click.

How the Hex to Base32 Converter Turns Bytes into Letters

Hex and Base32 are two views of the same bytes. A hexadecimal digit carries 4 bits, so two digits describe one byte. Base32 carries 5 bits per character, which is why the converter has to dissolve your hex digits into one long run of bits and then slice that run again at a different width. Nothing about the value changes; only the grouping does.

Convert Hex to Base32 Step by Step

The conversion steps are the same for every input, short or long:

1. Split the hex string into pairs and write each pair as 8 bits, giving the binary equivalent of every byte.
2. Join all the bits into a single sequence, left to right, with no gaps.
3. Cut that sequence into 5-bit groups, starting from the left.
4. If the last group is short, pad it on the right with zero bits until it reaches five.
5. Look each group up in the Base32 alphabet, where 0 is A, 25 is Z, 26 is 2 and 31 is 7.
6. Append = characters until the output length is a multiple of eight.

Worked Example: B7E151 Becomes W7QVC===

Take the six hex digits B7E151. In binary that is 10110111 11100001 01010001, which is 24 bits. Regrouped into fives it reads 10110 11111 10000 10101 0001, and the last group is one bit short, so the converter adds a zero to make 00010. The five values are 22, 31, 16, 21 and 2.

Five characters is not a full block, so three = signs follow and the finished result is W7QVC===. Feed the same hex to the hexadecimal to base-32 routine in any library and you should see exactly that string.

The converter reads your hexadecimal text as bytes, not as a number, so nothing is trimmed from either end. The value B7E151 also equals 12050769 in decimal, but that figure never enters the Base32 result; only its binary bytes do. A hexadecimal string with a leading zero byte, such as 00B7E151, therefore produces a longer Base32 string than B7E151, because the extra zero byte is real binary content and the converter keeps it.

Why Use an Online Tool for Hexadecimal to Base-32 Encoding

Whenever a hexadecimal dump from a log, a database column or a hardware token has to become text that a person can type, a converter saves real time. Doing the regrouping by hand is fine for three bytes and miserable for thirty. An online tool removes the bit-shifting errors, shows the step-by-step breakdown and lets you copy a clean result. Because the work is client-side, your value does not have to leave the browser.

TOTP Secret Keys and Two-Factor Authentication

The most common reason people convert is TOTP. Authenticator apps expect a Base32 secret, while many servers store the same secret keys as hex. A 20-byte key is 40 hex digits and becomes exactly 32 Base32 characters with no padding, ready to paste into an authentication app. The same step is needed when you migrate TOTP secrets between systems for 2-factor authentication.

QR Codes, API Keys and Email-Safe Text

Base32 shows up wherever a value has to be typed or scanned. A QR code for an authenticator enrolment embeds a Base32 secret, and many API keys use it because the output is email-safe and binary-safe: no punctuation, no symbols that a mail client might rewrite. That makes it a practical choice for data encoding in software development and cryptography workflows.

Hex to Base32 for a 20-Byte Authenticator Secret

A sysadmin is retiring an old login portal and has to re-enrol a service account in an authenticator app. The portal's database stores the shared secret as 40 hex digits: 9C4E7A12D3B8F05E61A7C2D94B0E38F6A15D7C93. The app only accepts Base32, so the first job is to count what is there. Forty digits at 4 bits each is 160 bits, or 20 bytes, which matches the 160-bit secret length that RFC 4226 recommends for HMAC-SHA-1 one-time passwords (its floor is 128 bits).

They paste the string into the converter with padding left on. Twenty bytes is exactly four full 40-bit blocks, so the result is 32 characters and no = signs at all:

TRHHUEWTXDYF4YNHYLMUWDRY62QV27ET

The portal's old export screen shows only the first eight characters, so the sysadmin checks them against the eight characters the converter produced for the first 5 bytes: 9C4E7A12D3 becomes TRHHUEWT, and the two agree. Typing 32 characters in one run is error-prone, so they split the value into eight groups of four (TRHH UEWT XDYF 4YNH YLMU WDRY 62QV 27ET), which the app accepts once the spaces are dropped on entry.

Before deleting anything, they run the Base32 string back through the reverse direction and get all 40 hex digits unchanged. Only then do they enrol the account, read the first six-digit code from the app and compare it with the code the old portal generates for the same 30-second window. The codes match, so the old record can be deleted safely.

Convert Hex to Base32 in Python and JavaScript

If you would rather script the job, every major language has libraries for it. This hex to base32 converter tool follows the same logic as the snippets below, which matter for programming tasks like batch migrations.

Python Example

Python ships with the encoder in its standard library, so the whole conversion is two calls:

import base64
print(base64.b32encode(bytes.fromhex("B7E151")).decode())  # W7QVC===

JavaScript Example

In JavaScript you can write the logic directly, which also shows the 5-bit regrouping clearly:

function hexToBase32(hex) {
  const A = "ABCDEFGHIJKLMNOPQRSTUVWXYZ234567";
  let bits = "";
  for (const h of hex.match(/../g)) bits += parseInt(h, 16).toString(2).padStart(8, "0");
  let out = "";
  for (let i = 0; i < bits.length; i += 5)
    out += A[parseInt(bits.slice(i, i + 5).padEnd(5, "0"), 2)];
  while (out.length % 8) out += "=";
  return out;
}