How is Base58 different from Base64?

Base58 drops the look-alike characters 0, O, I and l as well as + and /, leaving 58 letters and digits that are easy to copy by hand and select with a double click — Bitcoin addresses and IPFS CIDs use it. It treats the data as one big number and converts its base, writing leading zero bytes as the character 1. Base58Check appends the first 4 bytes of a double SHA-256 hash as a checksum, so a single mistyped character is detected.

What is the difference between Ascii85 and Z85?

Both encode 4 bytes as 5 characters, which is more compact than Base64 (25% overhead instead of 33%). Ascii85 uses ASCII 33–117, abbreviates four zero bytes as z and is common in PDF and PostScript, optionally wrapped in . Z85 is ZeroMQ’s variant with an alphabet free of quotes and backslashes so it embeds easily in source code, but the input length must be a multiple of 4.

How reliable is auto-detection?

Every supported encoding is tried and only successful decodes are kept, then ranked by format signals (narrower alphabets are more telling — input made only of 0s and 1s is most likely binary) and by whether the result is readable UTF-8 text. Short strings like “1111” fit several formats, so switch between the candidates or pick the source encoding yourself.

Which domains can the Punycode converter handle?

The domain is split on dots and every label with non-ASCII characters is converted with the RFC 3492 algorithm into an xn-- label, so münchen.de becomes xn--mnchen-3ya.de. Labels are NFKC-normalized and lowercased first and full-width dots such as 。 are recognized, which is close to the UTS #46 rules browsers use, though it doesn’t perform the full disallowed-character validation.

📟

📟Base32, Base58, Base62, Base85 & Punycode Encoder / Decoder

Developers run into many encodings: TOTP secrets use Base32, Bitcoin addresses use Base58Check, short links and IDs use Base62 or Base36, PDF and PostScript contain Ascii85, ZeroMQ uses Z85, email bodies are Quoted-Printable, and internationalized domain names become xn-- Punycode. This tool puts them all in one place. Enter text (as UTF-8), hex or Base64, or pick a file, and every encoding is listed at once, ready to copy. It covers Base32 (RFC 4648 standard and base32hex, padding optional), Base58 (Bitcoin alphabet) and Base58Check with a double SHA-256 checksum, Base62, Base36, Ascii85 (optionally wrapped in <~ ~>), Z85, hex, binary, octal and decimal bytes, Quoted-Printable and Base64; for text it also shows UTF-16 code units, UTF-16BE/LE bytes, UTF-32 code points, IDNA domains (xn--), raw Punycode, ROT13 and ROT47. To decode, choose the source encoding or let auto-detection try them all and rank the candidates by format signals and how much the result looks like readable text, then see the UTF-8 text and the raw bytes.

Free · No sign-up · Runs in your browserLast updated: 2026-10-26

Loading tool...

How to use Multi-Encoding Converter

1Choose Encode and enter text, hex or Base64, or pick a file
2Copy the encoding you need from the list, adjusting padding, case and other options
3To reverse it, switch to Decode, paste the data and use auto-detect or pick the source encoding

FAQ

How is Base58 different from Base64?: Base58 drops the look-alike characters 0, O, I and l as well as + and /, leaving 58 letters and digits that are easy to copy by hand and select with a double click — Bitcoin addresses and IPFS CIDs use it. It treats the data as one big number and converts its base, writing leading zero bytes as the character 1. Base58Check appends the first 4 bytes of a double SHA-256 hash as a checksum, so a single mistyped character is detected.
What is the difference between Ascii85 and Z85?: Both encode 4 bytes as 5 characters, which is more compact than Base64 (25% overhead instead of 33%). Ascii85 uses ASCII 33–117, abbreviates four zero bytes as z and is common in PDF and PostScript, optionally wrapped in <~ ~>. Z85 is ZeroMQ’s variant with an alphabet free of quotes and backslashes so it embeds easily in source code, but the input length must be a multiple of 4.
How reliable is auto-detection?: Every supported encoding is tried and only successful decodes are kept, then ranked by format signals (narrower alphabets are more telling — input made only of 0s and 1s is most likely binary) and by whether the result is readable UTF-8 text. Short strings like “1111” fit several formats, so switch between the candidates or pick the source encoding yourself.
Which domains can the Punycode converter handle?: The domain is split on dots and every label with non-ASCII characters is converted with the RFC 3492 algorithm into an xn-- label, so münchen.de becomes xn--mnchen-3ya.de. Labels are NFKC-normalized and lowercased first and full-width dots such as 。 are recognized, which is close to the UTS #46 rules browsers use, though it doesn’t perform the full disallowed-character validation.