Text & Data
Base64 Encoder & Decoder
Encode UTF-8 text to Base64 or decode standard and URL-safe Base64 back to text.
How to use this Base64 converter
Choose encode or decode, then enter a value to see the result. Encoding uses UTF-8, so Chinese, emoji, and other Unicode characters are handled safely; all calculations happen in your browser.
Standard and URL-safe Base64
Standard Base64 uses plus and slash and is suitable for ordinary text and data transfer. URL-safe Base64 replaces them with hyphen and underscore, making it safer for URLs, cookies, and file names. Padding is the trailing equals sign used to complete a group; both forms are accepted when decoding.
Frequently asked questions
Are Chinese characters and emoji handled correctly?
Yes. The tool converts text to strict UTF-8 bytes before encoding and validates UTF-8 while decoding, so damaged data is not silently treated as normal text.
When is padding needed?
Canonical standard Base64 usually keeps trailing equals signs so strict implementations can verify the length. URL-safe values often omit them to stay shorter. Choose either form while encoding; decoding accepts both.
What is the difference between URL-safe and standard Base64?
URL-safe Base64 uses <code>-</code> instead of <code>+</code> and <code>_</code> instead of <code>/</code>, avoiding characters that can be escaped or interpreted as delimiters in URLs. The two alphabets should not be mixed.