ToolSphere

Base32, Base58 & Base85 Codecs

More tools

Encode and decode text in Base32, Base58 (the Bitcoin alphabet) and Ascii85, side by side. Free, instant and private in your browser.

Advanced binary-to-text codecs

Encode alphanumeric representations into Base32, Bitcoin Base58, and Ascii85 (Base85) structures.

Encoded representation

On this browser only

Give feedback

Did this tool help?

Tell us what worked, what didn’t, or what you’d like next.

Opens Google Forms in a new tab with this tool’s name filled in. No sign-in or email required. Feedback is optional.

About Base32, Base58 & Base85 Codecs

Three Binary-to-Text Encodings, Three Different Design Goals

Base32, Base58, and Base85 (Ascii85) all convert binary data into printable text, but each optimizes for a different constraint, which is exactly why three separate encodings exist instead of just using Base64 everywhere. Base32 uses a 32-character alphabet deliberately excluding visually similar characters (like 0/O and 1/I), making it well suited for values a human might need to read aloud or type manually — TOTP two-factor authentication secret keys are commonly Base32-encoded for exactly this reason.

Base58 (popularized by Bitcoin) goes further, excluding not just similar-looking characters but also punctuation that could cause problems in certain contexts (like double-clicking to select a whole string) — this is why Bitcoin addresses and similar identifiers use it, prioritizing human transcription accuracy over encoding density.

Base85 takes the opposite priority: it maximizes encoding density (roughly 25% size overhead versus Base64's 33%, and far better than Base32's 60%) at the cost of using a larger, less human-friendly character set including punctuation — used in contexts like PDF and PostScript files where compact binary embedding matters more than a human ever reading the encoded string directly.

Frequently asked questions

Why does Base32 avoid characters like 0 and O?

They look nearly identical in many fonts, so excluding one avoids transcription errors — this makes Base32 well suited for values a person might need to manually type or read aloud, like two-factor authentication secret keys.

Why do Bitcoin addresses use Base58 instead of Base64?

Base58 excludes visually similar characters and punctuation that could cause selection or transcription issues, prioritizing human accuracy when manually copying or reading an address — a deliberate tradeoff against Base64's better encoding density.

Which of these three encodings is most space-efficient?

Base85 — its larger 85-character alphabet packs more bits per output character, resulting in roughly 25% size overhead versus the original data, compared to Base32's much larger ~60% overhead.

Have a suggestion for Base32, Base58 & Base85 Codecs?Share your feedback ↗