Base64 Encoder/Decoder

Base64 Encoder/Decoder
Input: 0 Output: 0 Size change: 0%
About Base64

Base64 is a binary-to-text encoding scheme that represents binary data using 64 ASCII characters (A-Z, a-z, 0-9, +, /).

  • Email Attachments
  • Web Data URLs
  • Authentication Tokens
  • XML/JSON Data
  • Image Embedding
Character Set
A-Z Values 0-25
a-z Values 26-51
0-9 Values 52-61
+ Value 62
/ Value 63
= Padding
Quick Facts
  • Size Increase: ~33% larger
  • Reversible: Perfect encoding/decoding
  • Text Safe: Only printable ASCII
  • URL Safe: Optional variant available

How Base64 Encoding Works

Base64 maps every 3 bytes of input to 4 ASCII characters, which is why encoded output is roughly 33% larger than the original. It exists so binary data can travel through systems that only handle text - email bodies, JSON documents, URLs, HTML attributes. Encoding and decoding here happen entirely in your browser. The alphabet, the padding rules and the common pitfalls are covered in Base64 encoding explained.

The URL-safe variant replaces + and / with - and _ so encoded data survives inside URLs and HTTP headers - it is the variant JWT tokens use for all three of their segments. For embedding images in HTML or CSS as data URIs, the Image to Base64 converter handles files directly; for plain text, paste it here.

Base64 Questions

It turns binary data into text using 64 safe ASCII characters. Handy when you need to stuff an image into JSON, send binary through a text-only channel, or create data URIs.

Not even slightly. It's encoding, not encryption - anyone can decode it instantly. If you see 'base64' and think 'security', think again. It's just a transport format.

Embedding small images in CSS/HTML (data URIs), passing binary data through JSON APIs, email attachments (under the hood), or debugging that weird-looking string someone pasted in Slack.

About 33% bigger. Every 3 bytes become 4 characters. That's the cost of making binary data safe for text channels.