BASE32 / 58 / 85
Multi-base encoding, Base32 / 58 / 85 both ways.
Convert between text and Base32, Base58 and Base85. Base32 is common for keys and DNSSEC, Base58 for Bitcoin addresses (no ambiguous chars), Base85 (Ascii85) for PDF / Git binary patches. All computed locally with standard algorithms.
Everything runs locally in your browser
What is this?
These encodings represent binary bytes as printable characters: Base32 uses 32 chars in 5-bit groups (RFC 4648); Base58 uses a 58-char alphabet without 0/O/I/l via big-integer conversion, preserving leading zeros; Base85 (Ascii85) encodes every 4 bytes as 5 chars with z for all-zero groups — more compact than Base64.
FAQ
How is Base58 different from Base64?
Base58 drops ambiguous chars (0, O, I, l) and the +, / and = padding, converts as a big integer and preserves leading zero bytes — better for human transcription (e.g. Bitcoin addresses). Base64 uses fixed 6-bit groups and is more general.
Decode errors or garbled output?
Make sure the encoding and direction are correct and the characters belong to that alphabet. Base85 decoding ignores whitespace and accepts <~ ~> wrappers; if the bytes are not valid UTF-8, decoded text may show replacement chars.
Is anything uploaded?
No. Everything runs in your browser; nothing is sent to a server.