Base64 Encode / Decode
Encode text to Base64 or decode Base64 back to readable text, with UTF-8 and URL-safe support.
Input: 0 characters · Output: 0 characters
How it works
Pick Encode to turn text into Base64, or Decode to turn a
Base64 string back into readable text — the result updates instantly as you type. Encoding
first converts your text to UTF-8 bytes, so accented characters, emoji and any other Unicode
survive the round trip. Tick URL-safe alphabet to get the - and
_ variant used in JSON Web Tokens and query strings (padding is dropped), or
Break lines every 76 characters for MIME/email style output.
Decoding is forgiving: line breaks and spaces are ignored, both the standard
(+/) and URL-safe (-_) alphabets are accepted, and missing
= padding is restored automatically. If the input contains characters that
cannot appear in Base64, or the bytes are not valid UTF-8 text, you get a clear message
instead of silent garbage. Everything runs in your browser with JavaScript — tokens, keys
and payloads are never uploaded, stored or logged.
Frequently asked questions
How do I encode text to Base64?
Leave the mode on Encode, then type or paste your text into the left box and the Base64 result appears in the right box instantly. Click Copy result to put it on your clipboard, or Download .txt to save it. To go the other way, switch to Decode, or press Swap to feed the result straight back in and reverse the direction.
Why does my Base64 string end with = signs?
Base64 turns 3 bytes of input into 4 characters, so when the input length is not a multiple of 3 the final block is padded with one or two = characters to fill it out. The padding carries no data. It only tells the decoder how many bytes that last block really holds. The URL-safe option drops it, and this decoder restores missing padding automatically.
Is Base64 encoding the same as encryption?
No. Base64 is an encoding, not encryption: anyone can decode it back in one click and no key is involved. It exists to carry binary data safely through text-only channels like email, JSON, data URIs and JWTs. Never use it to protect passwords or secrets, but because this tool runs entirely in your browser, pasting a token or key here is still safe, since nothing is uploaded.