Free Base64 Encoder & Decoder . Convert Text and Files Instantly Online
Encode any text or file to Base64 or decode Base64 strings back to plain text instantly, free, and 100% private.
Base64 Orbit
Base64 Encoder & Decoder
Follow these three steps to convert data between binary payloads and ASCII string formats.
Data Input
Paste your raw Text String, upload a small file, or enter an existing Base64 block into the workspace to prepare your source data.
Mode Selection
Choose either Encode to secure your data in ASCII characters, or Decode to restore the payload back to its native, human-readable format.
Output Retrieval
Inspect the generated values in the Live Preview field. Click the action button to instantly copy the script or download it safely as a file asset.
What Is Base64 and Why Does It Exist?
Base64 is a binary-to-text encoding scheme that converts binary data raw bytes, images, files, or any string of characters into a safe, printable ASCII text format. It was designed to solve a very specific and fundamental problem in computing: some communication systems and protocols were built to handle only plain text, not raw binary data. When you need to transmit binary content like an image file, an audio clip, or a PDF through a text-only channel, Base64 provides a reliable bridge.
The name comes from the fact that the encoding uses exactly 64 printable ASCII characters the uppercase letters A–Z, lowercase letters a–z, the digits 0–9, plus the characters + and / with = used as padding. Every character in this set is safe to use in any text-based system email, HTML, JSON, XML, URLs, and databases without triggering formatting errors or data corruption.
Base64 is not encryption. It does not protect the content of your data from being read by anyone who sees it. A Base64-encoded string can be decoded back to its original content by anyone with a decoder including the free one on this page. Its purpose is safe transport and embedding, not security.
Base64 is one of the most widely used encoding standards on the internet today embedded in email attachments, HTML image tags, JWT authentication tokens, API responses, and data URIs used by web developers across the United States every single day.
How Base64 Encoding Actually Works Step by Step
Understanding the mechanics of Base64 encoding helps you use it correctly and confidently. Here is exactly how the encoding process works, explained in plain language with a real example:
Convert Characters to Binary
Each character in your input string is first converted to its ASCII code, then to an 8-bit binary representation. For example, the letter "M" becomes ASCII code 77, which in binary is 01001101.
Group into 6-Bit Chunks
The binary stream is regrouped into 6-bit blocks instead of 8-bit bytes. Since 2 is divisible by both 6 and 8, every 3 input bytes (24 bits) map perfectly to 4 Base64 characters (4 × 6 bits = 24 bits). This 3-to-4 ratio is why Base64-encoded output is always approximately 33% larger than the original input.
Map Each 6-Bit Value to a Base64 Character
Each 6-bit chunk has a decimal value from 0 to 63. This value is used as an index into the Base64 character table to select the corresponding printable ASCII character. Values 0–25 map to A–Z, 26–51 to a–z, 52–61 to 0–9, 62 to +, and 63 to /.
Add Padding with = Characters
If the input length is not divisible by 3, one or two = padding characters are added to the end of the encoded string to make the output length a multiple of 4. You will frequently see Base64 strings ending in == or = this is expected and correct.
Live Encoding Example — "Hello" to Base64
ASCII codes: 72 101 108 108 111
Binary: 01001000 01100101 01101100 01101100 01101111
6-bit groups: 010010 000110 010101 101100 011011 000110 1111
Base64 output: SGVsbG8=
You can verify this yourself right now — paste Hello into our encoder above and you will get SGVsbG8= every single time. Paste SGVsbG8= into our decoder and you get Hello right back. That is Base64 completely reversible, completely deterministic.
The Complete Base64 Character Table
Every Base64-encoded string is built exclusively from the 64 characters in this table. Understanding the table helps you visually identify Base64 output and diagnose encoding errors instantly:
| Index | Character | Index | Character | Index | Character | Notes |
|---|---|---|---|---|---|---|
| 0–25 | A – Z | 26–51 | a – z | 52–61 | 0 – 9 | Letters & digits |
| 62 | + | 63 | / | Pad | = | Special chars |
⚠️ URL-Safe Base64 A Common Variant
Standard Base64 uses + and / characters that have special meaning in URLs and can break query strings. URL-safe Base64 (also called Base64url) replaces + with - and / with _ to make the output URL-safe. JWT tokens use Base64url. If you see a Base64-looking string with hyphens instead of pluses, that is the URL-safe variant.
Real-World Uses of Base64 — Where You Encounter It Every Day
Base64 is invisible infrastructure you encounter its output constantly without realizing it. Here are the most common real-world applications that American developers, marketers, and everyday users deal with regularly:
Email Attachments (MIME)
Email was originally designed as a plain text protocol. MIME (Multipurpose Internet Mail Extensions) uses Base64 to encode file attachments PDFs, images, Word documents into ASCII text so they can be safely transmitted through email servers. Every attachment you send or receive in Gmail, Outlook, or Apple Mail is Base64-encoded under the hood.
Embedded Images in HTML & CSS
Web developers embed small images directly into HTML or CSS files as Base64 Data URIs eliminating an extra HTTP request for the image file. An embedded logo or icon looks like src="data:image/png;base64,iVBOR..." in the HTML source. This technique is widely used to optimize page speed for small, frequently used assets.
JWT Authentication Tokens
JSON Web Tokens (JWTs) the standard authentication mechanism used by most modern US web applications are built from three Base64url-encoded sections separated by dots: a header, a payload, and a signature. If you have ever seen a long token like eyJhbGc... in an API response or browser cookie, that is a JWT with Base64url encoding.
API Authentication Headers
HTTP Basic Authentication encodes credentials as a Base64 string in the request header. When an API or web service uses Basic Auth, your username and password are combined as username:password, Base64-encoded, and sent as Authorization: Basic [encoded string]. Developers testing APIs with tools like Postman encounter this daily.
Storing Binary Data in Databases
Some database configurations or APIs require binary data like images or cryptographic keys to be stored or transmitted as text strings rather than raw binary blobs. Base64 encoding converts any binary content into a safe ASCII string that fits cleanly into a text column, a JSON field, or an XML element without corruption or escaping issues.
Cryptographic Keys & Certificates
SSL/TLS certificates, SSH public keys, PGP keys, and other cryptographic assets are almost universally distributed in Base64-encoded PEM format. The content between -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- is pure Base64. System administrators and DevOps engineers across the USA work with these files daily.
Base64 Encoding vs. Other Encoding Methods Full Comparison
Base64 is one of several encoding methods used in web development and data transmission. Here is how it compares against the most common alternatives — so you always choose the right tool for your specific use case:
| Encoding | What It Does | Size Increase | Reversible? | Best Used For |
|---|---|---|---|---|
| Base64 | Binary to 64-char ASCII text | ~33% | ✔ Yes | Emails, JWTs, APIs, data URIs |
| Hex (Base16) | Binary to 16-char hex digits (0–9, a–f) | ~100% | ✔ Yes | Color codes, hash display, debugging |
| URL Encoding | Replaces unsafe URL chars with %XX codes | Varies | ✔ Yes | Query strings, form data in URLs |
| HTML Entities | Replaces special HTML chars with &name; codes | Varies | ✔ Yes | HTML content with special characters |
| AES / RSA | Encrypts data requires a key to decrypt | ~33%+ | ✔ With key | Protecting sensitive data true security |
| MD5 / SHA | Produces a fixed-length hash of input data | Fixed size | ✗ No | Checksums, password hashing, file integrity |
💡 Key Takeaway
Use Base64 when you need to safely transport or embed binary data in text-based systems. Use AES encryption when you need to protect data from unauthorized access. These are entirely different tools for entirely different problems and confusing them is one of the most common mistakes made by developers new to these technologies.
Base64 in Web Development Practical Examples American Developers Use Daily
For US web developers, Base64 is a constant companion across frontend, backend, and DevOps work. Here are the most common practical implementations with real code examples you can use directly:
Embedding an Image in HTML Using Data URI
Instead of linking to an external image file, small images can be embedded directly into HTML as Base64-encoded Data URIs eliminating an extra HTTP request and improving page load performance for small icons and logos:
Encoding API Credentials for HTTP Basic Auth
When authenticating with an API that uses HTTP Basic Authentication, credentials are Base64-encoded and passed in the Authorization header:
const credentials = 'username:password';
const encoded = btoa(credentials); // Base64 encode
fetch('https://api.example.com/data', {
headers: {
'Authorization': `Basic ${encoded}`
}
});
// To decode Base64 in the browser:
const decoded = atob(encoded); // Returns 'username:password'
Decoding a JWT Payload
JWT tokens consist of three Base64url-encoded sections. Decoding the middle section (the payload) reveals the token's claims the user data it carries without needing the signing key:
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VySWQiOiIxMjM0NSIsImVtYWlsIjoidXNlckBleGFtcGxlLmNvbSIsImV4cCI6MTcwMDAwMDAwMH0.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
// Decode the payload (middle section):
const payload = atob('eyJ1c2VySWQiOiIxMjM0NSIsImVtYWlsIjoidXNlckBleGFtcGxlLmNvbSIsImV4cCI6MTcwMDAwMDAwMH0');
// Result: {"userId":"12345","email":"user@example.com","exp":1700000000}
Common Base64 Errors How to Diagnose and Fix Them
Base64 encoding and decoding errors are a frequent source of frustration for developers at every level. Here are the most common issues American developers encounter and exactly how to fix them:
Invalid Character in Base64 String
Cause: The string contains a character not in the Base64 alphabet like whitespace, newlines, or characters from URL-safe Base64 (- or _).
Fix: Strip all whitespace before decoding. If using URL-safe Base64, replace - with + and _ with / before passing to a standard decoder.
Incorrect Padding "Invalid Base64 Length"
Cause: Base64 output must have a length divisible by 4. Some systems strip the trailing = padding characters, breaking decoders that require them.
Fix: Add padding back manually. Calculate how many = characters are needed: padding = (4 - length % 4) % 4, then append that many = characters before decoding.
Garbled Unicode After Decoding
Cause: The original content was UTF-8 text, but the decoder is treating it as ASCII producing garbled characters for anything outside the basic ASCII range.
Fix: After Base64 decoding, explicitly decode the result as UTF-8: new TextDecoder('utf-8').decode(decoded) in JavaScript. Our tool handles this automatically.
Line Breaks in Encoded Output Breaking Parsers
Cause: The MIME standard inserts a line break every 76 characters in Base64 output for email compatibility. Some decoders break on these newlines.
Fix: Strip all newline characters (\n and \r) from the Base64 string before passing it to your decoder. Our tool produces clean single-line output with no MIME line breaks.
Is Base64 Safe to Use? Security Considerations Every Developer Must Know
Base64 Is Encoding Not Encryption
This is the most critical security point about Base64 and it cannot be overstated: Base64 provides zero security protection. Anyone who can see a Base64-encoded string can decode it instantly using any Base64 decoder including the one on this page. Do not use Base64 to obscure passwords, API keys, personal information, or any sensitive data you do not want others to read. For data that needs to remain confidential, use proper encryption AES-256 for symmetric encryption or RSA for asymmetric.
Do Not Store Sensitive Data as Base64 in Client-Side Code
A common mistake among junior developers is storing API keys, database credentials, or access tokens as Base64 strings in JavaScript files, HTML source code, or mobile app bundles under the mistaken belief that Base64 encoding provides obfuscation. It does not. Any developer who inspects your page source or decompiles your app can decode those strings in seconds. Sensitive credentials belong in environment variables, server-side configuration, or a secrets management system never in client-accessible code in any encoding.
Our Tool Is 100% Client-Side Your Data Never Leaves Your Browser
Every encoding and decoding operation performed by our tool happens entirely within your browser using native JavaScript. No data is sent to our servers. No input is logged, stored, or analyzed. This makes our tool safe to use with sensitive strings API keys you need to inspect, JWT tokens you need to decode for debugging, or any other content where privacy matters. Close the browser tab and everything is gone.
Watch for Base64-Encoded Malware in Emails and Scripts
Attackers frequently use Base64 encoding to obfuscate malicious code embedding malware payloads, phishing URLs, and exploit scripts as Base64 strings inside emails, PDFs, and web pages to evade content filters. If you encounter an unexplained Base64 string in an email attachment, a JavaScript file, or a system log, use our decoder with caution do not execute or open whatever you decode without verifying its content in a secure environment first.
Common Questions
Everything you need to know about Base64 Encoding & Decoding.
What is Base64 encoding and how does it work?
How can I encode text or files to Base64 online?
How do I decode Base64 back to readable text?
What’s the difference between Base64 encoding and encryption?
Why is Base64 used in data transmission and programming?
Can Base64 be used to encode images or other binary files?
Developer Toolbox
Markdown Editor
Write, edit, and preview your markdown text live. A completely free tool that turns plain text into clean, ready-to-use HTML code without any fuss.
CSS Minifier
Shrink your CSS file sizes instantly. This free web optimizer cleans up messy spaces and extra code lines so your pages load much faster for visitors.
JS Minifier
Make your JavaScript code lightweight and compact for free. Remove bulk and unneeded elements without breaking your script's features or performance.
JSON Formatter
Fix and beautify cluttered JSON strings effortlessly. Our free tool adds neat indentation and clear structuring so you can read and debug data easily.
URL Encoder / Decoder
Safely convert web addresses with special characters into secure, readable links. A free tracking tool to make sure your URLs never encounter broken path errors.