Base Encoder/Decoder

A universal Base encoding tool supporting Base32, Base58, Base62, Base64, Base85, Base91, Base122, and Base32768 algorithms for text and file encoding/decoding.

Different Base encoding algorithms are designed for specific scenarios. Whether you need URL-safe encoding, compact binary representation, or Twitter-friendly Unicode encoding, this tool provides the right algorithm for your needs. All processing happens locally in your browser with complete privacy protection.

Supported Algorithms

Base32

Defined in RFC 4648, Base32 uses 32 characters (A-Z and 2-7) to represent data. Its case-insensitive nature makes it ideal for systems that don't preserve letter case, such as DNS records and file systems. The tool supports both Standard and Extended Hex (using 0-9 and A-V) variants.

Base58

Originally designed for Bitcoin addresses, Base58 deliberately excludes visually ambiguous characters: zero (0), uppercase O, lowercase l, and uppercase I. This prevents transcription errors when users manually copy addresses. Three variants are available: Bitcoin (the original), Flickr (swaps uppercase and lowercase), and Ripple (custom alphabet for the payment network).

Base62

Uses only alphanumeric characters (0-9, A-Z, a-z), making it inherently URL-safe without special encoding. Commonly used for short URL services, unique identifiers, and any context where special characters are problematic.

Base64

The most widely used binary-to-text encoding scheme. Standard Base64 uses A-Z, a-z, 0-9, plus sign (+), and forward slash (/), with equals sign (=) for padding. The URL-safe variant (Base64URL) replaces + with - and / with underscore, removing padding characters for use in URLs, filenames, and JWT tokens.

Base85 (Ascii85/Z85)

Achieves higher encoding density than Base64 by using 85 printable ASCII characters. The Ascii85 variant (also known as Adobe encoding) wraps output in <~ and ~> delimiters, while Z85 (ZeroMQ encoding) uses a different character set optimized for embedding in source code and JSON strings.

Base91

Offers the highest encoding efficiency among ASCII-only encodings, using 91 printable characters. The encoded output is approximately 23% smaller than Base64 for the same input data, making it suitable for size-constrained environments.

Base122

A UTF-8 optimized encoding that uses single-byte characters whenever possible, falling back to two-byte sequences only for special cases. Produces very compact output while remaining valid UTF-8 text.

Base32768

Encodes data using Unicode characters from carefully selected safe ranges, storing 15 bits per character. Particularly useful for Twitter and other platforms with character limits, as it maximizes data density within those constraints.

How to Use

1. Select the encoding direction (Encode or Decode)
2. Choose an algorithm from the dropdown menu
3. Select a variant if available (e.g., Bitcoin/Flickr for Base58)
4. For encoding: enter text directly or upload a file
5. View the result in the output panel

Encoding Efficiency Comparison

Efficiency indicates how much of the original data size is preserved after encoding. Higher percentages mean smaller encoded output.

Common Use Cases

• API Development: Base64 for binary payloads, Basic Auth headers, and JWT tokens
• Cryptocurrency: Base58 for wallet addresses and transaction IDs
• URL Shorteners: Base62 for generating compact, URL-safe identifiers
• Social Media: Base32768 for maximizing data in character-limited posts
• Data Embedding: Base85 for efficient inline data in source code
• Legacy Systems: Base32 for case-insensitive storage and transmission

Important Notes

Encoded data is always larger than the original binary data. Base64 increases size by approximately 33%, while more efficient encodings like Base32768 have minimal overhead but produce Unicode output.

All processing occurs entirely in your browser. No data is transmitted to any server, ensuring complete privacy for sensitive content.

For large files, encoding may require significant browser memory. Files under 10MB work reliably; larger files may cause performance issues depending on your device.

Base encoding is not encryption. Anyone can decode Base64 or any other Base-encoded string. Never use these encodings to protect sensitive information.