If you work with websites or APIs, you will see strings like SGVsbG8= and %20. These are encodings, not secrets.
What is Base64?
Base64 converts data into a set of 64 safe characters: A to Z, a to z, 0 to 9, plus and slash, with equals signs as padding. It lets binary data travel through systems built for text. The cost is size: Base64 output is about one third larger than the input.
Example: Hello becomes SGVsbG8=.
What is URL encoding?
Web addresses can contain only certain characters. URL encoding (percent encoding) replaces others with a percent sign and a code.
| Space | %20 |
|---|---|
| & | %26 |
| / | %2F |
| é | %C3%A9 |
Try both in our free Base64 and URL encoder decoder.
The most important warning
Base64 is not encryption. Anyone can decode it in seconds, so never use it to hide passwords or private data. For safe passwords, use our password generator and read how to create strong passwords.
When you will use them
- Embedding small images in web pages (data URLs)
- Sending data in API requests
- Putting search terms or names safely inside a link
- Reading encoded values while debugging
Common errors
- Decoding text that is not valid Base64
- Forgetting that accents and emoji need UTF-8 handling
- Double-encoding a link that was already encoded
Base64 and URL encoding: frequently asked questions
Is Base64 secure?
No. It only changes the format and offers no protection.
Why does Base64 end with equals signs?
They are padding that makes the length a multiple of four.
Is URL encoding the same as Base64?
No. They solve different problems and use different rules.
