Encode plaintext to Bitcoin Base58
Input
Hello WorldExample output
JxF12TrwUP45BMdEncode text to Base58 or decode Base58 strings back to readable UTF-8 text using Bitcoin/IPFS, Ripple, or Flickr alphabets. Preserves leading zero byte integrity and executes 100% locally in browser memory.
| Alphabets | Bitcoin/IPFS, Ripple, and Flickr variants |
|---|---|
| Zero Preservation | Preserves leading null bytes as alphabet zero symbols |
| Maximum Input | 5 MB |
| Execution Deadline | 2 s |
Input
Hello WorldExample output
JxF12TrwUP45BMdInput
JxF12TrwUP45BMdExample output
Hello WorldIn Base58, leading zero bytes are preserved by prepending the first character of the alphabet (e.g. '1' in Bitcoin). Multiple leading zero bytes produce multiple leading '1' characters.
The standard Bitcoin Base58 alphabet excludes '0' (zero), 'O' (capital o), 'I' (capital i), and 'l' (lowercase L) to avoid transcription mistakes.
Attempting to decode strings containing non-alphanumeric characters, punctuation, or excluded ambiguous characters will produce a descriptive error pinpointing the invalid character and position.
Base64 Encoder / Decoder
Encode UTF-8 text to standard or URL-safe Base64 and decode Base64 back to text.
Base32 Encoder / Decoder
Encode UTF-8 text to RFC 4648 Base32, extended hex, or Crockford alphabet and decode Base32 back to readable text.
Hex (Base16) Encoder / Decoder
Encode text to hexadecimal (Base16) byte strings and decode hex bytes back to UTF-8 text with customizable delimiters and prefixes.
Base58 avoids confusing characters like 0 vs O and 1 vs l, and eliminates punctuation characters (+, /) so that double-clicking an address selects the whole string without splitting.
This tool encodes and decodes UTF-8 text. Cryptographic addresses that encapsulate raw binary hashes (Base58Check) can only be decoded to text if the underlying bytes form valid UTF-8.
Yes. All computation is executed in your browser via local Web Workers. No data is sent over the network.