43 characters · 9 words · 43 bytes (UTF-8)
Output will appear here
Click in the output to select all text
43 characters · 9 words · 43 bytes (UTF-8)
Output will appear here
Click in the output to select all text
Encode text to Base32 format (RFC 4648) and decode Base32 strings.
URL-safe Base64 encoding and decoding without padding or special URL characters.
Encode text to hexadecimal byte representation and decode hex back to ASCII.
Generate cryptographically secure random bytes in Hex, Base64, and Uint8 format.
This Base58 tool encodes text into Bitcoin-style Base58 format and decodes Base58 strings back into their original bytes, all inside your browser. Base58 strips out visually confusing characters — 0, O, I, and l — along with symbols like + and /, which is exactly why Satoshi Nakamoto chose it for Bitcoin addresses and why it's since spread to other cryptocurrencies, IPFS content identifiers, and short URL-friendly IDs. Blockchain developers verifying wallet address encoding, engineers implementing Base58Check, and anyone curious how crypto addresses are formatted will get accurate results here. All encoding and decoding logic runs locally as JavaScript — nothing you type, including private data or test keys, is ever sent to a server or logged anywhere. There's no signup, no rate limits, and conversions happen instantly. If your project uses standard Base64 or Base32 instead, check out this platform's dedicated tools for those formats too. Scroll down to try Base58 encoding or decoding on your own data.
Base58 is best known for encoding Bitcoin and other cryptocurrency addresses, but it's also used for IPFS content hashes and any identifier meant to be typed accurately by humans.
Base58 removes visually ambiguous characters (0, O, I, l) and non-alphanumeric symbols, reducing the chance of transcription errors when addresses are copied by hand.
No, Base58Check adds a version byte and a checksum before Base58-encoding the result, which is what Bitcoin addresses actually use to detect typos.
No, it's a reversible encoding, not encryption — anyone can decode a Base58 string back to its original bytes without any secret key.
Yes, any byte sequence, including plain text or hex data, can be encoded to Base58 and decoded back exactly.
Base58 excludes 0 (zero), O (capital o), I (capital i), l (lowercase L), and the symbols + and / to avoid visual confusion.
This tool performs standard Base58 encoding/decoding; for full address validation you'd also need to verify the appended checksum bytes separately.