Skip to content
Encoding
Base85
Boundary
Text or bytes
Runtime
Browser

Strictly decode Adobe Ascii85 or ZeroMQ Z85

Validate the selected Base85 dialect, recover its exact bytes, and keep invalid UTF-8 separate.

Local processingNo sign-upNo files or upload

Decode Base85

Limited to 512 KiB of bytes and 1 MiB of encoded text.

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

Adobe mode requires <~…~> and permits only the whitespace its specification ignores. Z85 rejects all whitespace and requires five-character groups.

Framing and tuple shape determine whether Base85 is valid

Adobe mode requires <~…~> and permits only the whitespace its specification ignores. Z85 rejects all whitespace and requires five-character groups.

Tuple values above 2³²−1 fail. Adobe z placement and partial tails are checked; Z85 uses the specified big-endian alphabet and chunk boundaries.

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