ruxox
Start
Start
Base64

Base64 Encoder & Decoder

Encode and decode Base64 strings entirely in your browser. Safe for config strings, API tokens, and data URIs. No data sent to any server.

Base64 Encoder & Decoder

Runs entirely in your browser — no server calls, no tracking.

Enter text and click Convert.

🔒 Your data never leaves this tab. This tool has no backend.

About this tool

About the Base64 Encoder & Decoder

Base64 encoding converts arbitrary binary data — or any string — into a subset of printable ASCII characters. It is used in HTTP Basic Authentication headers, data URIs for inline images, JWT payloads, and environment variable values when the raw value contains characters that would break shell parsing or YAML formatting.

Common uses

API credentials: many services encode client_id:client_secret in Base64 and send it as an Authorization: Basic ... header. Data URIs: images and fonts can be embedded directly in CSS or HTML as data:image/png;base64,.... Config values: TLS certificates, SSH keys, and JSON blobs are often Base64-encoded before storage in environment variables or Kubernetes secrets.

Base64 is not encryption

Base64 is an encoding, not encryption. Anyone who receives a Base64 string can decode it instantly — including with this tool. Never use Base64 to "protect" sensitive data. Use it only as a transport encoding for data that is already secured or that does not need to be secured.

This tool handles Unicode correctly by using encodeURIComponent + btoa for encoding and the reverse for decoding, preventing the common "string contains characters outside Latin1" error that plain btoa throws with multi-byte characters.

FAQ

Frequently asked questions

Why does Base64-encoded output sometimes end in = or ==?
Base64 works by grouping 3 bytes into 4 characters. When the input length isn't a multiple of 3, padding characters (=) are added to make the output length a multiple of 4. One = means one byte of padding; == means two. Some implementations omit padding (URL-safe Base64); this tool includes it.
What is the difference between standard Base64 and URL-safe Base64?
Standard Base64 uses + and / as the 62nd and 63rd characters. URL-safe Base64 (used in JWTs and many APIs) replaces these with - and _ so the string can be embedded in a URL without percent-encoding. This tool uses standard Base64; swap +// if you need URL-safe.
Does this tool work with binary data or just text?
This browser tool works with UTF-8 text. For binary data (images, PDFs, arbitrary bytes), you would need a server-side tool or a local script. The tool correctly handles all Unicode characters by converting to UTF-8 bytes before encoding.
Custom software

Need custom integrations or API tooling built?

ruxox builds production web apps and API integrations for growing businesses. Free estimate in 48 hours.