Skip to content
Encoding
Base58
Boundary
Text or bytes
Runtime
Browser

Decode raw Bitcoin Base58 into exact bytes

Recover exact bytes from the Bitcoin Base58 alphabet without Base58Check or address validation.

Local processingNo sign-upNo files or upload

Decode 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.

Decoded byte report

Decoder reports keep lowercase hexadecimal authoritative.

What this tool proves

Explicit byte-to-text semantics

Every leading 1 becomes a leading zero byte. Characters 0, O, I, and lowercase l are outside the alphabet and fail instead of being corrected.

Raw decoding stops before checksum or address interpretation

Every leading 1 becomes a leading zero byte. Characters 0, O, I, and lowercase l are outside the alphabet and fail instead of being corrected.

The decoded bytes are re-encoded and compared exactly. Whitespace is rejected even though some application parsers trim it.

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