Base32 is a binary-to-text encoding scheme that represents binary data using a set of 32 printable ASCII characters. Each Base32 character encodes exactly 5 bits of information. It is often used in contexts where data needs to be case‑insensitive and human‑readable, such as in QR codes, secret keys, and DNS labels. Standard Base32 (RFC 4648) uses the alphabet A-Z and 2-7.

Hexadecimal uses 16 symbols (4 bits per character), Base32 uses 32 symbols (5 bits per character), and Base64 uses 64 symbols (6 bits per character). Base32 produces shorter strings than Hex, but longer than Base64. Unlike Base64, standard Base32 is case‑insensitive and avoids visually ambiguous characters (like 1, l, 0, O), making it safer for manual transcription.

A valid custom alphabet must contain exactly 32 unique characters. When Case Sensitive is disabled (default), the alphabet is treated case‑insensitively: all input and alphabet characters are compared in uppercase, and duplicates after case folding are not allowed. If you enable case sensitivity, A and a become distinct symbols, which lets you create more densely packed encodings.

Type or paste your Base32 string into the left text area. The equivalent hexadecimal value instantly appears in the right text area. The conversion respects your selected alphabet and case‑sensitivity setting. Any invalid character will be flagged, and you can copy the result with one click.

When encoding hexadecimal to Base32, enabling Add Padding (RFC 4648) appends the appropriate number of = characters so that the output length becomes a multiple of 8. This follows the official RFC 4648 specification. Padding is ignored during decoding. For most custom applications, you can leave it off.