Base64 Encoder / Decoder
Encode and decode Base64 online — free.
Related tools
All Encoding & decoding tools →This free Base64 encoder and decoder converts text to Base64 and back, instantly. Base64 represents binary or text data using 64 safe ASCII characters, so it can travel through systems that only handle text — like data URIs, JSON, JWTs and email.
How to use it
- Paste your text or Base64 string.
- Choose Encode or Decode.
- Copy the converted result.
Frequently asked questions
What is Base64?
Base64 is an encoding that represents data using 64 printable ASCII characters (A–Z, a–z, 0–9, + and /), so binary content can be stored or sent as plain text.
Is Base64 a form of encryption?
No. Base64 is encoding, not encryption — anyone can decode it. Never use it to protect sensitive data; use real encryption for that.
When is Base64 used?
To embed images in HTML/CSS as data URIs, encode attachments in email, carry binary data in JSON or JWTs, and pass data safely through text-only channels.
What does Base64 Encoder / Decoder do?
Encode and decode Base64 online — free.
When would I actually use this?
Reading a payload someone sent you, embedding a small file in a config, and finding out why a query string breaks once it reaches the server.
What is the most common mistake?
Treating Base64 as a form of protection. It is an encoding, not encryption — anyone can decode it instantly, and a token pasted into a public issue is a leaked token.
How is Base64 Encoder / Decoder different from HTML Entity Encoder / Decoder?
They sit next to each other but answer different questions: HTML Entity Encoder / Decoder is the one to open when you need it to convert text to HTML entities and back, escaping <, >, &, quotes and optionally all non-ASCII characters. Pick whichever matches what you're starting from — both are free.
Is there a tool for the next step?
URL encoder / decoder is the closest one after this: Encode and decode URLs and query parameters.
What else is worth having open alongside it?
JWT decoder and UUID Validator / Decoder — they come up in the same task often enough to be worth a second tab.
Where do the figures come from?
The encodings follow their RFCs, so a round trip is lossless. URL encoding has two variants — one that encodes a space as %20 and one as a plus sign — and the tool says which it applies.