Base64 Encode / Decode
Convert plain text (including UTF-8) to and from Base64 encoding.
About this tool
The Base64 Encode / Decode tool converts plain text to Base64 and decodes Base64 strings back to readable text. Base64 represents arbitrary bytes using only 64 safe ASCII characters, which lets binary or Unicode data travel through channels that expect plain text — email bodies, JSON fields, data URIs, HTTP headers and config files.
It handles full UTF-8 correctly, so accented letters, emoji and non-Latin scripts round-trip without corruption. Everything is processed in your browser, making it a quick, private way to inspect tokens, embed small payloads or debug encoded values.
How to use
- Choose whether you want to encode text to Base64 or decode Base64 to text.
- Paste your input into the box — plain text for encoding, or a Base64 string for decoding.
- Read the converted output update instantly below.
- If decoding fails, check that the string is valid Base64 with correct padding.
- Copy the result with one click to use in your code, config or message.
Features
- Two-way conversion: encode to Base64 and decode back to text.
- Full UTF-8 support for accents, emoji and non-Latin scripts.
- Instant results as you type or paste.
- Clear handling of padding and invalid input when decoding.
- One-click copy of the output.
- Runs entirely in the browser — your data stays private.
Frequently asked questions
Is Base64 a form of encryption?
No. Base64 is an encoding, not encryption. Anyone can decode it, so never treat Base64 as a way to hide or secure sensitive data.
Does my text get uploaded when I encode or decode?
No. Conversion happens locally in your browser, so nothing you paste is sent to a server.
Why does encoded text look longer than the original?
Base64 represents every three bytes with four characters, so the output is roughly one-third larger than the input. That overhead is the trade-off for text-safe transport.
Why won't my Base64 string decode?
Decoding fails if the string contains characters outside the Base64 alphabet or has incorrect padding. Make sure it was not truncated and that URL-safe variants are converted back to standard Base64.