Base64 Decode
Paste a Base64 string and read the text inside. Standard and URL-safe alphabets both work, missing padding is fine, and line breaks or a data: prefix are stripped for you.
Use the tool
Why this tool exists
You meet Base64 when you open a Basic auth header, a Kubernetes secret, a webhook payload or a data URI and need to know what is actually inside. Decoding by hand is not realistic, and command-line tools differ on padding and on URL-safe input.
This decoder cleans the input first. It removes whitespace and any data: prefix, converts the URL-safe alphabet, and tolerates missing padding. It then reads the bytes as UTF-8 and tells you plainly if they are not valid text. Decoding runs in the page, so tokens and secrets you inspect are not sent anywhere.
How to use it
- Paste the Base64 string into the box. Line breaks and spaces are ignored.
- Leave everything else as is. Standard and URL-safe input are both detected.
- Read the decoded text in the output.
- Copy the result, or fix the input if an error message appears.
Frequently asked questions
Why does it say the bytes are not valid UTF-8 text?
The Base64 is valid, but the data inside is not text. It may be an image, a compressed file or an encrypted blob. For compressed data try the Gzip Decompress tool, and for images use the Base64 Image Viewer.
What does "Invalid Base64 input" mean?
The string contains characters outside the Base64 alphabet, or its length is impossible, such as one leftover character. Check for a truncated copy, a stray quote or a prefix that is not part of the data.
Does it handle URL-safe Base64 and missing padding?
Yes. It converts - and _ back to + and /, and adds the = padding itself, so JWT-style segments decode without editing.
Is it safe to paste a real token?
Decoding happens only in your browser and nothing is uploaded. Even so, avoid pasting live production credentials into any page you do not fully trust, and rotate a secret that has been exposed.