B45 ENC

Base45 Encoder / Decoder

Home All Tools

Base45 Encoder / Decoder

Online Free Base45 Encoding Tool — RFC 9285 Compliant · QR Code Optimized

Auto-convert

Drop file here

Chars: 0 | Bytes: 0
Chars: 0 | Overhead: 0%
Strip Whitespace from Input
Process Line by Line
Add Header Comment

Why Use Our Base45 Encoder / Decoder?

RFC 9285

Fully compliant standard

QR Optimized

Efficient QR alphanumeric

Validation

Char-by-char analysis

File Mode

Any file type supported

Private

100% browser-based

Compare

vs Base64 & Base32

The Complete Guide to Base45 Encoding and Decoding: RFC 9285 for QR Codes and Digital Health Certificates

Among the newer additions to the family of data encoding standards, Base45 stands out as a highly specialized encoding designed specifically to maximize the efficiency of QR code data transmission. Standardized in September 2022 as RFC 9285 by the Internet Engineering Task Force (IETF), Base45 was created to address a very specific problem: how to encode arbitrary binary data in a form that is as compact as possible when used in QR codes operating in alphanumeric mode. The result is an encoding that achieves better space efficiency than Base64 within QR codes while using a simple, cleanly defined algorithm. Our free Base45 encoder decoder online implements the complete RFC 9285 specification with full accuracy, supporting text encoding, file encoding, real-time validation, batch processing, a step-by-step visual breakdown, and a three-way comparison with Base64 and Base32—all running privately in your browser without any server uploads or signup requirements.

To understand why Base45 was created, you need to understand how QR codes store data. QR codes support several encoding modes, and the alphanumeric mode is particularly efficient for a specific 45-character set: the digits 0–9, uppercase letters A–Z, and the symbols space, dollar sign ($), percent sign (%), asterisk (*), plus sign (+), hyphen/minus (-), period (.), and forward slash (/). In QR alphanumeric mode, each character requires only 5.5 bits of storage (compared to 8 bits in binary mode), making strings composed entirely of these 45 characters significantly more compact than arbitrary binary data. This is exactly the alphabet that Base45 encoding uses—the full 45-character QR alphanumeric set. By encoding binary data using only these 45 symbols, any Base45-encoded string can be embedded in a QR code using the highly efficient alphanumeric mode rather than the less efficient binary mode.

The Base45 Algorithm: How Encoding Works

The Base45 encoding algorithm (as specified in RFC 9285) is straightforward in concept but distinct from other encoding schemes like Base64. Rather than processing input bytes individually or in groups of 3 as Base64 does, Base45 processes bytes in pairs. For each pair of bytes (16 bits total), the encoder computes a single integer n = byte[0] × 256 + byte[1]. Since n can range from 0 to 65535, and 45^3 = 91125 > 65535, three Base45 characters are sufficient to represent any 2-byte pair. The three characters are computed as: c[0] = n mod 45, c[1] = (n div 45) mod 45, and c[2] = n div 2025 (where 2025 = 45^2). Each of these three values (0–44) is then mapped to the corresponding character in the Base45 alphabet.

When the input data has an odd number of bytes (a single remaining byte after processing all pairs), that last byte is encoded as just 2 Base45 characters: c[0] = byte mod 45 and c[1] = byte div 45. Since a single byte can be at most 255, and 45 × 5 = 225 < 255 < 45 × 6 = 270, two characters always suffice for a single byte. This means Base45 encoding produces output of length ceil(n_bytes / 2) × 3 - (n_bytes mod 2) characters, or equivalently: for every 2 bytes of input, 3 characters of output are generated, with an extra 2 characters for a trailing odd byte. The overhead is exactly 50% (every 2 bytes becomes 3 characters), compared to Base64's 33.3% overhead (every 3 bytes becomes 4 characters). However, the critical advantage emerges when these encoded strings are placed in QR codes—the alphanumeric mode's storage efficiency more than compensates for the extra characters, making Base45 + QR alphanumeric mode significantly more compact than binary data or Base64-encoded data in a QR code.

