Runs locally in your browser. Nothing you enter is uploaded to our servers.
Tips for Base64 decoding
Base64 is encoding, not encryption.
Padding (=) and URL-safe variants matter for some payloads.
Decoded binary may not be valid text — check the context.
Do not assume decoded JWT-like strings are verified.
Strip whitespace before decoding when sources wrap lines.
Decode Base64 back to text or bytes
Processing stays in your browser — your input is not uploaded to our servers.
Base64 is an encoding, not encryption. This decoder turns ASCII Base64 into the original bytes so you can read tokens, small files, or data URLs.
Padding (`=`) and URL-safe alphabets (`-` `_`) are the usual compatibility snags.
Decode Base64
Paste the Base64 string
Strip `data:...;base64,` prefixes if you only want the payload.
Decode
If the alphabet is URL-safe, keep the dashes and underscores — do not “fix” them to plus/slash by guesswork unless you know the variant.
Read the output
Binary payloads may look like garbage as text; copy the raw result instead of retyping.
Base64 decode FAQ
Is Base64 encryption?
No. Anyone can decode it. Do not treat encoded secrets as hidden.
Why do I get an error?
Wrong alphabet, missing padding, or extra line breaks. JWT payloads use URL-safe Base64 without padding.
Is the string uploaded?
No. Decoding stays in the browser.