Base32 to Hex Converter

The tool validates your input against the standard RFC 4648 Base32 alphabet (A-Z, 2-7, plus = padding), bit-packs the 5-bit values back into 8-bit bytes, and renders each byte as its 2-digit hexadecimal equivalent.

No. The tool runs entirely client-side – no backend requests, no APIs, no logging. Everything is processed directly in your browser, and after the page loads you can keep working with the network disconnected.

The decoder auto-pads with = up to the next multiple of 8 before decoding. That means you can paste an unpadded Base32 string (common in URLs or compact formats) and still get correct bytes out.

Yes, 100% free with no cap on input length or number of decodes. No sign-up, no premium tier, no watermark.

No. The RFC 4648 Base32 alphabet is officially uppercase, but the tool accepts either case and canonicalises to uppercase before decoding – so jbsw and JBSW decode identically.

Yes. HTML, CSS, and JavaScript are self-contained. Once the page has loaded, you can turn off Wi-Fi and the tool keeps working.

The inline error names the first offending character (for example “Invalid Base32 character: 8 – expected A-Z, 2-7, or = padding”) instead of producing garbage bytes. Fix the character and the decode runs again.

Base32 uses 32 case-insensitive characters, avoids visually similar digits (no 0, 1, 8, 9), and is safe for URLs, filenames, and voice dictation. It is the standard encoding for TOTP OTP secrets (Google Authenticator) and DNS labels.

Pick the JSON-array separator with an optional 0x prefix to produce a paste-ready JavaScript/Python/Rust byte array. For a hex dump aligned to a grid, leave the defaults (space-separated, lowercase, zero-padded) – that matches xxd output.

Use the sibling Hex to Base32 converter. It accepts the same space/comma/newline separators, so any hex produced here pastes cleanly into the reverse direction.