When to use the Base64 Decoder
Inspecting API data
Read Base64 values found in JSON responses, logs or webhooks.
Recovering files
Turn a Base64 string from an email source or database back into a downloadable image, PDF or ZIP.
Reading JWT parts
Decode the header and payload sections of a JSON Web Token to inspect their claims.
Debugging data: URIs
Check what an embedded image inside a CSS or HTML file actually contains.
Features and benefits
- Accepts standard and URL-safe Base64, with or without padding
- Strips data: URI prefixes and whitespace automatically
- Recognises PNG, JPG, GIF, WebP, PDF and ZIP data
- Clear messages for invalid characters or truncated input
Example
eyJ1c2VyIjoiYW5uYSIsInJvbGUiOiJlZGl0b3IifQ==
{"user":"anna","role":"editor"}How the Base64 Decoder works
ConvertNest removes whitespace and any data: prefix, converts URL-safe characters back to the standard alphabet and adds missing padding. It then turns every four characters back into three bytes. If those bytes are valid UTF-8 text, the text is shown; if they start with a known file signature – such as PNG, JPG, PDF or ZIP – the type is detected and a download button appears.
A real-life example
A support engineer receives a webhook log with a field called “document” containing 40,000 characters of Base64. Pasting it here shows “Detected: PDF document” and offers a download. The PDF is the customer’s invoice, which confirms the webhook sent the right file – the problem was on the receiving server, which was saving the text instead of decoding it.
Good to know
Base64 shows up in email source code, JSON web tokens, API payloads and HTML data URIs. Decoding it is often the quickest way to see what a system is actually sending.
If the decoded bytes are not valid UTF-8 text, the data is binary – usually a file. ConvertNest checks the first bytes (the file signature) to guess its type and offers it as a download instead of showing unreadable characters.
A JSON web token (JWT) is three Base64url parts joined by dots. Paste one part at a time to read the header or payload. Remember that decoding a token does not verify its signature.
Tips for the best results
- If decoding fails, check that the string was not cut off when copying.
- For JWTs, decode only the first two parts separated by dots; the third part is a signature.
- Use the download button for binary data instead of copying unreadable text.
- Never paste production secrets into tools you do not trust – ConvertNest decodes locally.
Common mistakes to avoid
Decoding the whole JWT at once
The dots are not Base64 characters. Decode each part separately.
Expecting readable text from an image
Binary files are not text. Download them instead.
Copying with line numbers from a log
Extra characters make the data invalid. Copy only the Base64 value.
Base64 Decoder – frequently asked questions
Why do I get “Invalid character”?
Base64 only contains A–Z, a–z, 0–9, + and / (or - and _ in the URL-safe form) plus = padding. Remove any other characters, such as quotes copied by accident.
Can I decode a Base64 image?
Yes. Paste the string or full data URI. If it is an image, you will see a preview and a download button.
Can this decode a JWT?
Yes, part by part. Paste the middle section (between the two dots) to read the payload. This does not check whether the token is genuine.
Is my data sent anywhere?
No. Decoding happens in your browser.
Can Base64 be decoded without a key?
Yes. Base64 is an encoding, not encryption, so no key is needed.
Why does the result contain strange symbols?
The data is probably binary, such as an image or compressed file. Use the download option.