Base64 Encoder/Decoder

Convert text to Base64 for HTTP headers, data URIs, JSON payloads and configuration files — or decode Base64 you’ve found in logs, tokens or emails back into readable text. Accented letters, other alphabets and emoji are handled correctly as UTF-8.

This tool runs entirely in your browser. Your files and text are processed on your own device and are never uploaded to our servers.

How to use the Base64 Encoder/Decoder

  1. Choose Encode to turn text into Base64, or Decode to turn Base64 back into text.
  2. Type or paste into the left box — the result updates instantly on the right.
  3. For URLs and file names, tick URL-safe to use - and _ instead of + and / and drop the = padding.
  4. Copy or download the result, or use Swap to feed it back in and reverse the conversion.

Examples

Encoding a short message

Input
Hello, world!
Result
SGVsbG8sIHdvcmxkIQ==

Accents and emoji (UTF-8)

Input
café 👍
Result
Y2Fmw6kg8J+RjQ==

Decoding the payload of a JWT

JWTs use URL-safe Base64 without padding. Paste the middle section of the token to read its claims — decoding is local, so the token never leaves your browser.

Base64 is encoding, not encryption

Base64 represents any data using 64 safe characters so it can travel through systems designed for text. Anyone can decode it — it provides no secrecy at all. Never rely on Base64 to protect passwords or personal data; use proper encryption instead.

Frequently asked questions

Is my text sent anywhere?

No. Encoding and decoding happen in your browser, so secrets and tokens you paste stay on your device.

Why does the decoded result say it contains binary data?

The Base64 represents a file (such as an image or PDF) rather than text. You can download the decoded bytes as a file, and images can be previewed with the Base64 Image Converter.

What is URL-safe Base64?

A variant (RFC 4648 §5) that replaces + with - and / with _ and usually omits the = padding, so the result can be used in URLs and file names without escaping. The decoder accepts both variants automatically.

Why is Base64 longer than the original?

Every 3 bytes become 4 characters, so Base64 is about 33% larger than the data it encodes, plus up to two = padding characters.

Everything you need. One simple place.

Free, fast online tools for text, PDFs, images, data and everyday maths. Every tool runs entirely in your browser, so your files stay on your device.

  • Privacy-first processing
  • No sign-up required

© 2026 Toolora. All rights reserved.

Built for speed and privacy