Base58 Decode
ED-51Paste a Base58 string to get the bytes back as UTF-8 text or as hex. It reads the Bitcoin alphabet and can verify a Base58Check checksum.
Runs in your browser. Nothing is uploaded.
Base58 string (or text to encode)
Result
How to use it
- Paste the Base58 string into the input box. Spaces and line breaks are ignored.
- Under Decode output, choose Text (UTF-8) for readable text or Hex bytes for raw bytes.
- Click Decode Base58. Use Decode Base58Check if the string ends in a 4 byte checksum, as Bitcoin addresses do.
- Copy the result or download it as a .txt file.
What decoding gives you
Base58 writes a sequence of bytes as one long number in base 58. Decoding reverses that and returns the bytes. If those bytes are text, pick Text (UTF-8) and you see the words. If they are a hash, a key or other binary data, pick Hex bytes, because arbitrary bytes are usually not valid text. Each leading 1 in the string decodes to a zero byte, so a string of three 1s is three zero bytes.
Decoding a Base58Check string
A Base58Check string carries a 4 byte checksum at the end: the first four bytes of the SHA-256 hash of the SHA-256 hash of the data before it. Decode Base58Check recomputes that value and compares it. When it matches you see the first byte, which is the version, and the rest of the payload in hex. A mismatch usually means one character was mistyped. The tool does not say what a given version byte means.
Limits to know
Only the Bitcoin alphabet is read: 1 to 9, A to Z and a to z without 0, O, I and l. Other orderings of 58 characters give different bytes for the same text, so a string written with another alphabet will either fail or decode to the wrong data. There is also an Encode button for the opposite direction, which is secondary on this page.
Error messages and what to do
| Message | What it means | Fix |
|---|---|---|
Invalid Base58 character | The text has a character outside the Bitcoin alphabet. The message names the character and its position. | Correct that character. 0, O, I and l are never valid. |
The checksum does not match | The last four bytes are not the double SHA-256 checksum of the bytes before them. | Look for a mistyped or missing character, or use Decode Base58 if the string has no checksum. |
The bytes are not valid UTF-8 text | The decoded bytes are not text, for example a hash or a key. | Set Decode output to Hex bytes. |
Questions people ask
How do I decode Base58?
Paste the Base58 string and click Decode Base58. The tool maps each character to its value in the Bitcoin alphabet, rebuilds the number and writes it out as bytes, shown as UTF-8 text or hex depending on your choice.
Why does Base58 decode show an error about UTF-8?
Decoding returns bytes. If you ask for text and the bytes are not valid UTF-8, for example when the string holds a hash or a key, there is no text to show. Change Decode output to Hex bytes and the same data displays fine.
How do I decode a Bitcoin address?
Use Decode Base58Check. It checks the checksum, then shows the version byte and the hash that follows it in hex (20 bytes for ordinary P2PKH and P2SH addresses). It tells you whether the checksum is valid, but it does not look up the address or its balance.
What does a Base58 string starting with 1 decode to?
Each leading 1 is one leading zero byte. In a Bitcoin address that first byte is the version 00, which is why many addresses begin with 1. After the leading ones, the rest of the characters give the remaining bytes.
Which characters does Base58 leave out?
The digit 0, the capital letters O and I, and the lowercase l. They are easy to mix up when reading or typing a string, so the alphabet drops them and keeps 58 characters.
Can this decode Base58 with the Ripple or Flickr alphabet?
No. Only the Bitcoin alphabet is supported. A string written with another ordering will be rejected or decode to different bytes than intended, so convert it to the Bitcoin alphabet first or use a tool made for that variant.
About this tool
Reads Base58 written with the Bitcoin alphabet, which leaves out 0, O, I and l, and gives back the bytes as UTF-8 text or as hex. Each leading 1 decodes to a zero byte. Whitespace is ignored, and any other character outside the alphabet is reported with its position. Base58Check decoding splits off the last 4 bytes and compares them with the double SHA-256 checksum of the rest, then shows the first byte (the version) and the payload in hex. Other Base58 alphabets, such as the Ripple one, are not supported. The decoded bytes must be valid UTF-8 to show as text; otherwise switch the output to hex.