What this tool does
Converts text or bytes to/from Base32, Base58, and Base85—useful for compact representations in different ecosystems.
This page focuses on practical, step‑by‑step usage for **Base32/Base58/Base85 Converter**, with clear examples and common pitfalls.
When you should use it
Use it when dealing with IPFS/Base58 identifiers, legacy encodings, or when you need printable output with fewer ambiguous characters.
How to use
- Pick the base variant (32/58/85).
- Paste input and choose direction.
- Confirm the alphabet variant and copy result.
Quick example
Example: Convert a hex string to Base58 to match an address/identifier format used by a library.
Notes
Different Base58 alphabets exist; keep the same alphabet end-to-end.
Base32/Base58/Base85 Converter
Convert between multiple base encoding formats used in cryptocurrencies, file encoding, and data serialization
Encoding Formats
Base32
Character Set: A-Z, 2-7, = (padding)
Uses: DNSSEC, TOTP, file hashes
Example: JBSWY3DP (Hello)
Base58
Character Set: 1-9, A-H, J-N, P-Z, a-k, m-z
Uses: Bitcoin addresses, IPFS
Example: 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa
Base85
Character Set: 0-9, A-Z, a-z, !#$%&()*+-;<=>?@^_`{|}~
Uses: PDF, PostScript, IPv6
Example: 87cURD]i,"Ebo80 (Hello World!)
About Base Encoding Formats
Base encoding schemes convert binary data into text formats that are safe for transmission and storage. Each format has specific use cases and characteristics.
Base32 Characteristics
- Case Insensitive - Easy for human transcription
- No Special Characters - Safe for file systems
- 33% Size Increase - Less efficient than Base64
- Common Uses: Two-factor authentication, DNS records, file hashes
Base58 Characteristics
- No Ambiguous Characters - Removes 0, O, I, l
- Human Readable - Designed for manual entry
- Bitcoin Standard - Used for cryptocurrency addresses
- Common Uses: Bitcoin addresses, IPFS hashes, short URLs
Base85 Characteristics
- High Efficiency - 25% size increase (better than Base64)
- Complex Character Set - Uses more special characters
- PDF Standard - Used in PostScript and PDF files
- Common Uses: PDF documents, Git patches, IPv6 addresses
FAQ
What’s the difference between encoding and encryption on this page?
Encoding changes representation (for transport/compatibility). Encryption protects confidentiality with a key. Use encryption when you need secrecy.
What should I do if the input fails to decode/parse?
Start by checking for missing padding, wrong alphabet/variant, or extra whitespace. If the data looks multi-layered, try decoding step-by-step (e.g., URL decode → Base64 decode).
Is it safe to paste sensitive data here?
For best security, avoid pasting real secrets (private keys, live tokens, seed phrases). Use test data or work offline, especially for anything that could grant access or move funds.