Encoding
Encode text to Base58
Base58 Encoder writes text using the alphabet Bitcoin made familiar, 123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz, which drops the lookalike characters 0, O, I and l. Developers use it to make compact identifiers, prepare test vectors and experiment with Bitcoin-style formats; bitcoin encodes to 4jJc4sAwPs. The text is converted to UTF-8 first. Output is plain Base58, with no version byte and no checksum, so it is not Base58Check like a Bitcoin address.
How to use Base58 Encode
- Open Base58 Encode in the Toolbox101 app.
- Paste the text you want encoded into the
Inputbox;bitcoinis a quick test. - Read the result in the
Outputbox. It uses only the Bitcoin alphabet, so no 0, O, I or l. - Click
Copyto put the Base58 string on your clipboard.
Worked example
Base58 Encode returns the output below for this input.
Input
bitcoinOutput
4jJc4sAwPsCheck it yourself: open Base58 Encode and enter the same input.
Frequently asked questions
What is Base58 and why does Bitcoin use it?
Base58 encodes bytes with an alphabet of 58 unambiguous characters: all digits and letters except 0, O, I, and l, which look alike when handwritten or read aloud. Bitcoin uses it so addresses and keys can be shared without transcription errors. The format is case-sensitive and more compact than hex.
What is the difference between Base58 and Base58Check?
Plain Base58 encodes raw bytes only. Base58Check (used for Bitcoin addresses) first prepends a version byte and appends a four-byte double-SHA256 checksum, then encodes that whole payload. This tool produces plain Base58 without version or checksum, so its output is not a valid Base58Check string.
Which characters does the Bitcoin alphabet exclude and why?
The alphabet keeps digits 1-9 and letters except O, I, and l: 0 is dropped because it is indistinguishable from O, and I and l because most fonts render them identically. That leaves 58 unambiguous characters covering roughly 5.86 bits each, so encoded strings stay short without risking misread copies.
How does Base58 compare with Base64 or hex for short IDs?
Base58 packs about 5.86 bits per character, so it is shorter than hex (4 bits per character) and only marginally longer than Base64 (6 bits). Choose Base58 when strings are read aloud or copied by hand, Base64 when every byte of compactness matters, and hex when downstream tools expect it.
Use Base58 Encode now
Runs in your browser. Nothing you type is uploaded.