Base58 and Base32 Converter

The address-class encodings.

Paste an address, a content id, hex, or plain text and see the same bytes in every encoding. Base58 tells you what kind of address a string is and shows, step by step, how its checksum catches a typo.

Zero retention: your data never leaves this browser. Verify it yourself in DevTools

Loading the toolbox.

About Base58

How Can You Verify That Nothing Leaves This Browser?

You do not have to take our word that your data stays here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.

  1. Open your browser developer tools with F12, or Cmd+Option+I on a Mac, and select the Network tab.
  2. Reload the page and let it finish. You will see the page's own files, its web fonts, and one anonymous page-view request. Nothing has been typed yet, so none of them can contain your data.
  3. Click the clear icon in the Network tab so that the log is empty.
  4. Paste an address or a value and copy one of its encodings.
  5. Look at the Network tab again. It is still empty. For extra proof, turn on offline mode after the page loads and the tool keeps working.

Only two things can add a line to that log, and neither carries your data. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.

The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint, so a coding mistake could not quietly send your data elsewhere.

What Is Base58?

Base58 writes bytes using 58 characters: the digits 1 to 9 and the upper- and lower-case letters, minus the four that are easy to confuse when copied by hand: zero, capital O, capital I, and lower-case l. It also has no punctuation, so a Base58 string is selected whole by a double-click and never breaks a URL. Bitcoin introduced it for addresses, and IPFS, Solana, and many other systems use the same alphabet. Flickr and Ripple use the same 58 characters in a different order, and the converter supports both.

Unlike Base64, which encodes every three bytes as four characters, Base58 treats the whole input as one large number and rewrites it in base 58, so it has no padding. Leading zero bytes would vanish in that conversion, so each one is written as a leading 1. That is why a Bitcoin address with version byte zero always starts with 1, and why the burn address of twenty zero bytes is a long run of ones.

How Does Base58Check Catch Typos?

Base58Check, the format of Bitcoin legacy addresses and WIF keys, adds a checksum before encoding:

  1. Start with a version byte that says what the data is, such as 0x00 for a mainnet pay-to-public-key-hash address.
  2. Append the payload, for an address the 20-byte hash of a public key.
  3. Hash version plus payload with SHA-256, then hash the result again with SHA-256.
  4. Append the first four bytes of that double hash, and encode everything in Base58.

A wallet decodes the string, recomputes the double hash, and refuses the address if the four bytes differ. The checksum lab on this page shows the version byte, the payload, the embedded and recomputed checksums, and what happens when one character is changed. A random error gets past a four-byte checksum about once in 4.3 billion tries. Newer Bech32 addresses (bc1...) go further: their BCH checksum is guaranteed to detect up to four wrong characters, and Base58 can recognize and verify those too.

Which Address Shapes Does It Recognize?

  • Bitcoin legacy addresses: P2PKH (starts with 1) and P2SH (starts with 3) on mainnet, and m, n, or 2 on testnet, with the Base58Check checksum verified.
  • Bitcoin SegWit addresses: Bech32 for version 0 (P2WPKH and P2WSH) and Bech32m for Taproot, checked against BIP173 and BIP350, including the rule that each witness version must use the right variant.
  • Keys: WIF private keys, xpub and xprv extended keys, and their ypub, zpub, and testnet forms. Private ones are flagged in red.
  • IPFS content ids: CIDv0 strings that start with Qm, decoded to their sha2-256 multihash, and CIDv1 strings in multibase base32 such as bafy..., decoded to their codec and digest.
  • 32-byte Base58 values: the shape of an Ed25519 public key, as used by Solana addresses, noted with the warning that this shape has no checksum.

Anything else is still converted. The detection is a reading of the bytes, not a lookup: Base58 never contacts a blockchain, an explorer, or an IPFS gateway, and it cannot tell you whether an address has ever been used.

How Do the Base32 Variants Differ?

  • RFC 4648 Base32: A to Z and 2 to 7, padded with equals signs. It is the format of TOTP secrets and of many case-insensitive identifiers.
  • Base32hex: 0 to 9 and A to V. Encoded values sort in the same order as the bytes, which is why DNSSEC uses it for NSEC3 records.
  • Crockford Base32: digits and letters without I, L, O, and U, with no padding. It is used by ULID. When decoding, I and L are read as 1 and O as 0, and hyphens are ignored.

Base64 and Base64url are shown alongside: the same 64-character scheme, with + and / replaced by - and _ in the URL-safe form, which is also what JWTs use.

When Should You Use Which Encoding?

  • Hex for logs, hashes, and debugging, where reading the bytes matters more than length.
  • Base64 or Base64url for binary data in JSON, HTTP headers, and URLs, where length matters.
  • Base58 or Base58Check for identifiers people copy by hand or read aloud, especially when a typo must be caught.
  • Bech32 for new identifiers that may be typed or read out, with case-insensitive input and stronger error detection.
  • Base32 when a value must survive case-insensitive systems, such as DNS names or file systems.

What Happens If You Paste a Private Key?

Base58 is built for public values, so the field is not masked. But if what you paste reads as a private key, such as a WIF key or an xprv extended key, the page switches to the same rules as TOTP and Env dump: a red notice appears, the key is held only in this tab's memory, and it is wiped when you leave the tab, switch tools, or stop for five minutes. Use throwaway test keys only; a key that controls real funds should never be pasted into any web page.

What Other Tools Are in the Encode / Crypto Lane?

  • Hash: MD5, SHA-1, SHA-256, SHA-384, and SHA-512 of text or a file, plus HMAC and a checksum verifier.
  • Base: Binary, octal, decimal, hex, and any base to 36, with a clickable bit grid and two's complement.
  • TOTP: Live RFC 6238 codes from a pasted secret or otpauth URI. The secret stays in this tab's memory.

Elsewhere in the toolbox: UUID, .gitignore, CSP, .htaccess, and more on the 2toolbox home page. Part of the 2suite.io privacy-first ecosystem.

Frequently Asked Questions

Why does a Bitcoin address start with 1 or 3?

The first byte is the version: 0x00 encodes as a leading 1 for pay-to-public-key-hash addresses, and 0x05 lands on 3 for pay-to-script-hash addresses.

Is Base58 a kind of encryption?

No. It is an encoding, like hex or Base64. Anyone can decode it back to the same bytes without a key.

Why does my Base58 string pass with no checksum?

Plain Base58, as used by IPFS CIDv0 and Solana addresses, has no checksum. Only Base58Check values carry one, and a typo in plain Base58 gives a different valid-looking value.

Why does my bc1 address fail here?

Bech32 must be all lowercase or all uppercase, and version 0 addresses must use Bech32 while Taproot must use Bech32m. A single wrong character also fails the checksum.

Which alphabet does IPFS use?

The Bitcoin Base58 alphabet, called base58btc in multibase. CIDv1 strings usually use lowercase base32 with the prefix b instead.

Was this helpful?