Base58 Decoder

Paste Base58 and read the text.

Use this tool

Result

The result appears in this panel after you run the tool.

About this tool

Characters that are not in the alphabet are rejected.

Leading zeros in the original bytes are preserved when the alphabet encoding included them.

How to use it

  1. Open this page and provide the input it asks for.
  2. Set the options that are visible, then use Decode Base58.
  3. Read the result in the panel. Copy it or download it when a file is offered. The input stays in this browser.

Limitations

Unknown glyphs fail closed

What is accepted

The decoder trims the ends and then requires every remaining character to be in the Bitcoin alphabet. A leading run of 1 characters becomes that many zero bytes. The other symbols are a base-58 integer unpacked into bytes. Those bytes are decoded as UTF-8 and shown as text. There is no padding to ignore, because this alphabet does not use an equals sign. An equals sign, a 0, an uppercase O, an uppercase I, a lowercase L, a space, or a newline in the middle rejects the paste because a glyph sits outside the alphabet. The whole value fails. There is no skip-and-continue.

That is harsher than the base32 decoder, which strips padding and uppercases before it looks at symbols. Here case is significant, because uppercase and lowercase are different symbols. A base64 or base32 string will almost always hit a forbidden character and throw. That error means the alphabet is wrong. It does not mean the payload was tampered in a cryptographic sense. There is still no checksum on this page.

Round trip and the losses

Text from the encoder decodes back to the same text. The losses are about inputs the encoder did not produce, and about what the format never carried. Interior whitespace fails, whereas a human might expect it to be ignored. Case changes fail, whereas base32 would have folded case. A Base58Check string decodes to whatever bytes it contains, checksum included, and may look like garbage text or throw inside the UTF-8 step only in the sense of replacement characters. The page does not report “bad checksum,” because it does not compute one. Leading 1 characters that you add or remove change the zero bytes, so they change the text. They are not decoration.

Not a wallet screen

Decoding does not identify a network, a version byte, or a key type. It does not prove the string is an address. It does not contact a node. If the goal is to read a secret that was only encoded, you now have the secret in the panel, which is the opposite of keeping it. If the goal is confidentiality, encoding was the wrong tool before you ever decoded it.

Privacy

Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.