About this tool
This tool converts Base64 back into readable text as you paste it and tells you whether the input is valid. Developers use it to inspect API payloads, tokens, email sources, and configuration values. Base64 decoding reverses Base64 encoding: every 4 characters from the 64-character alphabet are turned back into 3 bytes, which are then read as UTF-8 text.
How it works
Paste a Base64 string into the input box, or use the buttons to paste from the clipboard, upload a text file or insert sample data. The decoded text appears immediately, along with a status that shows whether the input is valid. Line breaks and spaces are ignored, so Base64 copied from an email source or a wrapped PEM-style block decodes without cleanup.
Standard and URL-safe input both work without changes, and missing padding is added for you. Once the result looks right, copy it or download it as a .txt file. If the status reports an error, check for characters outside the Base64 alphabet or for data that was never text to begin with.
Example
The input SGVsbG8/ decodes to Hello?, and the URL-safe form SGVsbG8_ gives the same result. Missing padding is restored automatically, so Y2Fmw6k decodes to café even without its trailing padding character. A string such as SGVsbG8* is rejected because the asterisk is not part of any Base64 alphabet.
The built-in sample, SGVsbG8sIEJhc2U2NCEg0J/RgNC40LLQtdGCIPCfjI0=, decodes to Hello, Base64! Привет 🌍. It shows that a single Base64 string can carry Latin letters, Cyrillic text and an emoji, because each character was stored as its UTF-8 bytes before encoding.
Assumptions and limits
The decoder expects the result to be valid UTF-8 text. Base64 that encodes binary data, such as an image or a compressed file, is reported as invalid instead of being shown as garbled characters. Decoding runs in your browser, and links never carry your input. It does not decrypt or verify signed data such as JWT signatures.
Frequently asked questions
How do I know if a string is Base64?
Valid Base64 uses only letters, digits, plus and slash (or hyphen and underscore in the URL-safe variant), and its length is a multiple of 4 once padding is added. Passing that check does not prove the content is text, which is why this tool also checks the decoded bytes for valid UTF-8. Short ordinary words such as Test can also look like valid Base64, so context matters as much as the characters.
Why does my Base64 decode to garbled or invalid text?
The data probably encodes binary content, such as an image, a compressed file or encrypted bytes, rather than text. It can also happen when the text was encoded with a character set other than UTF-8, such as Windows-1252. In both cases the bytes are correct, but they cannot be shown as readable UTF-8 characters.
Can I decode a JWT with a Base64 decoder?
Yes. The header and payload of a JSON Web Token are base64url-encoded JSON, so you can paste each dot-separated part to read it. Decoding does not verify the signature, and a dedicated JWT decoder is more convenient because it splits the token and shows dates such as exp for you.
What are the equals signs at the end of Base64?
They are padding that brings the length to a multiple of 4 characters. One padding character means the last group held 2 bytes, and two mean it held 1 byte. Many decoders, including this one, accept input without them, which is common in URL-safe Base64.
How do I decode Base64 in code or on the command line?
On Linux and macOS, piping the string into base64 --decode prints the original bytes. In Python, base64.b64decode(value).decode("utf-8") returns text, and base64.urlsafe_b64decode handles the URL-safe alphabet. In browser JavaScript, atob returns raw bytes as a string, so pass them through TextDecoder if the original text contained non-ASCII characters.
Link with your values
Add these parameters to this page’s address to open it with the values filled in, for example to share a calculation or to link to it from an AI assistant. The result is calculated in the browser: the page HTML shows an example for the default values, and the tool sets the data-url-params attribute once the link’s values are applied.
| Parameter | Value | If omitted |
|---|---|---|
base64Base64 Input | not accepted in links: enter it on the page |
Links cannot carry this tool’s input, so there are no examples: enter it on the page.
Write decimals with a point. Encode a space as %20, + as %2B, # as %23 and & as %26.
Result elements: [data-result-block="base64-decoded"]