Skip to content
Encoding
Base85
Boundary
Text or bytes
Runtime
Browser

Encode bytes as framed Adobe Ascii85 or strict Z85

Choose framed Adobe Ascii85 for arbitrary byte lengths or unframed Z85 for exact four-byte chunks.

Local processingNo sign-upNo files or upload

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

Selected Base85 representation

Decoder reports keep lowercase hexadecimal authoritative.

What this tool proves

Explicit byte-to-text semantics

Adobe Ascii85 and Z85 use different alphabets and termination rules. The profile selector never auto-converts one dialect into the other.

Base85 names a family, not one interoperable alphabet

Adobe Ascii85 and Z85 use different alphabets and termination rules. The profile selector never auto-converts one dialect into the other.

Ascii85 emits <~…~>, uses z only for a complete zero tuple, and handles a final partial tuple. Z85 rejects source lengths not divisible by four.

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