Skip to content
Encoding
Base58
Boundary
Text or bytes
Runtime
Browser

Encode raw bytes with the Bitcoin Base58 alphabet

Create raw Bitcoin-alphabet Base58 text without address rules, hashing, or Base58Check.

Local processingNo sign-upNo files or upload

Encode Base58

Limited to 4,096 bytes or 5,600 encoded characters.

Tool Swim does not upload, fetch, save, log, convert files, or create presets from these values.

Raw Bitcoin Base58

Decoder reports keep lowercase hexadecimal authoritative.

What this tool proves

Explicit byte-to-text semantics

Bitcoin Base58 omits visually ambiguous characters. Each leading zero byte becomes a leading 1 so the byte sequence survives a round trip.

Bitcoin alphabet does not imply Bitcoin address semantics

Bitcoin Base58 omits visually ambiguous characters. Each leading zero byte becomes a leading 1 so the byte sequence survives a round trip.

This is raw encoding only. It does not append a hash checksum, version a payload, validate an address, or claim a network.

Bytes stay explicit, private, and bounded

Encoder text is converted with UTF-8 only after malformed surrogate pairs are rejected. Hex mode accepts exact byte pairs without 0x, spaces, or separators. Decoder hex is authoritative; a text preview appears only when the bytes are valid UTF-8.

The work starts only when you submit the form. Source text, byte values, and results stay in the current browser tab; Tool Swim does not upload them, log their content, save presets, or call a developer API.

Base16, Base32, Base64, and Base85 allow at most 512 KiB of source or decoded bytes and 1 MiB of encoded text. Bitcoin Base58 is limited to 4,096 bytes or 5,600 characters because generic radix conversion is quadratic.

Primary references

Questions and answers

Related Base Encoding tools