Base32
Encode any file to Base32 text (RFC 4648) or decode Base32 back to bytes. Pairs with the base64 tool.
About Base32
Base32 encodes any file or text into RFC 4648 Base32 and decodes Base32 strings back into the original bytes. Reach for it when a system expects Base32 rather than Base64, such as TOTP secrets, DNS records, or case-insensitive identifiers. The conversion runs locally in your browser, so the bytes you encode never touch a server.
- Category
- convert
- Input
- Accepts: */*.
- Output
- Outputs: text/plain.
- Cost
- Free, runs in your browser
- Memory
- low
Common uses
- Encode a shared secret into the Base32 form an authenticator app expects
- Decode a Base32 string from a config file back to its raw bytes to inspect them
- Produce a case-insensitive, URL-safe encoding for an identifier
- Convert binary data into Base32 for a system that rejects Base64's mixed case
- Verify that a Base32 value round-trips cleanly before committing it to a record
- Hand off Base32 output to a colleague who only has copy-paste access
Frequently asked questions
What is the difference between Base32 and Base64?
Base32 uses a 32-character alphabet (A-Z and 2-7) that is case-insensitive and avoids ambiguous characters, at the cost of longer output. Base64 is more compact but case-sensitive. Use Base32 when case-insensitivity matters.
Which Base32 standard does this use?
RFC 4648, the standard alphabet used by TOTP secrets and most tooling.
Can I encode a binary file, not just text?
Yes. It accepts any file and encodes the raw bytes, so images, keys, or arbitrary binaries all work.
Does my data get uploaded?
No. Encoding and decoding both run in your browser; nothing is sent anywhere.
What if my Base32 input is malformed?
Decoding expects valid RFC 4648 characters. Stray characters or bad padding will cause the decode to fail rather than produce garbage.
Keywords
- base32
- encode
- decode
- rfc4648
- binary
- text