Base64 is a way of writing any data, whether text, images or files, using only 64 safe characters (A–Z, a–z, 0–9, + and /). That makes it easy to embed in emails, JSON, HTML, CSS and URLs. Developers meet it constantly: in API tokens and JWTs, HTTP Basic auth headers, data: image URIs, email attachments and config files. This free Base64 encoder and decoder converts in both directions instantly as you type. Unlike many quick tools that break on accented letters or emoji, it's UTF-8 safe: "café ☕" encodes and decodes correctly. Switch on URL-safe mode to use - and _ instead of + and / and drop the = padding, as used in JWTs and web tokens. When decoding, it accepts either style, ignores spaces and line breaks, and tells you clearly if the input isn't valid Base64. You can also encode a file, such as a small image or PDF, into Base64 or a ready-to-paste data URI, and decode Base64 back into a file you can download. A reminder: Base64 is an encoding, not encryption, so anyone can decode it, and you should never rely on it to hide secrets. Everything runs locally in your browser.
Encode or decode
File to Base64
How to use it
- Choose Encode or Decode.
- Type or paste your text; the result updates live.
- Tick URL-safe for JWT-style Base64.
- Or choose a file to get its Base64 or data URI.
Common uses
- Inline images in CSS or HTML as data URIs.
- Reading the payload of a JWT (the middle part).
- HTTP Basic auth: Base64 of
user:password.
FAQ
Is Base64 encryption?
No. It’s a reversible encoding that anyone can decode, so use real encryption for secrets.
Why does Base64 make data bigger?
Every 3 bytes become 4 characters, about 33% larger.
What is URL-safe Base64?
A variant that uses - and _ instead of + and /, usually without = padding, so it’s safe in URLs and file names.
Is my data uploaded?
No. Encoding and decoding happen in your browser.
Comments
Post a Comment