Base45's Role in the EU Digital COVID Certificate

The most prominent real-world deployment of Base45 is in the EU Digital COVID Certificate (EU DCC), also known as the Digital Green Certificate or the European Health Certificate. During the COVID-19 pandemic, the European Union created a standardized digital certificate system that allowed EU citizens to prove their vaccination, test, or recovery status for travel and venue access across member states. Each certificate was encoded in a QR code with a specific technical structure: the certificate data (expressed as a CBOR-encoded COSE structure) was compressed using zlib/DEFLATE, then the compressed bytes were encoded using Base45, and finally a prefix "HC1:" was prepended to indicate the health certificate version 1 format.

The choice of Base45 for this system was deliberate and technically motivated. By using Base45 encoding, the compressed certificate data could be stored in a QR code using the efficient alphanumeric mode (since all Base45 characters fall within the QR alphanumeric character set). This resulted in significantly smaller QR codes than would have been possible with Base64 encoding (which includes characters like '+', '/', and '=' that fall outside the QR alphanumeric set, forcing use of the less efficient binary mode). The practical result was that EU DCC QR codes could store more information in a smaller, more reliably scannable QR code format. Our tool correctly handles the "HC1:" prefix convention and can decode DCC payloads (the Base45 portion after stripping the prefix) to reveal the compressed certificate data.

Comparing Base45 with Base64 and Base32

Understanding when to use Base45 versus Base64 or Base32 requires looking at the specific use case and the constraints of the target system. Base64 is the most ubiquitous encoding for binary-to-text conversion, encoding every 3 bytes of input as 4 characters (33.3% overhead) using a 64-character alphabet that includes both uppercase and lowercase letters, digits, and the + and / symbols. Base64 is the right choice for HTTP APIs, email MIME encoding, data URIs in HTML/CSS, and virtually any web-based binary data embedding. However, Base64's alphabet includes lowercase letters and special characters, making it unsuitable for QR alphanumeric mode and problematic in case-insensitive contexts.

Base32 uses a 32-character alphabet (uppercase letters and a subset of digits), producing output that is 60% larger than the original data. Its case-insensitivity and alphanumeric-only character set make it suitable for applications like TOTP authentication codes, DNS records, and geohash encoding, but it is not optimized for QR code use. Base45, by using exactly the QR alphanumeric character set of 45 symbols, hits a unique sweet spot: 50% overhead in character count but genuine compactness when stored in QR codes because of alphanumeric mode's superior bit density (5.5 bits per character vs. 8 bits per character in binary mode).

Our compare tab makes these trade-offs concrete and quantifiable for any text you enter. You can immediately see the exact character count and byte size in QR storage for Base45, Base64, and Base32 encodings of your specific data, enabling informed encoding decisions based on your actual content rather than theoretical averages.

Practical Applications Beyond Health Certificates

While the EU DCC made Base45 widely known, the encoding has broader applicability in any context where data needs to be embedded in QR codes efficiently. Event ticketing systems that encode complex ticket data (including seat information, purchaser details, and security tokens) in QR codes benefit from Base45's QR optimization. Transportation systems encoding boarding passes, access credentials, or route information can use Base45 to maximize data density while maintaining reliable QR scanning. Government identity documents and credential systems that use QR-coded data for verification can achieve more compact, higher-quality codes with Base45.

The HCERT specification (Health Certificate) that uses Base45 has been adopted beyond COVID certificates for other health credential use cases, including vaccine passports for other diseases, medical prescription verification systems, and laboratory result authentication. As digital credentials become more widespread, the technical infrastructure built around Base45 encoding for these health applications is likely to be reused and extended. Developers working on digital credential systems, decentralized identity solutions, or verifiable credentials will find our free Base45 encode decode tool invaluable for debugging, testing, and validating their implementations.

Using Our Base45 Tool: Feature Guide

