Base64 Decode
Paste Base64 and read what it contains. The decoding happens on your device.
How it works
Base64 is a way of writing any data using only 64 safe characters: A to Z, a to z, 0 to 9, plus and slash. It was created so that files could travel through email systems that only handled plain text.
To decode it, each character is turned back into a 6 bit number. Four characters make 24 bits, which is three bytes of the original data. An equals sign at the end is padding. It shows that the final group held only one or two bytes.
You can often spot Base64 by its look: a long run of mixed case letters and digits with no spaces, a length that divides by four, and often one or two equals signs at the end.
Base64 is not encryption. Anyone can decode it, as this page shows. If you find a password or an API key stored only in Base64, treat it as stored in plain text.
This decoder also accepts the URL safe variant, which uses a hyphen and an underscore instead of plus and slash, and it adds missing padding for you.
Worked example
SGk= decodes to Hi. The single equals sign shows that the last group carried two bytes.
The Base64 alphabet
| Values | Characters |
|---|---|
| 0 to 25 | A to Z |
| 26 to 51 | a to z |
| 52 to 61 | 0 to 9 |
| 62 | + (or - in URL safe Base64) |
| 63 | / (or _ in URL safe Base64) |
| padding | = |
Common questions
Is it safe to paste secrets here?
The decoding runs entirely in your browser and the text is not sent to a server. Even so, it is good practice to avoid pasting live credentials into any website.
Why is my decoded text unreadable?
The data is probably not text. Images, files and encrypted data are often carried in Base64, and they decode to raw bytes.
How do I read a JWT token?
A JWT has three Base64 parts separated by dots. Paste the first or second part on its own to read the header or the payload.