Encode or decode RFC 1924 Base85. Not Ascii85 or Z85. Runs in your browser.
Runs in your browser — your input is processed on this device and never uploaded.
Enter text or upload a file to encode. To decode, enter the encoded text.
Results appear here.
Base85 writes binary data using 85 printable characters, so four bytes become five characters. This page uses the alphabet from RFC 1924. That is not Adobe Ascii85, and it is not Z85.
There is one alphabet and no padding or wrapping option.
Several encodings call themselves Base85 and do not share a character set. Mixing them does not throw a loud error. It just gives you the wrong bytes, which is worse.
Name the RFC when the protocol names the RFC. If it names Adobe, PostScript, or ZeroMQ, you want a different tool.
Ascii85 Encoder and Decoder is the Adobe variant, the one PDF and PostScript streams actually use. Base64 Encoder and Decoder is the default when the other end does not name a Base85 dialect at all. basE91 is denser still and even less widely implemented.
None of these encrypt or compress. They only change how bytes are written as text.
RFC 1924 proposed Base85 as a shorter way to write IPv6 addresses. The encoding stuck around more as a curiosity than as a network standard.
Encoded output can include punctuation that JSON, URLs, or a shell will treat as syntax. Escape it before dropping it into those formats.