Binary-to-text encoders and decoders — Base64, Base64URL, Base32, Base58 and Ascii85. These schemes carry arbitrary bytes through text-only channels such as email, JSON and URLs. Everything runs locally in your browser.
- Base64 Encoder
Convert text or Unicode characters into Base64 – the binary-to-text encoding used by email attachments, data URIs and HTTP basic authentication.
- Base64 Decoder
Decode a Base64 string back to readable text, with clear errors for invalid characters, wrong length and bad padding.
- Base64URL Encoder
Encode text with the URL-safe Base64 alphabet from RFC 4648 section 5: minus and underscore replace plus and slash, and padding is normally dropped, so the result is safe in URLs, filenames and JWTs.
- Base64URL Decoder
Decode URL-safe Base64 – the variant used in JWT header and payload sections – back to text, handling missing padding automatically.
- Base32 Encoder
Encode data as Base32 (RFC 4648) using the case-insensitive A-Z 2-7 alphabet found in TOTP authenticator secrets, DNS records and Onion addresses.
- Base32 Decoder
Decode Base32 back to text or bytes.
- Base58 Encoder
Encode bytes as Base58 – the Bitcoin alphabet that deliberately omits 0, O, I and l so codes survive being read aloud, handwritten or retyped.
- Base58 Decoder
Decode a Base58 string such as a Bitcoin address or IPFS CIDv0 back to its underlying bytes, shown as text where possible and hex otherwise.
- Ascii85 Encoder
Encode data as Ascii85 (base85), which packs 4 bytes into 5 characters for about 25 percent overhead versus the 33 percent of Base64.
- Ascii85 Decoder
Decode Ascii85 or base85 data back to bytes, accepting the Adobe delimiters and the z shortcut that stands for four zero bytes.
