Base58 Encoder & Decoder

Base58 is a binary-to-text encoding scheme that uses 58 alphanumeric characters — deliberately excluding easily confused characters like 0 (zero), O (capital o), I (capital i), and l (lowercase L). It was popularized by Bitcoin for wallet addresses to make them human-readable and less error-prone when typed manually. Compared to Base64, Base58 trades a small increase in output length for significantly better usability in contexts where humans need to read or transcribe the encoded data.

Common use cases include: Bitcoin addresses, IPFS content identifiers, Ripple addresses, and various cryptocurrency-related tools.

Base64 uses 64 characters (A-Z, a-z, 0-9, +, /) and is optimized for machine processing with minimal overhead (~33% larger than raw bytes). Base58 uses only 58 characters, removing 0, O, I, l, +, and / — making it more human-friendly but slightly less efficient (~37% larger than raw bytes).

In short: Base64 is faster for machines; Base58 is friendlier for humans. That's why Bitcoin addresses use Base58 — nobody wants to confuse a zero with the letter O when sending cryptocurrency.

The standard Bitcoin Base58 alphabet, in order, is:
123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz

Notice what's missing: 0 (zero), O (capital O), I (capital I), and l (lowercase L). The digit 1 represents the value zero in Base58, which is why Bitcoin addresses often start with '1'.

Yes, but with an important caveat. Bitcoin addresses use Base58Check — which is Base58 encoding with an added 4-byte checksum (double SHA-256 hash). This tool decodes the raw Base58 portion, giving you the underlying bytes (including any version byte and checksum). It does not validate the Bitcoin checksum.

To verify a Bitcoin address's validity, you'd need a dedicated Bitcoin address validator that checks the Base58Check integrity. This tool is ideal for general-purpose Base58 encoding/decoding tasks.

Base58 encodes raw binary data, not necessarily text. If the original data wasn't valid UTF-8 text (e.g., it's a cryptographic hash, a Bitcoin address's raw bytes, or random binary data), decoding it as text will produce garbled characters.

For non-text data, switch the output format to Hex — this will show you the raw bytes as a hexadecimal string, which is the most common way to inspect binary data. Only use "Text" mode when you know the original encoded data was a text string.

No. Base58 is an encoding scheme, not an encryption algorithm. It provides zero security — anyone can decode Base58 data back to its original form using a tool like this one.

Think of Base58 as a way to represent data in a compact, readable format (like how hexadecimal or Base64 work). For protecting sensitive information, always use proper encryption algorithms such as AES, ChaCha20, or RSA. Never rely on encoding alone for security.

Besides Bitcoin, Base58 is used by:
• IPFS — Content identifiers (CIDs) often use Base58
• Ripple (XRP) — Wallet addresses use a Base58 variant
• Flickr — Short photo IDs use Base58
• YouTube — Video IDs are essentially Base58-like
• Various altcoins — Many cryptocurrencies forked from Bitcoin use Base58 addresses
• Short URL services — Some use Base58 to generate compact, unambiguous IDs