Decode a token, an e-mail header or a data URL, or make one. Non-Latin text is handled correctly.
It is a way of writing bytes as text that anyone can reverse. Never use it to hide passwords or personal data.
Many encode characters directly instead of their UTF-8 bytes, which breaks on non-Latin text. Here text is converted to UTF-8 first, so results match other languages and systems.
For URLs and JWTs, + and / become - and _, and trailing = is dropped. Decoding accepts both forms.
Drop any image file up to 5 MB to instantly generate a standard data:image/...;base64,... string you can paste into your stylesheet. The encoding runs locally in your browser, so image assets are never uploaded to an external server.
Enable the URL-safe toggle to replace + with -, / with _, and strip trailing = padding so the output can go directly into query parameters. The decoder accepts standard Base64, URL-safe variants, and data-URL prefixed strings interchangeably with full UTF-8 support.
Paste the Base64 string between the second and third dots of a JWT into the decode field to reveal the JSON claims. The decoder automatically handles both standard and URL-safe formats, displaying non-Latin characters correctly through UTF-8 byte parsing.
Screens and numbers from actually running this tool with sample values (2026-10-06, Chromium-based browser on a Mac). Results vary with your input and device.

After entering text and clicking encode, the Base64 output appears. In this example, 15 characters became 36 characters. A URL-safe option and a file-to-data-URL feature are also available.
Base64 is an encoding, not encryption. A copy button lets you grab the result directly.
No. Pasting a token here keeps it on your machine.
5 MB for data URLs; Base64 is about 33% larger than the original.
The data was probably binary (an image or archive), not text.
Yes, it processes text using UTF-8 byte encoding, ensuring that non-Latin characters and special symbols encode and decode accurately.
Yes, the URL-safe option replaces + and / with - and _ and strips trailing = padding characters.
Yes, you can load files up to 5 MB to convert them directly into browser-ready data:...;base64,... strings.
No, Base64 is purely an encoding scheme for data representation and does not provide cryptographic security or encryption.