The main encoding and decoding panels provide instant conversion with real-time feedback. The input encoding option lets you specify whether you are providing UTF-8 text, hex byte values, decimal byte values, or binary bit strings, allowing the tool to correctly interpret your input before encoding. Similarly, the output encoding for decode mode lets you see the decoded bytes as human-readable text, hex, decimal, or binary. This flexibility is essential for developers working with binary protocols where the data is not simple ASCII text.

The Validate tab performs a character-by-character analysis of any Base45 string, highlighting valid characters in green and invalid characters in red with underline. The validation also checks whether the string length is valid (Base45 output length can never be n where (n mod 3) == 1, because that would require a fractional input byte), providing immediate diagnostic information for debugging decoder failures. The character count breakdown shows valid, invalid, and space characters separately.

The Visual tab shows the step-by-step encoding process for the first 10 bytes of your input, displaying how each byte pair maps to three output characters through the Base45 arithmetic. This educational visualization is particularly useful for developers implementing Base45 in a programming language and wanting to verify their implementation against the expected intermediate values. The Compare tab provides an immediate side-by-side comparison of Base45, Base64, and Base32 encoding for your input text, showing exact character counts and estimated QR code sizes for each encoding.

Base45 in Modern Digital Infrastructure

The adoption of Base45 as an RFC standard represents a broader trend in data encoding: the recognition that different deployment contexts require different encoding trade-offs, and that a single encoding (like Base64) cannot optimally serve all use cases. As QR codes become a more central part of digital infrastructure—for payments, identity verification, ticketing, healthcare, and access control—the specific optimizations that Base45 provides for QR alphanumeric mode become increasingly valuable.

The simplicity of the Base45 algorithm also makes it easy to implement correctly in any programming language, with minimal code and no lookup tables required. The algorithm is entirely arithmetic, making it fast, deterministic, and straightforward to verify. This implementation simplicity, combined with the well-defined RFC 9285 specification, ensures interoperability between different Base45 implementations across different systems and languages.

Conclusion: The Right Tool for QR-Optimized Data Encoding

Our Base45 encoder decoder online is the most comprehensive tool available for working with Base45-encoded data, combining accurate RFC 9285 implementation with real-time validation, step-by-step visual encoding, three-way comparison with other encodings, file support, batch processing, and multiple input/output encoding formats—all running privately in your browser without any data transmission. Whether you need to encode Base45 online for a QR code payload, decode Base45 online to extract digital health certificate data, debug a Base45 implementation, or simply explore how this encoding compares to Base64 and Base32 for your specific data, our free online Base45 encoder decoder provides the accuracy, insight, and flexibility you need. Bookmark this tool as your go-to Base45 converter online free resource for all Base45 encoding and decoding tasks.

Frequently Asked Questions

Base45 is a binary-to-text encoding scheme defined in RFC 9285 (September 2022). It uses exactly 45 characters: 0-9, A-Z, space, $, %, *, +, -, ., and /. These 45 characters are precisely the QR code alphanumeric character set. Base45 encodes 2 input bytes into 3 output characters (or 1 byte into 2 characters for the last odd byte). The primary motivation is efficient storage in QR codes: since all Base45 characters fit in QR's alphanumeric mode (5.5 bits/char), Base45-encoded data takes fewer bits in a QR code than Base64 (which requires binary mode at 8 bits/char).

Base64 uses characters (lowercase letters, +, /, =) that fall outside the QR code alphanumeric character set (0-9, A-Z, and 9 symbols). When QR codes contain characters outside this set, the QR encoder must switch to binary mode (8 bits per character) instead of alphanumeric mode (5.5 bits per character). Base45 uses only QR alphanumeric characters, so a Base45 string always encodes in QR alphanumeric mode. Even though Base45 produces ~50% more characters than Base64, the per-character bit savings (5.5 vs 8 bits) make Base45 QR codes more compact than Base64 QR codes for the same binary data.

The EU Digital COVID Certificate (EU DCC) is a standardized digital health certificate used across the EU. Technically, the certificate data goes through this pipeline: JSON health data → CBOR-encoded → COSE (signed) → zlib/DEFLATE compressed → Base45 encoded → "HC1:" prefix added → QR code. Base45 is used in the second-to-last step to encode the compressed binary certificate data as a QR-alphanumeric string. To decode a DCC, strip the "HC1:" prefix, Base45-decode the remainder to get compressed bytes, then decompress with zlib. Our tool handles the Base45 decode step.

