Skip to content

Free Base64 Encoder & Decoder

Encode text to Base64 and decode Base64 strings back to text. Supports standard and URL-safe Base64. Browser-based. Free, with no sign-up required — everything happens right in your browser, so nothing you enter is sent to a server.

💻 Base64 Encoder & Decoder

How the Base64 Encoder & Decoder Works

Choose Encode or Decode, paste your text and press the button. To encode, the tool first converts your text to UTF-8 bytes, so accented letters, symbols and emoji work correctly, and then writes those bytes in Base64. To decode, it reverses the process and shows the original text. Tick URL-safe to use the variant that swaps + and / for - and _ and drops the = padding, which is the form used in JWTs and web addresses.

Base64 is an encoding, not encryption. It represents bytes with 64 printable characters so they can travel through systems that only handle text, and anyone can decode it. Because every three bytes become four characters, the output is about a third larger than the input. If decoding fails, the string is probably incomplete, contains characters outside the Base64 alphabet or decodes to bytes that are not valid text, as happens with images or other binary files.

Practical Use Cases

  • Decode a Base64 value from an API response, configuration file or email header.
  • Encode a short string for use in a data URI, a basic authentication header or an environment variable.
  • Convert between standard and URL-safe Base64 when working with tokens.
  • Check what a suspicious-looking encoded string actually contains.

Tips for Best Results

  • Never put secrets in Base64 and think they are protected. Treat any encoded value as readable by anyone who sees it.
  • Choose URL-safe mode for tokens in links, filenames and JWT parts, and use standard mode for email, data URIs and most APIs.
  • If a decoded string looks like gibberish, it may contain binary data such as an image or compressed file, which cannot be shown as text.

Frequently Asked Questions

No. It only changes how data is written, and anyone can reverse it. Never use it to protect passwords or secrets.
It replaces + with - and / with _ and removes the = padding, so the result can be placed in a URL or filename without further escaping. JSON Web Tokens use this form.
Yes. Text is converted to UTF-8 before encoding and decoded as UTF-8 afterwards, so non-English characters survive the round trip.
The input may be truncated, contain spaces or characters that are not Base64, or represent binary data rather than text. Check that you copied the whole string.
No. The encoding and decoding run in your browser.