Base64 Decode
Decode Base64 and URL-safe Base64 strings back into readable text instantly in your browser. Unpack an encoded value from an API response or config file, read a JWT payload by hand, or verify Basic Auth credentials without sending data to a server.
Usage examples
Checking a Base64 value inside an API response
When a server response or a JWT token has a Base64-encoded value buried in it, paste it in to see the original text right away.
Unpacking an encoded value from a config file
If an environment variable or config file stores a Base64 value, paste it here to see the original content instantly.
Decoding a URL-safe encoded value directly
URL-safe Base64 using - and _ can be pasted as-is — no need to convert it back to standard Base64 first.
Reading the payload of a JWT by hand
Copy the middle segment of a JWT (between the two dots) and decode it to inspect the claims inside, without installing a JWT debugging tool.
Verifying a Basic Auth header's credentials
An Authorization: Basic header carries a Base64-encoded username:password pair. Decode it to confirm which credentials a request is actually sending.
Quick reference
| Base64 | Decoded text |
|---|---|
| aGVsbG8= | hello |
| SGVsbG8gV29ybGQ= | Hello World |
| SGVsbG8sIFdvcmxkIQ== | Hello, World! |
| dGVzdA== | test |
| cGFzc3dvcmQ= | password |
| MTIzNDU2 | 123456 |
| YWRtaW46YWRtaW4= | admin:admin |
| YWRtaW46cGFzc3dvcmQ= | admin:password |
| dXNlcjpwYXNzd29yZA== | user:password |
| eyJ | {" |
| eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9 | {"alg":"HS256","typ":"JWT"} |
| JVBERi0xLjQ= | %PDF-1.4 |
| PD94bWwgdmVyc2lvbj0iMS4wIj8+ | <?xml version="1.0"?> |
| PHN2Zw== | <svg |
| PGh0bWw+ | <html> |
| Pz8_ | ??? |
| 7ZWc6riA | 한글 |
Frequently asked questions
Is the text I paste sent to a server?
No. Decoding happens entirely in your browser, and what you paste is never sent to a server.
Why am I seeing an error?
You'll see an error if the input doesn't match the Base64 format (disallowed characters, wrong length), or if the decoded bytes aren't valid UTF-8 text — for example, if they're binary data like an image.
Can this decode URL-safe encoded values too?
Yes. URL-safe Base64 using - and _ is automatically recognized and converted back to standard Base64 before decoding.
Can it decode non-text data like images or files?
This tool only shows the result as text. If the decoded bytes aren't valid UTF-8 text, it shows an error — binary data such as images isn't supported.
Why does my Base64 string have = or == at the end, and do I need to keep it?
The = characters are padding, added so the encoded length is a multiple of 4 characters, per RFC 4648. Most decoders, including this one, can tolerate missing padding, but it's safest to paste the string exactly as you received it, padding included.
Is Base64 encoding the same thing as encryption?
No. Base64 is just a reversible text representation of binary data — anyone can decode it instantly with no key or password required, as this tool demonstrates. It provides no confidentiality at all, so it should never be used as a substitute for actual encryption.
Why did I get an error even though the text looks like normal Base64?
Base64 alphabets differ slightly by context. Standard Base64 uses + and /, while URL-safe Base64 uses - and _ instead. If a string mixes characters from both alphabets, or has incorrect padding for its actual length, it will fail to decode.