3️⃣ Base32 Encoder / Decoder
Base32 encodes bytes using 32 case-insensitive characters (A–Z, 2–7) — encode or decode instantly, with the base32hex variant.
6 chars → 16 Base32 chars (RFC 4648)
How the base32 encoder / decoder works
Encoding groups the UTF-8 bytes into 5-bit chunks and maps each to one of 32 characters — A–Z and 2–7 in the standard alphabet (RFC 4648), padding to a multiple of 8 with =. Base32 is case-insensitive and avoids easily-confused characters (no 0/O or 1/I), which is why it is used where humans type or read the value: TOTP two-factor secrets, some file hashes and identifiers. Decoding accepts either alphabet and tolerates missing padding and whitespace.
Base32 is encoding, not encryption — it is fully reversible with no secrecy. Compared with Base64 it is ~20% larger (5 bits per character vs 6) but case-insensitive and safer to transcribe by hand or read aloud. If you are working with a two-factor authentication secret, it is Base32 — pair this with the TOTP generator.
Frequently asked questions
What is Base32 used for?
Anywhere a value must survive being typed, read aloud or written down: TOTP/2FA secrets, some content hashes and identifiers. Its case-insensitive alphabet (A–Z, 2–7) avoids characters that look alike, unlike Base64.
How is Base32 different from Base64?
Base32 uses 32 characters (5 bits each) and is case-insensitive; Base64 uses 64 (6 bits) and is case-sensitive. Base32 output is about 20% larger but far easier to transcribe without errors.
What is the base32hex variant?
An alternative alphabet (0–9 then A–V) defined in RFC 4648 §7 that preserves sort order of the encoded data. Pick it only if your target system specifies it; most uses want the standard alphabet.
Is Base32 encryption?
No — it is a reversible transport encoding with zero secrecy. Anyone can decode it. Encrypt first if you need confidentiality.
Is my text uploaded?
No — encoding and decoding run entirely in your browser. Nothing is transmitted and it works offline.