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.
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.
Loading the toolbox.
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.
F12, or Cmd+Option+I on a Mac, and select the Network tab.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.
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.
Base58Check, the format of Bitcoin legacy addresses and WIF keys, adds a checksum before encoding:
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.
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.
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.
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.
Elsewhere in the toolbox: UUID, .gitignore, CSP, .htaccess, and more on the 2toolbox home page. Part of the 2suite.io privacy-first ecosystem.
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.
No. It is an encoding, like hex or Base64. Anyone can decode it back to the same bytes without a key.
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.
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.
The Bitcoin Base58 alphabet, called base58btc in multibase. CIDv1 strings usually use lowercase base32 with the prefix b instead.