Base58 Text Encoder Decoder

Encode UTF-8 text as Bitcoin-alphabet Base58 or strictly decode it back to text, locally in your browser.

Bitcoin Base58 alphabet, without checksum. Input limit: 4,000 UTF-16 code units; maximum 2,000 UTF-8 bytes. Processing stays in your browser. Decoding rejects whitespace; pasted line endings may normalize to LF.

Convert text using the Bitcoin Base58 alphabet

This tool converts UTF-8 text to a compact Base58 representation and decodes valid UTF-8 results. It uses 123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz, the alphabet used by Bitcoin. The characters 0, O, I and lowercase l are excluded. Case matters: upper- and lowercase letters have different values.

Try a reproducible conversion

Load example (replaces input and mode) inserts hello. Choose Process input to obtain Cn8eVZg, representing five UTF-8 bytes. Paste that result, check Decode bytes to UTF-8 text, and process it to recover hello.

Raw Base58 is not Base58Check

No version byte, checksum or address validation is added or checked. A wallet address can decode to binary data that is not UTF-8, so this text tool is unsuitable for verifying cryptocurrency addresses or extracting arbitrary binary files. The alphabet and leading-zero convention can be checked in Bitcoin Core's Base58 implementation.

Each leading zero byte becomes a leading 1; decoding restores those bytes. Thus 1 decodes to one NUL character, which is invisible in a textarea but retained in the download. Zero bytes are not discarded or confused with an empty input. The decoder rejects whitespace, punctuation and = padding rather than trimming or repairing a value.

Work limits and text boundaries

Input must contain 1-4,000 UTF-16 code units. Both source UTF-8 bytes and decoded bytes are limited to 2,000 because repeated integer conversion grows more expensive with input length. A short string of multibyte characters may reach the byte limit before the input character limit. Empty input is a missing entry rather than an empty-byte conversion.

UTF-8 validation and export behavior

Decoding requires valid UTF-8: isolated continuation bytes, overlong sequences and encoded surrogate values fail instead of becoming replacement characters. A leading UTF-8 BOM is preserved as U+FEFF. Input containing an unpaired surrogate is rejected. A text encoding changes representation; it does not encrypt the text or prove its origin.

The TXT download contains the exact result encoded as UTF-8, without an added newline. Invisible control characters remain in the file. Browser textarea input can normalize CRLF or CR to LF, so this is not a byte-preserving file converter. Editing the input or mode removes the previous result and download. Copy can depend on browser permissions; downloading is an alternative.

Use UTF-8 Byte Inspector to see byte offsets and values, or Hex Text Encoder Decoder when you need a byte-pair representation. All conversion happens in this browser; the tool does not upload your text.