Text to Base64 — Free, in Your Browser
Base64 encoding shows up everywhere: embedding small files in data URIs, putting a token into a config line, encoding a password for a .htaccess file, or just understanding what that long blob in your error log actually is.
Base64 Encoder / Decoder
Encode & decode — 100% local
Why convert Text to Base64
Base64 encoding shows up everywhere: embedding small files in data URIs, putting a token into a config line, encoding a password for a .htaccess file, or just understanding what that long blob in your error log actually is. The standard move — pasting secrets into an online encoder — is backwards: you are sending the secret to a web form to make it *less* readable.
This encoder runs on your keyboard. Whatever you type — API keys, connection strings, certificates — is transformed locally and stays there. The output is exactly what every RFC 4648-compliant decoder will read back: the same bytes, different alphabet.
How to do it (3 steps)
- Type or paste the text to encode.
- The Base64 appears instantly as you type.
- Copy the encoded string into your config, code or document.
Technical note
Base64 expands size by ~33% (4 output characters per 3 input bytes) and adds up to two padding "=" characters — that is the format, not a bug. It is encoding, not encryption: anyone with the string can decode it in one step. Never treat Base64 as a way to hide a secret; treat it as a way to carry a binary or special-character payload through a text-only channel.
The mistake worth avoiding
The common mistake is encoding the wrong scope: encoding a whole URL when only one query parameter needed encoding — you end up with mangled colons and slashes where a working link should be — or encoding a file's path instead of its contents. Base64 carries bytes, so decide exactly which bytes you need to carry, and encode just that. And remember the security direction: this tool makes things more legible to machines, not less secret to people.
FAQ
- Is the text sent anywhere? No — encoding happens in your browser. This is the one converter where "no upload" is not a feature, it is the whole point.
- Why does the output have "=" signs? Padding. Base64 packs 3 bytes into 4 characters; if the input length is not a multiple of 3, the tail is padded with =.
- Will other systems decode it correctly? Yes — it is standard RFC 4648 Base64 with standard padding, which is what every mainstream tool and language expects.
- Why does my output differ in length from another encoder's? It should not — RFC 4648 Base64 is deterministic. Length differences come from different inputs: one tool encoded the file bytes, the other the file path, or one kept line breaks and the other stripped them. Compare the inputs, not the outputs.
Base64 Encoder/Decoder — full tool →