🔢 Base32/58/85 Encoder/Decoder

🎯
⚙️
📝
ℹ️
Base Details:
RFC 4648 standard, case-insensitive (A-Z, 2-7)
Bitcoin alphabet, no ambiguous chars (0OIl excluded)
ASCII85, 85 printable ASCII characters
Character Set Size: characters
📤
📊
Input: chars
Output: chars
Ratio:
Efficiency: %
⚠️

ℹ️ About Base32/58/85 Encoding

Base32, Base58, and Base85 encoding convert bytes into printable text alphabets so data can be copied, stored, or embedded in systems that are safer with plain ASCII characters. These formats are reversible encodings, not encryption: anyone with the encoded value and the right alphabet can decode the original data.

Common use cases:

  • Encode identifiers that must survive case-insensitive systems, DNS labels, QR codes, or manual entry.
  • Decode Base32 secrets and tokens when checking interoperability with systems that follow RFC 4648.
  • Create Base58 strings for wallet-style identifiers, short invite codes, or values that should avoid visually ambiguous characters.
  • Use Base85 when you need a denser text representation of binary-like data than Base64 or Base32.

Technical details:

  • Base32 uses the uppercase alphabet A-Z and 2-7, groups data into 5-bit values, and pads output with = to an 8-character boundary. This follows the Base32 alphabet defined by RFC 4648.
  • Base58 uses the Bitcoin alphabet 123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz. It omits 0, O, I, and l, matching the alphabet used by the Bitcoin Core Base58 implementation.
  • Base85 encodes each complete 4-byte group into 5 printable characters, using an ASCII85-style alphabet from ! through u. Adobe's PDF reference documents the ASCII85Decode filter, while RFC 1924 is a separate Base85 alphabet for compact IPv6 text representation.

Examples: encoding Hello World produces JBSWY3DPEBLW64TMMQ====== in Base32, JxF12TrwUP45BMd in Base58, and 87cURD]i,"Ebp7 in Base85.

Limitations:

  • Encoding does not hide or protect data. Do not treat Base32, Base58, or Base85 output as a secret.
  • Base58 here is raw Base58; it does not add the version byte or checksum used by Base58Check addresses.
  • Base85 variants are not interchangeable. This tool does not add Adobe <~ ~> wrappers, the ~> end marker, or the z all-zero shorthand.
  • Decoded bytes are displayed as UTF-8 text, so arbitrary binary data may show replacement characters if it is not valid text.

Privacy note: this page processes text in your browser for interactive use. Avoid pasting private keys, production secrets, access tokens, or sensitive personal data into any online encoder unless you are comfortable with the surrounding browser and network environment.

API Usage Example:

POST /api/tools/encoding-decoding/basex
Content-Type: application/json

{
    "text": "hello",
    "operation": "encode",
    "base": "32"
}
Ready