Base32 Encode/Decode client-side ?
How to use Base32 Encode/DecodeBase32 encodes binary data with a 32-character set (letters A-Z and digits 2-7), case-insensitive, following RFC 4648. It's more readable than Base64 and compatible with systems that don't distinguish upper and lower case: 2FA TOTP keys, some identifiers, file names. Paste text to encode it, or a Base32 string to decode it. Everything happens in your browser
?
Base32 encodes binary data with a 32-character set (letters A-Z and digits 2-7), case-insensitive, following RFC 4648. It's more readable than Base64 and compatible with systems that don't distinguish upper and lower case: 2FA TOTP keys, some identifiers, file names. Paste text to encode it, or a Base32 string to decode it. Everything happens in your browser
Base32 encodes binary data with a 32-character set (letters A-Z and digits 2-7), case-insensitive, following RFC 4648
How to use Base32 Encode/Decode
Base32 encodes binary data with a 32-character set (letters A-Z and digits 2-7), case-insensitive, following RFC 4648. It's more readable than Base64 and compatible with systems that don't distinguish upper and lower case: 2FA TOTP keys, some identifiers, file names. Paste text to encode it, or a Base32 string to decode it. Everything happens in your browser
Frequently asked questions
How does it differ from Base64?
Base32 uses 32 characters instead of 64; it's longer but case-insensitive and more readable, which suits manual entry (TOTP codes, for example)
What is the '=' character for?
It's the padding that completes the last group to reach a length that is a multiple of 8