For each pair of input bytes [b0, b1]: compute n = b0 × 256 + b1 (range 0–65535). Then: char[0] = ALPHABET[n mod 45], char[1] = ALPHABET[(n ÷ 45) mod 45], char[2] = ALPHABET[n ÷ 2025]. For a trailing single byte b: char[0] = ALPHABET[b mod 45], char[1] = ALPHABET[b ÷ 45]. Example: "H" (72) and "i" (105) → n = 72×256+105 = 18537 → 18537%45=42='Q', (18537÷45)%45=12='C', 18537÷2025=9='9' → "QC9". Use the Visual tab to see this for your own input.

It depends on the context. In raw character count, Base64 is more efficient: it adds 33% overhead (3 bytes → 4 chars) versus Base45's 50% overhead (2 bytes → 3 chars). For UTF-8 text storage, JSON, or HTTP APIs, Base64 is the better choice. However, in QR codes, Base45 is significantly more efficient: Base45 output uses QR alphanumeric mode (5.5 bits/char), while Base64 output requires binary mode (8 bits/char). So 100 bytes → 137 Base64 chars → 1096 QR bits, versus 100 bytes → 150 Base45 chars → 825 QR bits. Base45 QR codes are about 25% smaller. Use our Compare tab to see exact numbers for your data.

The Base45 alphabet (RFC 9285) consists of exactly 45 characters in this order: 0-9 (values 0-9), A-Z (values 10-35), space (36), $ (37), % (38), * (39), + (40), - (41), . (42), / (43), : (44). Any character not in this set is invalid in a Base45 string. Common invalid characters include lowercase letters (a-z), @, #, !, equals (=), brackets, quotes, and all Unicode characters above ASCII 127. Note that the space character IS valid in Base45 (it's value 36), unlike most other encodings. Use our Validate tab to identify invalid characters in any string.

A valid Base45 string must have a length where (length mod 3) ≠ 1. In other words, valid lengths are 0, 2, 3, 5, 6, 8, 9, 11, 12... — any length that is either divisible by 3 or leaves remainder 2 when divided by 3. A string whose length mod 3 equals 1 would imply a fractional input byte, which is impossible. For example, a 4-character Base45 string (4 mod 3 = 1) is always invalid and should be rejected by any decoder. Our validator checks this condition and reports it clearly.

Yes. Use the File tab, drop any file (PDF, image, zip, etc.) onto the drop zone, select "Encode → Base45", and click Run. The tool reads the raw bytes of the file and encodes them as a Base45 text string. You can copy the result or download it as a .b45 file. To decode back, provide the Base45 text (or .b45 file), select "Decode → File", and click Run to reconstruct the original binary. Note that Base45 increases file size by 50%, so this is practical mainly for small files (documents, certificate data, etc.) not large media files.

Yes, completely safe. This tool runs 100% in your browser using JavaScript — no data is ever sent to any server, stored anywhere, or accessible to any third party. Health certificate QR data, vaccination records, and any other sensitive information you decode or encode stays entirely on your local device. You can verify this by using your browser's developer tools network tab while using the tool — zero network requests are made during encoding or decoding. This makes it suitable for handling personal health data, identity credentials, and other privacy-sensitive information.

The space character is included because the QR code alphanumeric character set includes it, and Base45's design goal was to use exactly the QR alphanumeric set for maximum QR efficiency. The QR alphanumeric set has 45 characters (10 digits + 26 letters + 9 symbols including space), which is why the encoding is called "Base45." If the designers had excluded the space, they would have had only 44 characters, making the encoding less efficient (since 44^3 = 85184 < 65535 would work but 44^2 = 1936 < 255 would fail for single-byte encoding). Including space completes the natural 45-character set perfectly. This does mean that Base45 strings can contain spaces, which our tool handles correctly.