Base58 Encoder / Decoder

How to use

1. 1Pick Encode or Decode at the top, then choose the alphabet that matches your data: Bitcoin / IPFS for crypto and IPFS hashes, Ripple for XRP, Flickr for short URLs.
2. 2Toggle Base58Check on for Bitcoin addresses and WIF keys. The encoder will append a 4-byte double-SHA-256 checksum, and the decoder will verify it.
3. 3When encoding, pick UTF-8 text or Hex bytes for the input. Hex lets you encode arbitrary binary like 20-byte hashes without character-set issues.
4. 4When decoding, pick UTF-8 text or Hex bytes for the output. The tool falls back to hex automatically when the bytes are not valid UTF-8.
5. 5Use a quick-conversion preset to load a worked example (Hello, World!, a Bitcoin genesis address, a Ripple-encoded payload) and confirm the algorithm matches your expectations.
6. 6Click Copy Base58 (or Copy output for decode) to grab the result. Click Clear to reset the input. Switch directions instantly with the Swap button.

About this tool

Base58 Encoder / Decoder converts between raw bytes and Base58 entirely in your browser, with first-class support for the three alphabets you actually encounter in the wild. Bitcoin / IPFS Base58 (the original alphabet: 123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz) is used by Bitcoin addresses, WIF private keys, IPFS CIDv0 hashes, ActivityPub short IDs, and many crypto wallet QR codes. Ripple Base58 reshuffles the same 58 characters so XRP Ledger account IDs always begin with the letter r. Flickr Base58 places lowercase letters before uppercase and is used by Flickr short URLs and several short-link services. Encoding accepts either UTF-8 text or hex byte sequences, so you can encode a string like Hello, World! or a 20-byte hash without ambiguity. Decoding can render the result as UTF-8 text (with a graceful hex fallback when the bytes are not valid UTF-8) or as hex bytes. Base58Check, the variant used by Bitcoin addresses and WIF keys, is available as a one-click toggle. When enabled, the encoder appends a 4-byte checksum derived from a double SHA-256 of the payload, and the decoder verifies that checksum and reports a clear mismatch when a typo would silently corrupt the address. The SHA-256 computation uses the Web Crypto API built into every modern browser, so there are no external dependencies. The leading-zero rule is handled correctly in both directions: each leading zero byte in the input becomes a leading 1 in the output (or the first character of the chosen alphabet), and the byte count is preserved exactly on the roundtrip. The decoder ignores whitespace in pasted input and pinpoints the position of the first invalid character with an alphabet-specific message so you can spot a misread O for 0 or l for 1 at a glance. Useful for inspecting Bitcoin addresses, validating Solana keys (which use the Bitcoin alphabet), decoding IPFS CIDv0 hashes back to their multihash bytes, building or analyzing short-link payloads, debugging Ripple wallet integrations, and any developer task that touches the Bitcoin or IPFS encoding standards. Everything runs locally on your device. Nothing you paste here is uploaded, logged, or shared.

Free to use. Works in your browser. No signup, no login.