Base64 Encoder/Decoder
Encode UTF-8 text or files as standard Base64, or decode Base64 into UTF-8 text. Files up to 10 MB are processed locally in your browser and are not uploaded.
Processed locally in your browser — nothing you enter here is uploaded.
Encode UTF-8 text or files as standard Base64, or decode Base64 into UTF-8 text. Files up to 10 MB are processed locally in your browser and are not uploaded.
Base64 encoding is a way to convert binary data into ASCII text. It sounds technical, but it's used everywhere—web development, email systems, data storage, APIs. Understanding Base64 helps you work with data that needs to be text-safe, URL-safe, or stored in text-only formats.
Base64 takes binary data (like images, files, or binary strings) and converts them into a string of ASCII characters. It uses 64 characters: A-Z, a-z, 0-9, plus + and / (with = for padding). This encoding ensures the data can be transmitted or stored in systems that only handle text. The encoded data is about 33% larger than the original, but it's text-safe.
Data URIs are a common use for Base64 encoding. Instead of hosting images on a server, you can embed them directly in HTML or CSS using Base64. The image data is encoded and included in the code. This eliminates HTTP requests, which can improve performance for small images. It's also useful for offline applications or when you need self-contained documents.
Email systems use Base64 for attachments and binary content. Email protocols were originally designed for text only. Binary data like images or PDFs needs to be encoded as text to be transmitted. Base64 provides this encoding. MIME (Multipurpose Internet Mail Extensions) uses Base64 for binary attachments. This is why email attachments work—they're Base64 encoded.
API development often uses Base64 for binary data transmission. When you need to send binary data through an API that expects JSON, you Base64 encode it. The API receives text instead of binary, which it can handle. The receiving system decodes it back to binary. This is common for image uploads, file transfers, and binary payloads.
Web storage sometimes uses Base64 for binary data. LocalStorage and sessionStorage only store strings. If you need to store binary data, you Base64 encode it first. This is useful for caching images, storing user-uploaded files temporarily, or saving binary data in the browser. Just remember the 33% size increase when planning storage.
URL encoding with Base64 is possible, but Base64 uses + and / which aren't URL-safe. URL-safe Base64 variants use - and _ instead. This is important when putting Base64 data in URLs. Standard Base64 in URLs can break or be misinterpreted. URL-safe Base64 ensures proper transmission.
Authentication systems use Base64 for basic authentication. Username and password are combined and Base64 encoded (not encrypted—this is encoding, not security). Basic auth is simple but not secure without HTTPS. Understanding Base64 helps you work with authentication tokens and credentials.
Certificate encoding uses Base64. SSL certificates, public keys, and other cryptographic data are often stored as Base64-encoded strings. This allows them to be stored in text files, transmitted as text, or included in configuration. The PEM format used for certificates is essentially Base64-encoded binary data.
This tool encodes UTF-8 text or an uploaded file as standard Base64. It decodes Base64 into UTF-8 text. File encoding accepts files up to 10 MB; it does not reconstruct a downloaded binary file from decoded input.
Base64 is a binary-to-text encoding scheme that represents binary data in an ASCII string format. It's commonly used to:
Share this utility
Send the tool, not any text or files you entered. Input is never added to the share URL.
Continue the workflow
Step 5 of 5. Keep the context and finish the related checks.
Where this comes from
Defines the standard and URL-safe Base64 alphabets and padding rules.
Explains Base64 handling of binary data in the browser.
Links last checked August 13, 2026.
Step-by-step help
Keep working