ZH

Base64 / Base58

Base64 Base58 Encoder Decoder converts text and hex across Base64, Base58 and Base58Check with checksum checks. For BTC, WIF and Solana; runs locally.

Base64
SGVsbG8sIFdlYjM=
Base58
JxF12Ts3Lkd7M3Y
Base58Check
32UWxgjUxcoWzccCboaTA
Hex
0x48656c6c6f2c2057656233

Calculations and checks on this page run in your browser. Private keys and seed phrases are never uploaded to the server.

About this tool

Base64 Base58 Encoder Decoder turns binary into printable strings. Base58 drops lookalike characters and is common for BTC and Solana addresses and key formats.

Base58Check appends the first 4 bytes of double SHA-256—used by Bitcoin P2PKH addresses and WIF; decode failures usually mean typos or the wrong format.

Encode: text/hex → encodings. Decode: Base64/Base58/Base58Check → hex and a UTF-8 preview.

How to use

  1. Choose encode or decode.
  2. Encode: set text or hex input and enter data.
  3. Decode: pick the source format and paste the string.
  4. Copy the hex or text result.

FAQ

When should I use Base58 vs Base64?

Base64 is denser and common in HTTP/APIs. Base58 is easier to transcribe by hand and is typical for on-chain addresses and WIF.

Why does Base58Check decoding fail?

Checksum mismatch (entry error) or plain Base58 data such as a Solana address. Retry in Base58 (no check) mode.

Should I decode a WIF private key in a web page?

Not recommended. Computation is local, but extensions may still read the DOM. Prefer an isolated environment or CLI for WIF.

Is Base64 encoding the same as encryption?

No. Base64/Base58 are reversible encodings, not encryption—do not use them to protect secrets.

Related tools