Encoders & Decoders
Convert text to and from the encodings used on the web, and read the contents of tokens, without sending anything to a server.
Choosing the right tool
Encoding changes how data is written so it can travel safely through systems that only accept certain characters. Base64 turns any bytes into plain letters and digits, so they fit in an email, a data URL or a JSON field. URL encoding replaces characters that have a special meaning in a web address, such as spaces, ampersands and question marks, with percent codes.
Decoding reverses the change, and it is usually how you find out what a value really contains. A JSON Web Token, for example, is three Base64 parts, and decoding it shows the claims inside, such as who the token is for and when it expires. Encoding is not encryption: anyone can decode these formats, so never treat them as a way to hide a secret.
These tools handle international text correctly and run in your browser, so tokens, keys and query strings you paste are never uploaded.
Frequently asked questions
- Is Base64 a form of encryption?
- No. Base64 is a reversible way to write data as text, and anyone can decode it. Do not use it to protect secrets.
- Is it safe to paste a JWT into an online decoder?
- Only if the decoder never sends it anywhere. These tools decode in your browser and do not upload the token. Even so, avoid pasting live production tokens into any website you do not trust.
- When do I need URL encoding?
- Whenever a value goes into a web address, such as a search term or a redirect link, and may contain spaces or symbols like & and ?. Encoding stops them from being read as part of the address structure.