How to use
- Choose the encoding of your input as the source, for example Base64.
- Choose the encoding you want as the target, for example Base58.
- Paste the input to get the converted output.
- Click Copy to use the result, or Swap to convert in the opposite direction.
Why convert bytes instead of text
Base64, Base58, hex and the other encodings on this site all describe bytes. Converting by decoding to text and then encoding that text again only works when the data really is text. Keys, hashes, signatures, images and compressed data contain byte sequences that are not valid UTF-8. A text decoder replaces them with the replacement character U+FFFD, and the re-encoded result is silently wrong.
This converter decodes the source string to raw bytes and writes those bytes directly in the target encoding. A 32-byte key stays exactly 32 bytes, leading zero bytes are kept, and converting back returns the same bytes. The conversion runs entirely in your browser.
Common conversions
- Base64 to Base58: move public keys and hashes from an API into the format used by Bitcoin, Solana and IPFS. For hex input, see hex to Base58.
- Base32 to Base64 or hex: inspect a TOTP secret or reuse it in a system that expects another format.
- Hex to Base62 or Base58: shorten hashes and IDs for URLs. A 64-digit SHA-256 hex string becomes about 43 characters.
- Base64 to Base64URL: make a value safe for URLs, cookies and JWT fields.
- Ascii85, Base85 or Z85 to Base64: reuse data taken from PDF streams, Git binary patches or ZeroMQ messages.
The same four bytes in five encodings:
| Encoding | Value |
|---|---|
| Hex | deadbeef |
| Base64 | 3q2+7w== |
| Base58 | 6h8cQN |
| Base62 | 44pZgF |
| Base85 | -mSjx |
Input rules and limits
- Base64 input may use the standard or the URL-safe alphabet, contain line breaks and leave out the padding.
- Hex input may contain spaces, colons or a
0xprefix, in upper or lower case. - Base58 and Base62 treat the data as one big number, so conversions that involve them are limited to about 20 KB.
- Checksums are neither checked nor added. To verify or create a Base58Check string, use the Base58Check page.
Frequently asked questions
How do I convert Base64 to Base58?
Select Base64 as the source and Base58 as the target, then paste your string. The Base64 is decoded to bytes, and those bytes are written with the Bitcoin Base58 alphabet, which Solana and IPFS use as well.
Is this the same as decoding and then encoding again?
Only when the data is plain text. For binary data such as keys or images, decoding to text loses bytes. This tool never goes through text, so the bytes are preserved exactly.