Base64 Converter
Encode or decode UTF-8 text, including non-Latin characters, to and from Base64 (standard or URL-safe). Nothing you enter is sent to a server.
Input
Result
Your result will appear here
Run the conversion to copy the result or convert it back.
User reviews
No reviews yet. If you’ve used this tool, be the first to leave one.
Base64 Converter: complete guide
Walk through the steps and examples, or jump straight to the topic you need.
At a glance
- Target
- Converts UTF-8 text, including Korean and emoji, to and from Base64.
- Format
- You can choose standard Base64 or URL-safe Base64.
- URL-safe
- Uses - and _ instead of + and /, and leaves out the = padding at the end of the encoded result.
- Input and saving
- Up to 100,000 characters of input or a UTF-8 file of 512KB. Supports copying the result and saving as TXT.
- Scope
- It is not a tool for restoring binary files such as images or PDFs, or for encrypting and decrypting.
How to use Base64 Converter
Check whether you have plain text or an encoded value
To convert plain text, choose encode, and to read a Base64 string, choose decode. Do not include a data: prefix or a JSON property name; enter only the text part to convert.
Choose standard or URL-safe
Check the format required by the service you exchange the value with. A value that uses - and _ may be URL-safe. Do not guess the format only because you copied it from a URL; it is better to check the original format as well.
Run the conversion and check the content
The result is shown in a separate area from the input. If decoding fails, check the direction, the format and whether any characters are missing. Even valid Base64 cannot be read by this tool if the bytes it holds are not UTF-8 text.
Copy, save as TXT, or convert back
You can copy the result or save it as TXT. Bring the result in as input and convert in the opposite direction to check the original. If you change the options or the original, make the result again.
What it’s good for
Convert UTF-8 text, including Korean
Enter the original text and encode it, and the UTF-8 bytes are turned into a Base64 string. Decoding turns UTF-8 text expressed in Base64 back into the original. You can bring the result in as the next input and convert in the opposite direction.
Standard Base64 and URL-safe Base64
The URL-safe option replaces + and / of standard Base64 with - and _, and leaves out the = padding at the end. If the value is for a URL or token, check the format the system requires. Base64 is not encryption that hides content, and an encoded value can be read again.
Worked examples
Converting one Korean character
The Korean syllable "ga" (U+AC00)6rCAStandard result with padding
HelloSGVsbG8=Standard, URL-safe and encryption
Swipe the table sideways to see the rest.
| Type | Role | What to watch for |
|---|---|---|
| Standard Base64 | A general format for passing bytes as characters | May use + and / and the = padding at the end. |
| URL-safe Base64 | Expressed in characters that are convenient in URLs | This tool uses - and _ and leaves out the = at the end. |
| Encryption | A separate operation that controls access to content using a key | Base64 can be reversed without a key, so it is not a substitute for encryption. |
When the result isn’t what you expected
I get an error when I press decode
Check the conversion direction and the URL-safe option, then see whether the value was cut off in the middle. Quotes or a prefix attached in a sentence may be included. Binary data such as images may not be decodable as text.
The encoded result became longer
Base64 is not compression. It expresses UTF-8 bytes as characters, so the result string can be longer than the original. It is not suited to making text shorter.
I re-encoded the decoded result and the notation differs
Compare the standard or URL-safe choice and the padding at the end. Also check whether spaces or line breaks were added when you copied the original. First tell apart whether the same content was just expressed with a different notation rule.
Key terms
- UTF-8
- A way of expressing characters such as Korean and emoji as bytes.
- Padding
- The = characters added at the end of Base64. They make the output length fit its unit.
- URL-safe
- A variant of Base64 in which some characters are replaced to be easier to handle in URLs.
Base64 Converter FAQ
Can it decode image Base64 or files?
Currently it supports UTF-8 text conversion. It does not restore binary data such as images to files or handle data:image/... addresses.
Does using Base64 make a password safe?
No. Base64 is an encoding that can be reversed without a key. It is not a substitute for hashing or encryption used to store passwords.
What should I check if Base64 decoding fails?
Check the conversion direction and the standard or URL-safe option, and see whether the input was cut off. An error also occurs when the decoded bytes are not valid UTF-8 text.
Can it read Base64 that contains line breaks?
When decoding, it removes whitespace from the Base64 input and then processes it. However, spaces and line breaks in the original text you encode are data, so they are reflected in the result.
If I put in a whole JWT token, will it be read?
It is not a tool for analyzing a whole JWT separated by dots. You can understand the structure and convert only the UTF-8 text part you need in URL-safe form, but it does not verify the signature or check the token's validity.