Base64 Encoder/Decoder
Encode text or files to Base64 and decode Base64 back to text — with full Unicode and URL-safe support.
Runs in your browser — nothing is uploadedMode
0 characters · 0 words
0 characters · 0 words
About Base64 Encoder/Decoder
Base64 represents binary data — images, files or any bytes — using only plain text characters. It is used in email attachments, data URLs, JSON APIs, JWT tokens and configuration files where raw binary is not allowed.
Encode text or files to Base64, or decode Base64 back to readable text. Unicode text and the URL-safe variant are fully supported, and everything is processed in your browser.
When to use it
- Embedding small images in HTML or CSS as data URLs.
- Decoding Base64 values in API responses and logs.
- Inspecting the payload of a JWT token.
- Encoding credentials or data for configuration files.
Tips for better results
- Base64 makes data about 33% larger — avoid it for large images on websites.
- Use URL-safe Base64 for values in URLs and file names.
- Never treat Base64 as protection for passwords or secrets.
How to use the Base64 Encoder/Decoder
- Pick Encode, Decode or Encode a file.
- Paste your text or Base64, or drop a file.
- Copy or download the result.
Frequently asked questions
Is Base64 encryption?
No. Base64 is an encoding that turns data into plain letters and digits. Anyone can decode it, so never use it to protect secrets.
What is URL-safe Base64?
It replaces + and / with - and _ and drops the = padding, so the result can be used in URLs and file names. The decoder accepts both forms automatically.
Why does decoding say it is not readable text?
The Base64 contains binary data such as an image. You can download the decoded bytes as a file instead.
Why does Base64 end with = signs?
The = characters are padding. Base64 works in blocks of three bytes, and padding fills the last block when the input length is not a multiple of three.
Is my data sent to a server?
No. Encoding and decoding happen in your browser.