Free Base64 Encoder & Decoder

What Is Base64?

Base64 is a binary-to-text encoding scheme that represents binary data — such as images, audio files, and other binary content — using only 64 printable ASCII characters. The characters used are A–Z (26 characters), a–z (26 characters), 0–9 (10 characters), and two additional characters that vary by variant: + and / in the standard Base64 alphabet, or - and _ in the URL-safe variant (Base64url). Padding characters (=) are used to ensure the encoded output length is always a multiple of four characters.

The name "Base64" comes from the encoding base: 64 possible characters per position, which requires 6 bits of information to encode each character (2⁶ = 64). Since each original byte is 8 bits, every 3 bytes (24 bits) of input are encoded as 4 Base64 characters (24 ÷ 6 = 4). This means Base64-encoded data is approximately 33% larger than the original binary data — a tradeoff accepted because it makes binary data safe to include in text-based systems like email, JSON, XML, CSS, and HTML.

When Do Developers Use Base64?

Base64 encoding appears throughout modern web development and software engineering. Here are the most common scenarios:

• Data URIs in HTML and CSS: Small images, fonts, and icons are commonly inlined into HTML or CSS as Base64-encoded data URIs. This eliminates additional HTTP requests: <img src="data:image/png;base64,iVBORw0KGgo...">. Useful for small images that would otherwise require a separate request, though generally not recommended for images over a few kilobytes.
• JSON and XML payloads: When binary data needs to be included in a JSON or XML document, Base64 is the standard approach. REST APIs commonly encode file uploads, thumbnails, certificates, and binary blobs as Base64 strings within JSON bodies.
• Email attachments (MIME): Email was originally designed only for ASCII text. The MIME standard specifies that binary attachments — images, PDFs, Word documents — must be Base64-encoded before being included in email messages. Your email client handles this transparently when you attach files.
• HTTP Basic Authentication: The HTTP Basic Auth header encodes credentials as Base64(username:password). While trivially decodable (it is not encryption), it allows credentials to be safely included in headers that only support ASCII characters. Always use HTTPS with Basic Auth.
• Storing binary data in databases: Relational databases store data as text or binary columns. Base64 is sometimes used to store binary data in text columns, though dedicated binary column types (BLOB, BYTEA) are generally preferred.
• Cryptographic keys and certificates: PEM-formatted SSL/TLS certificates and private keys are Base64-encoded DER certificates wrapped in header/footer lines. This allows cryptographic binary data to be pasted into text editors and configuration files.

Base64 vs Base64url

The standard Base64 alphabet uses + and /, which have special meanings in URLs and query strings. To safely include Base64-encoded data in URLs without percent-encoding, the URL-safe variant (Base64url) replaces + with - and / with _. Base64url is used in JSON Web Tokens (JWTs), OAuth tokens, and URL-safe identifiers. This tool uses standard Base64 (not Base64url).

Is Base64 Encryption?

No. Base64 is encoding, not encryption. It transforms binary data into a text-safe format using a deterministic, reversible, publicly-known algorithm with no key involved. Anyone with the encoded string can decode it instantly — there is no secret. Base64 does not provide any security or confidentiality. Do not use it to obscure passwords, API keys, or sensitive data in client-side code or publicly accessible files, as it provides zero protection against anyone who looks at the encoded string.

Frequently Asked Questions

Related Free Tools