Standard Base64 uses + and / characters, which are special characters in URLs. URL-safe Base64 replaces these with - and _ so the string can be used in URLs and HTTP headers without percent-encoding.
Encode text or files to Base64, decode Base64 back to text or downloadable files, and preview Base64 image data URIs — all processed locally in your browser.
Text, file encoding, file decoding, or image preview.
Paste text or Base64, or drag and drop any file.
Click the button and see the result instantly.
Copy to clipboard or download the result as a file.
data:mime/type;base64,... string for CSS or HTML.
Click to upload or drag and drop any file
Any file type, up to ~10 MB recommended
<img> or CSS background-image snippet.
HTTP Basic Auth credentials are Base64-encoded in the Authorization header on every request.
The header and payload sections of every JSON Web Token are Base64URL-encoded strings.
Inline images in CSS and HTML use Base64 data URIs to embed image bytes directly in the file.
MIME email attachments are Base64-encoded so binary files can travel over text-based protocols.
Standard Base64 uses + and / characters, which are special characters in URLs. URL-safe Base64 replaces these with - and _ so the string can be used in URLs and HTTP headers without percent-encoding.
Base64 encodes every 3 bytes of binary data as 4 ASCII characters, resulting in approximately 33% overhead compared to the original binary size.
No. All encoding and decoding happens entirely in your browser using JavaScript. Nothing is sent to any server.