Esoteric & Radix Encoders
Encode and decode Base32, Base58 (Bitcoin), Ascii85 (Adobe), Punycode IDN domains, and Uuencode in your browser.
Private by architecture:
All processing is 100% client-side memory. Your data never leaves this browser tab.
Quick Presets:
Plaintext / Input
0 charsUTF-8
Encoded / Output
0 charsResult
About This Tool
Convert and decode specialized binary-to-text radices including Base32 (RFC 4648), Base58 (Bitcoin/IPFS), Ascii85 (Adobe PostScript/Git), Punycode (RFC 3492 international domain names), and classic Unix Uuencode.
Ideal for blockchain engineers, security researchers, DevOps administrators, and internationalized domain name managers who need offline encoding precision.
Supports bidirectional encoding and decoding with automatic delimiter stripping and character set validation.
Key Features
- Base32 (RFC 4648): Encode and decode standard 32-character alphabets with or without padding characters.
- Base58 (Bitcoin / IPFS): Binary-to-text encoding avoiding visually ambiguous characters (0, O, I, l).
- Ascii85 (Adobe / Git): 5-character encoding for 4-byte quadwords with zero-compression support.
- Punycode & IDN Domains: Translate internationalized Unicode domain names to and from ASCII xn-- labels.
- Uuencode (Classic Unix): Generate and unpack historical Unix uuencoded file attachments.
Frequently Asked Questions
Why does Base58 omit characters like 0, O, I, and l?
Satoshi Nakamoto designed Base58 for Bitcoin addresses specifically to eliminate visual confusion between the number zero (0) and capital O, as well as capital I and lowercase l, making cryptocurrency addresses easier and safer to transcribe by hand.
How is Ascii85 more efficient than Base64?
Base64 expands binary data by 33% (4 characters for every 3 bytes). Ascii85 expands data by only 25% (5 characters for every 4 bytes), offering a significant bandwidth and storage efficiency gain.
Are my keys or domains transmitted to external APIs?
No. All radix encodings and conversions run 100% locally in your browser memory.
