What Base32 alphabet does this tool use?

The tool uses the standard RFC 4648 Base32 alphabet: the 26 uppercase letters A–Z plus the digits 2–7. This is the same alphabet used by TOTP/HOTP authenticator apps (Google Authenticator, Authy, etc.).

Does Base32 output include padding?

Yes. RFC 4648 requires that the output length be padded with "=" characters to a multiple of 8. You can strip the padding if your target system does not require it.

Is the hex input case-sensitive?

No. Both uppercase (A–F) and lowercase (a–f) hex digits are accepted. The output is always uppercase Base32 per RFC 4648.

What happens if I enter an odd-length hex string?

An odd number of hex digits cannot represent a whole number of bytes. The tool will display an inline error and ask you to check your input.

Can I decode Base32 back to hex with this tool?

Yes. Use the "Base32 to Hex" direction. Paste a valid RFC 4648 Base32 string (with or without padding) and the tool outputs the original hex bytes.

Is any data sent to a server?

No. All encoding and decoding runs entirely in your browser using JavaScript. Nothing is transmitted over the network.

Hexadecimal to Base32 Converter

Name: Hexadecimal to Base32 Converter
Availability: InStock
Author: Nham Vu

Convert hexadecimal strings to RFC 4648 Base32 encoding — or reverse from Base32 back to hex — instantly in your browser.

Hexadecimal Input

Quick Samples

Base32 Output

Include Padding (=)

RFC 4648 requires padding; disable only when your target system does not need it.

Copied!

Summary

Convert hexadecimal strings to RFC 4648 Base32 encoding — or reverse from Base32 back to hex — instantly in your browser.

How it works

Paste or type a hexadecimal string into the Hex input field.
The tool decodes the hex bytes into raw binary data.
Each group of 5 bits is mapped to one of the 32 RFC 4648 characters (A–Z, 2–7).
Padding characters (=) are appended so the output length is a multiple of 8.
For the reverse direction, switch to Base32 input and the tool decodes Base32 to hex.

Use cases

Encode cryptographic key material from hex into Base32 for use in TOTP/HOTP secrets.
Convert hex-encoded identifiers to the Base32 format required by certain APIs.
Verify that a Base32-encoded value matches a known hex byte sequence.
Debug encoding pipelines by round-tripping hex through Base32 and back.
Generate Base32 tokens from random hex for URL-safe identifiers.
Inspect binary data stored in hex by viewing its Base32 representation.

Frequently Asked Questions

Last updated: 2026-06-13 · Reviewed by Nham Vu