About the Base64 Decoder
Base64 strings appear in API responses, email source code, configuration files and tokens. This decoder converts them back into readable text using UTF-8, so accented letters and emoji come back correctly.
It accepts both standard and URL-safe Base64, ignores spaces and line breaks, and adds missing padding automatically. If the input is not valid Base64, or if it decodes to binary data such as an image rather than text, you will see a clear message instead of garbled characters.
How to use it
- Paste the Base64 string.
- Click Decode Base64.
- Read or copy the decoded text.
Example
SGVsbG8sIHdvcmxkISDwn5GL
Hello, world! 👋
When to use it
- Reading the payload section of a JSON web token.
- Inspecting Base64 values in API responses and logs.
- Decoding email content encoded as Base64.
- Checking configuration secrets and environment values.
Frequently asked questions
Can it decode JWTs?
Yes. Paste the middle part of the token (between the two dots) to read its payload. The signature is not verified.
Why do I get a “binary data” message?
The string decoded correctly, but the result is not text. It is probably an image or another file.
Do I need to add = padding?
No. Missing padding is added automatically.
Is the text I enter kept private?
Yes. The Base64 Decoder runs entirely in your web browser, so your text is never uploaded to or stored on our servers. Like most free websites, TextForge shows ads from Google, which may use cookies. See our Privacy Policy for details.