Encode and decode Base64 strings.
How It Works
Upload / Input
Select your files or paste your content to get started.
Process
The work happens in this browser tab. Your file never leaves your device, so nothing is queued, stored or transmitted.
Download / Result
Get your results instantly. Download files or copy output in one click.
Features
How to use Base64 Encoder
Choose a direction
Encode text or a file to Base64, or decode Base64 back.
Provide the input
Paste the text or Base64 string, or add a file.
Convert
The result appears ready to copy.
Copy the whole thing
Base64 strings are long and truncation is the usual cause of a failed decode.
When to use Base64 Encoder
- Embedding a small image directly in HTML or CSS as a data URI
- Decoding a Base64 payload while debugging an API
- Moving binary data through a channel that only accepts text
- Inspecting the contents of a Base64-encoded configuration value
FAQ
Related Tools
Hash Generator
Generate SHA-1, SHA-256, SHA-384 and SHA-512 hashes.
Text Utilities
Case conversion, line cleanup, sorting and live text statistics.
Unit Converter
Convert between length, weight, volume, and more.
Length Converter
Convert between metric and imperial lengths.
About Base64 Encoder
Base64 represents binary data using only printable ASCII characters. Its purpose is transport: getting binary through systems that only handle text, such as email bodies, JSON payloads and URLs. The cost is size — Base64 output is about 33% larger than the input, because it uses six bits of information per eight-bit character.
The most important thing to understand is that Base64 is not encryption and offers no security whatsoever. It is a reversible encoding with no key, and anyone can decode it instantly. Base64-encoding a password or an API key hides it from a casual glance and from nothing else.
The common practical use is data URIs — embedding a small image directly into HTML or CSS instead of loading it as a separate file. This saves a network request, which is worthwhile for a small icon and counterproductive for anything larger, since the inflated data cannot be cached separately and bloats every page that includes it.
Tips and limits
- Base64 is encoding, not encryption. It provides no security at all.
- Output is about 33% larger than the input.
- Data URIs suit small icons; beyond a few kilobytes a separate cached file is better.
- Copy the entire string — truncation is the usual cause of decode failures.
- URL-safe Base64 replaces + and / with - and _; the variants are not interchangeable.