Base64 Encode & Decode
Encode and decode text or files using Base64 encoding.
By Syed Mubashir Ali · Last updated
Where base64 actually gets used
Email attachments are the oldest use: email was designed for text, so attachments get base64-encoded to ride along. Data URIs in web pages are the most visible modern use: that long data:image/... string in the HTML is a base64-encoded image, no separate download needed. API keys and basic-auth credentials are routinely base64-encoded in headers (which, again, is encoding for transport, not security).
The rule of thumb: base64 when you must put binary data somewhere that only accepts text. If both ends handle binary natively (a file upload, a database blob column) skip the encoding and save the 33% size overhead.
How to Use Base64 Encoder
- 1For text: choose Encode or Decode and type or paste. The result updates as you type; tick URL-safe for Base64 that can go in a web address or a JWT.
- 2For a file: switch to 'File → Base64' and select it. Copy the Base64 on its own or as a data URI, or download it as a text file.
- 3To turn Base64 back into a file, switch to 'Base64 → File' and paste it (a data URI works too). Images are previewed, and the file type is recognised from its contents so it downloads with the right extension.
- 4If text you decode turns out to be a file rather than text, the tool says so and offers to download it, instead of showing garbled characters.
- 5Use the output anywhere that accepts Base64: HTML img src attributes, CSS backgrounds, API payloads, etc.
- 6Encoding an image for embedding in HTML or CSS? Convert it to base64 here, then use it as data:image/png;base64,... and you need no separate image file.
Frequently Asked Questions
What is Base64 encoding?
Base64 is an encoding scheme that converts binary data (or any text) into a string of ASCII characters using 64 printable characters. It's commonly used to transmit binary data over text-based protocols like email (MIME), JSON APIs, and HTML attributes.
Why would I need to Base64 encode a file?
Embedding files as Base64 strings in HTML, CSS, or JSON allows you to include images, fonts, or other assets inline without separate HTTP requests. It's also used to send binary file content through APIs that only accept text/JSON.
Does Base64 encrypt my data?
No. Base64 is encoding, not encryption. Anyone with a Base64 decoder can read the original content. Never use Base64 for security: use proper encryption for sensitive data.
What is URL-safe Base64?
A variant (RFC 4648 'base64url') that swaps + and / for - and _ and usually drops the = padding, because +, / and = have special meanings in web addresses. JWTs and many APIs use it. Tick URL-safe to encode that way; decoding accepts either kind, with or without padding.
Why is my Base64 string longer than the original?
Base64 encoding increases size by approximately 33%. Every 3 bytes of input become 4 Base64 characters. This is the inherent trade-off of representing binary data in a text-safe format.
Is base64 encryption?
No. And this matters. Base64 is an encoding, not encryption. It converts binary data to text so it can travel through text-only systems, but anyone can decode it instantly. Never use base64 to 'protect' passwords, tokens, or sensitive data. It's like writing a message backwards: it looks hidden until someone tilts their head.
Why does the encoded text get longer?
Base64 represents every 3 bytes of input as 4 characters of output, so the result is about 33% larger than the original. That's the price of making binary data text-safe. For small payloads (tokens, short files) it doesn't matter; for large files, consider whether you really need to embed them.
Does it remember what I typed?
Only if you leave "Remember recent inputs" ticked: it keeps the last five things you typed here in this browser, and nothing is sent anywhere. Pick one from the Recent menu to bring it back, or press "Clear recent" to forget them. Unticking the box stops it and wipes the list.
About Base64 Encoder
The Base64 Encoder and Decoder is a versatile tool for developers and technical users who need to convert between raw text or binary files and their Base64 representations. Base64 encoding is ubiquitous in web development: from embedding images inline in HTML and CSS, to encoding credentials in HTTP Basic Auth headers, to sending file attachments through JSON APIs.
The Text Mode handles any Unicode text, correctly encoding multi-byte characters (including emoji, Arabic, Chinese, and other non-ASCII text) by first converting to UTF-8 bytes before encoding. This ensures the output is valid and decodable across all platforms and programming languages.
The File Mode reads any file you select and generates its data URI representation: the format used to embed files directly in web pages. The complete data URI includes the MIME type prefix (e.g. data:image/png;base64,) followed by the encoded content. The copy button extracts just the Base64 portion for use in API calls and other contexts that expect raw Base64.
All encoding and decoding happens entirely in your browser using the built-in btoa() and atob() functions combined with TextEncoder/TextDecoder for proper Unicode handling. Your files and text never leave your device, making this tool safe for encoding sensitive configuration files, private keys, and confidential documents.
Base64 is the duct tape of data encoding: it takes anything (an image, a PDF, a binary blob) and turns it into plain text that can survive email, JSON, HTML, and URLs. Developers use it to embed small images directly in code, to encode API credentials, and to pass binary data through systems that only speak text.