Base64 is not encryption.

If anyone can decode it without a key, it is not a secret. Base64 makes bytes easier to move; it does not make them confidential.

What Base64 actually does

Base64 is a reversible representation of bytes using a small text alphabet. Systems use it to include binary content in text formats, such as an attachment in email or a small binary value in JSON. The encoded text is usually about a third larger than the original bytes.

Hello → SGVsbG8= → Hello

There is no password, key, or authentication step in that round trip. “Base64 encryption” is a misleading phrase.

Encoding, hashing, and encryption

Common traps in engineering work

Basic authentication: the credentials in the Authorization header are Base64-encoded, not encrypted. Protect the connection with HTTPS and avoid copying real credentials into tickets or logs.

JWTs: a token’s header and payload are generally Base64URL-encoded. Reading a payload does not verify a signature, expiry, issuer, or audience. A readable token is not necessarily a trustworthy one.

Kubernetes Secrets: Base64 values in manifests are still sensitive. Encoding them is not a substitute for access controls or encryption.

Why convert locally?

Local conversion removes the need to send your input to a conversion service. On base64.date, text and file contents stay in browser memory; the application does not put them in storage or URLs.

This does not protect against a compromised browser, extensions with page access, clipboard managers, or someone looking at your screen. Use your organization’s approved offline tools for highly sensitive material. Clear the input when you are done, and treat downloaded files as untrusted unless you know their source.

Go to the source

Read RFC 4648 for the encoding specification, RFC 7617 for Basic authentication, and RFC 7519 for JWTs.