Base58 (raw)
Hello, World!
72k1xXWG59fYdzSNoA
Raw Base58 of the UTF-8 bytes.
Encode text to Base58 or decode Base58 to UTF-8 text in your browser. Choose raw Base58 or Base58Check with a checksum; all processing stays on your device.
Base58 (raw)
Hello, World!
72k1xXWG59fYdzSNoA
Raw Base58 of the UTF-8 bytes.
Base58 (raw)
72k1xXWG59fYdzSNoA
Hello, World!
Decoding restores the original text.
Base58Check (checksum)
Hello
1vSxRbq6DSYXc
Base58Check adds version byte 0x00 and a four-byte checksum before encoding the UTF-8 text.
Base58Check (checksum)
1vSxRbq6DSYXc
Hello
The checksum is verified before the original UTF-8 text is returned.
Base58, also written as Base 58, is a binary-to-text encoding that represents bytes as a large number in base 58. Its Bitcoin alphabet deliberately omits the easily confused characters 0, O, I, and l. That makes a Base58 string more practical to read, copy, and transcribe than encodings that include those symbols.
Unlike Base32 or Base64, Base58 encoding does not split data into fixed-size bit groups. It treats the complete byte sequence as one large integer, repeatedly divides it by 58, and maps the remainders to the Base58 alphabet. Leading zero bytes are preserved as leading 1 characters.
This tool converts the UTF-8 bytes of the text you enter. Select Base58 (raw) for a direct byte-to-Base58 conversion, or select Base58Check when you need the tool’s checksum format. The conversion happens locally in your browser; nothing is sent to a server.
Base58Check first prefixes the payload with a version byte, then appends the first four bytes of a double SHA-256 hash as a checksum before Base58 encoding. On decoding, this tool verifies that checksum and rejects a value that does not match it. A checksum helps detect accidental changes; it does not encrypt the data or prove who created it.
Bitcoin commonly represents legacy P2PKH and P2SH addresses with Base58Check. Those names describe address types, not different Base58 alphabets. This page is a text conversion tool: its Base58Check option always uses version byte 0x00 and returns the decoded payload as UTF-8 text, so it should not be used to generate, classify, or validate arbitrary cryptocurrency addresses, wallets, transactions, or private keys.
Encode text and binary payloads to Base64 and decode them back with UTF-8 support.
Convert text and bytes to hexadecimal format and decode hex sequences back to text.
Encode and decode URL strings and query params for safe transport in HTTP and APIs.
Convert text into 8-bit binary groups and decode binary bytes back into readable text.
Convert ASCII characters and numeric codes for protocol and parser workflows.
Decode JWT tokens in-browser and inspect header, payload, claims, and expiration data.