Encode text in several languages
UTF-8 makes Arabic, Urdu and emoji round-trip correctly.
Input
Hello, مرحبا, السلام علیکم 👋
Output
SGVsbG8sINmF2LHYrdio2KcsINin2YTYs9mE2KfZhSDYudmE24zaqdmFIPCfkYs=
Encode text to Base64 or decode Base64 back to readable text. Text is converted to UTF-8 first, so any language and emoji work correctly, unlike tools that only handle plain English letters. Choose the URL-safe alphabet for tokens and URLs, or 76-character lines for email and PEM-style data.
Runs in your browser · Your data never leaves your device
Tip: decoding accepts both standard and URL-safe Base64, with or without padding.
These outputs were produced by the same code that runs in the tool above.
UTF-8 makes Arabic, Urdu and emoji round-trip correctly.
Input
Hello, مرحبا, السلام علیکم 👋
Output
SGVsbG8sINmF2LHYrdio2KcsINin2YTYs9mE2KfZhSDYudmE24zaqdmFIPCfkYs=
A token-style value with - and _ and no padding.
Input
eyJ1c2VyIjoiYW1pbmEiLCJyb2xlIjoiZWRpdG9yIn0
Output
{"user":"amina","role":"editor"}
No. Base64 only changes how data is written; anyone can decode it. Do not use it to protect passwords or secrets.
It replaces + and / with - and _ so the value can be used in URLs and file names without escaping. JWTs use URL-safe Base64 without padding.
Base64 uses 4 characters for every 3 bytes, so it is about a third longer. Non-English characters take 2 to 4 bytes each in UTF-8.
No. Encoding and decoding run on your device.
Read the privacy policy for how the site handles data.