About the Base64 Decoder
Found a Base64 string in a config file, an email header or a token and want to know what it says? Paste it here. The decoder accepts both standard and URL-safe Base64, tolerates missing “=” padding and line breaks, and strips a data: URL prefix automatically.
If the input is not valid Base64, or decodes to binary data such as an image rather than text, the tool tells you exactly that instead of showing garbled characters.
How to use the Base64 Decoder
- Paste the Base64 string.
- Read the decoded text, which updates as you type.
- Copy or download the result.
Features
- Batch files: run the tool on up to 200 files with the same settings and download every result as one ZIP
- Standard and URL-safe alphabets
- Missing padding and whitespace tolerated
- Strips data: URL prefixes
- Clear errors for invalid or binary data
- Line-by-line decoding
Supported formats
- Base64 text
- Base64URL
- Data URLs
Frequently asked questions
Can I decode a JWT with this?
Yes. A JWT has three parts separated by dots. Paste the first or second part on its own to read the header or payload. The signature part is binary.
Why do I get “decodes to binary data”?
The Base64 represents a file such as an image or PDF rather than text. Those bytes cannot be shown as readable characters.