Base64 compared with other binary-to-text encodings
| Encoding | Alphabet size | Overhead | Typical use |
|---|---|---|---|
| Hex (Base16) | 16 | +100% | Hashes, debugging, colours |
| Base32 | 32 | +60% | TOTP secrets, case-insensitive IDs |
| Base58 | 58 | +37% | Bitcoin addresses (no 0/O/I/l confusion) |
| Base64 | 64 | +33% | E-mail, data URIs, JSON, JWT |
| Ascii85 / Base85 | 85 | +25% | PDF, PostScript, Git binary patches |
| Uuencode | 64 | +35% (+ line overhead) | Legacy Usenet / e-mail |
Base64 wins in practice because its alphabet survives almost every system, the 3-to-4 ratio is easy to implement, and every language ships it.
Comments (0)
Questions, ideas or a bug in “More about Base64”? Leave a comment, rate the tool, or reply to others.
No comments yet. Be the first to share your feedback!