Flip UTF-8 text to Base64 or back in this tab, including a URL-safe alphabet. Base64 is encoding, not encryption — anyone can decode it. Binary files and data-URI images belong on the sibling tools.
You have a token, a PEM fragment, or a config value that is Base64 and you want the UTF-8 back — or the other way. That is this page. People say “Base64 encrypt”; they mean encode.
File Base64 owns arbitrary files. Image to Base64 owns data:image/... URIs. JWT decoder owns three-segment tokens (still not encryption).
Encode vs decode
- Paste text. Pick standard or URL-safe.
- Encode or decode in this tab.
- If decode looks like garbage, you had the wrong alphabet, or the source was binary — use the file tool.
UTF-8 is the text assumption. Legacy encodings will mojibake.
Honest limits
- Not a secret keeper. Encoded credentials are still credentials.
- Huge pastes are limited by the tab, not a cloud queue.
- We do not implement raw MIME headers for you.
For hashing the decoded string, use hash generator after you have the plaintext.