Encoding & Decoding
Search or browse every encoding & decoding tool in this category.
Working with Encoding & Decoding
Encoding problems are easy to misdiagnose because the output can look random even when the underlying data is intact. Base64, URL encoding, HTML entities, Unicode escapes, hexadecimal text, and character sets solve different problems, and one format is often nested inside another. These tools are meant for quick inspection and conversion when you need to see what a string actually contains.
It helps to identify the layer you are dealing with before decoding repeatedly. A URL parameter may contain percent-encoded Base64, while an escaped JSON string may contain Unicode sequences that should not be treated as bytes. If a decoded result still looks wrong, check the expected character set and whether padding, line breaks, or transport escaping changed the original value.
Practical tips
- Decode one layer at a time and inspect the result before continuing.
- Do not assume Base64 means encryption; it is only an encoding and provides no secrecy.
- For URL values, distinguish between encoding a full URL and encoding an individual query parameter.
- If non-ASCII text becomes garbled, check UTF-8 versus legacy encodings before changing the content.
- When copying encoded values from logs or shells, watch for stripped plus signs, backslashes, and trailing padding.