How to Encode Text and Files to Base64 — Complete Developer Guide

Base64 is a common encoding method used to represent text or binary data as readable ASCII characters. You may encounter it in email attachments, API requests, data URIs, configuration files, and web-development workflows. This guide explains what Base64 encoding does, when it is useful, its limitations, and how to encode text or supported files in your browser.

What Base64 Encoding Actually Does

Base64 is an encoding scheme that represents binary data, including text bytes and file data, using a set of printable ASCII characters. Standard Base64 uses uppercase letters, lowercase letters, digits, plus (+), and slash (/); equals signs (=) may appear as padding at the end.

Base64 is useful when binary data needs to be placed inside a text-based format or field. For example, it can be used in MIME email messages, JSON fields, data URIs, and some authentication or configuration workflows. It is not always the best option for large files because encoding increases the amount of data that must be stored or transferred.

Where You Encounter Base64 Every Day

Even if you have never intentionally used Base64, you interact with it constantly:

Email Attachments

When you attach a photo or PDF to an email, the email client encodes the attachment as Base64 before sending it through the SMTP protocol. The recipient's email client decodes it back. This happens automatically — you never see the Base64 string, but it is there in the raw email source. The MIME (Multipurpose Internet Mail Extensions) standard, defined in RFC 2045, specifies how Base64 is used for email attachments.

HTTP Basic Authentication

When you access a password-protected API or website, the browser combines your username and password with a colon (username:password) and Base64 encodes the result. This encoded string is sent in the Authorization header. Base64 does not encrypt these credentials. Basic Authentication should only be used over HTTPS/TLS, because the encoded username and password can be decoded by anyone who obtains the header value.

JSON Web Tokens (JWT)

JSON Web Tokens (JWTs) are commonly used in web applications. A JWT usually has three dot-separated parts: header, payload, and signature. The header and payload use Base64URL encoding, which is a URL-safe variation of Base64. You can decode these sections to inspect readable JSON, but decoding does not verify that a token is genuine, valid, or safe to trust. JWT handling and validation should be done by the application or a suitable library.

Data URIs in HTML and CSS

Small images and icons can be embedded directly in HTML or CSS as Base64-encoded data URIs. Instead of linking to an external image file, you include the image data right in the page. This can avoid a separate file request for a very small asset, but it also increases the HTML or CSS size and prevents that embedded asset from being cached separately. For most larger images, a normal image file is usually the better choice.

The Size Trade-Off You Need to Know

Base64 encoding makes data approximately 33% larger. This is not a bug — it is a mathematical consequence of how the encoding works. Every 3 bytes of original data are split into 4 groups of 6 bits. Each 6-bit group maps to one of the 64 characters. Three bytes in, four characters out. Four divided by three equals 1.33 — a 33% increase.

For small amounts of data — authentication tokens, short text strings, tiny icons — this increase is negligible. For large files, it adds up. A 10 MB file becomes about 13.3 MB when Base64 encoded. This is why you should not Base64-encode large files unless you have a specific reason to do so.

The exact output size depends on the original byte length and padding. Base64 output may also be wrapped with line breaks in some formats, such as MIME email messages.

How to Encode Text to Base64

The Base64 Encoder processes supported input locally in your browser. For text, a reliable Base64 implementation should first convert text into UTF-8 bytes before encoding it, so non-English characters and symbols are handled correctly. For decoding Base64 back to text, use our Base64 Decoder.

1. Open the Base64 Encoder tool
2. Type or paste your text into the input box
3. Click Encode to Base64 — the output appears instantly
4. Click Copy to grab the encoded string, or Download to save it as a .txt file

Questions People Ask About Base64

Explore Related Developer Tools

Further Reading

• RFC 4648 — The Base16, Base32, and Base64 Data Encodings (IETF Standard)
• RFC 7617 — The 'Basic' HTTP Authentication Scheme (IETF Standard)