How to encode or decode text
Choose Encode to convert text to Base32, or choose Decode to convert Base32 back to text. The output updates automatically in the read-only result box.
Convert text step by step
- Enter text or load it with Upload or Drop file.
- Select Encode or Decode when you know the direction.
- Review the output as it updates automatically.
- Use Copy or Download to retrieve the result.
How Auto-detect works
Auto-detect is a heuristic. It removes whitespace, checks the RFC 4648 length and padding rules, decodes the value, and confirms that re-encoding produces the same canonical Base32 value. Plain text such as HELLO is therefore treated as text to encode.
Some short strings can still be valid Base32 by coincidence. Choose Encode or Decode directly when you know the direction.
Upload and decode a text file
Use Upload or Drop file to load a local file as text. The inspected implementation does not define binary conversion, a file-size limit, or an accepted file-type list.
Download or copy the result
Use Copy to copy the current output. Use Download to save it as a text/plain file named base32-encoder-decoder-output.txt. The interface does not provide a filename control.
Input rules and error behavior
Encode uses TextEncoder to create UTF-8 bytes, then produces uppercase Base32 using A-Z and 2-7. Output may end with = padding until its length is a multiple of 8. Decode accepts upper- or lowercase letters, removes whitespace and trailing = characters, and uses TextDecoder to display the decoded bytes as UTF-8. Invalid UTF-8 bytes may appear as replacement characters.
Invalid Base32 characters such as 0, 1, 8, or 9 cause an error. Empty input clears the output and status. A conversion error also clears the output and displays the message in b32Status.
Privacy and page-wide limitations
The conversion code processes input in the browser. The page also includes shared scripts and analytics-related assets, so the inspected tool code does not establish how every page-level script handles input. Do not treat this as a page-wide privacy guarantee.
The local implementation does not define a file-size limit, file-type restriction, or configurable download filename.
Frequently Asked Questions (FAQs)
What is Base32 encoding?
Base32 is a binary-to-text encoding scheme defined in RFC 4648. This tool applies its standard A-Z and 2-7 alphabet to text bytes, with output that may include trailing = padding.
How is Base32 different from Base64?
Base32 uses 32 symbols and packs 5 bits per character; Base64 uses 64 symbols and packs 6 bits per character. Base64 can be shorter, while this tool accepts Base32 letters without regard to case. The formats are not interchangeable.
Why not just use hexadecimal or URL encoding instead?
They serve different purposes. Hexadecimal represents values with 0-9 and A-F, while URL encoding escapes text for use in URLs. Choose this tool when the value you have is text that needs Base32 encoding or decoding. The output still needs to meet the rules of whatever system receives it.
Is my data safe when I use this tool?
The conversion code processes input in the browser. Because the page also includes shared scripts and analytics-related assets, the inspected tool code does not establish how every page-level script handles input. Do not treat this as a page-wide privacy guarantee.