Original text
0 characters
Not saved
Base64 Encoder & Decoder
Encode and decode Unicode text without corrupting non-ASCII characters.
How to use
These are example steps; replace the values for your task.
- Choose Encode, set line width to 0 and enter Hello.
- Toggle URL-safe form and compare the trailing =.
- For decoding, paste the encoded result into the source field and check that it returns Hello.
Converted text
0 characters
About this tool
Create or inspect Base64 text used in email and APIs. Base64 is encoding, not encryption.
Continue this task
- Morse Code Translator — For a human signaling alphabet rather than a data encoding, inspect alphanumeric Morse notation.
Non-ASCII text is encoded as UTF-8
Encoding “café” as UTF-8 produces “Y2Fmw6k=”, and decoding that value returns “café”. The letter-and-digit output is only reversible when both sides agree on the underlying character encoding.
- Base64 is not encryption. It does not make confidential text safe to store or share.
- The URL-safe form substitutes - and _ for + and /. Check which variant the receiving system expects.
Try a use case and check the result
Encode text as Base64 and check decoding back to the original.
Try this example replaces the input and settings. Restore previous input returns to the state before the latest example. Normal draft-saving rules apply.
After trying multiple examples, repeat Restore previous input to return to your original input. History is kept only in this page; restore any input you need before closing it.
Check standard Base64
Input and settings
Hello
URL-safe: Off; Wrap width: 0; Operation: Encode
Expected result
SGVsbG8=
Decode an encoded value
Input and settings
SGVsbG8=
URL-safe: Off; Wrap width: 0; Operation: Decode
Expected result
Hello
How to read the result
A trailing = is padding. Decode operates on the source field, so paste the encoded value into that field. URL-safe output omits trailing padding (=). For example, Hello becomes SGVsbG8= in ordinary output and SGVsbG8 in URL-safe output.
Scope and pitfalls
Base64 is not encryption and does not conceal sensitive content.
Continue with the next task
Frequently asked questions
Does it support Unicode text?
Yes. Text is encoded and decoded safely as UTF-8.
What is URL-safe Base64?
It replaces + and / with - and _, and omits trailing = characters for easier use in URLs and filenames.
Is my text sent to a server?
No. Conversion and storage take place only in your browser.
Related tools
Share this tool
Share only the tool name and public URL. Your input and results are not included.
Inputs and storage
Keep a separate copy before clearing or resetting. This browser autosaves entered text and tool settings. Data is not restored when read 30 days or more after its last save. Clearing site data or storage restrictions may remove it sooner.
Favorites and language preferences are stored separately and may be lost when site data is cleared. Tool resets and site-data deletion do not delete files already downloaded to your device.