How it works
Each group of 4 Base64 characters is converted back into 3 bytes, and the bytes are read as UTF-8 text. Missing = padding is added automatically, so URL-safe values without padding decode too.
If the bytes are not valid UTF-8, the input almost certainly encoded binary data such as an image, a PDF or compressed data rather than text. The tool tells you so instead of showing meaningless characters without warning.
Rules this tool follows
- Accepted characters: A–Z, a–z, 0–9, + and / (or - and _), with up to two = at the end.
- Whitespace and line breaks anywhere in the input are ignored, so wrapped email-style Base64 works.
- Input whose length cannot be valid Base64 (for example a value that was cut off) is reported as an error.
Example
Input
SGVsbG8sIFdvcmxkIQ==
Output
Hello, World!
Common uses
- Reading Base64 values found in configuration files, logs, emails and API responses.
- Inspecting the header and payload parts of a JSON Web Token (each part is base64url-encoded JSON).
- Checking that an encoded value contains what you expect.
Limitations and notes
- Decoding a JSON Web Token shows its contents but does not verify its signature.
- Binary data is detected but not displayed or saved as a file.