Encoding Tools

Percent-encoding that understands your payload

URLs can only carry a narrow alphabet, so anything else — spaces, ampersands, non-ASCII text, entire JSON documents in a query parameter — must be percent-encoded. The plain URL Encode/Decode tool handles free text with correct UTF-8 semantics (one emoji becomes several %XX bytes, and decodes back to one emoji). The format-aware variants go further: JSON, XML, and YAML URL encoders validate the payload before encoding and after decoding, so a malformed document is caught at the tool instead of in production.

Decoding is forgiving where reality demands it: + is treated as a space (the form-encoding convention), uppercase and lowercase hex both decode, and malformed sequences produce a clear error rather than mojibake. As with everything here, encoding happens in your tab — tokens and payloads in your URLs never reach a server.

When you need this

The classics: building a callback or redirect URL that carries a return address, debugging why an API call with an & in a parameter truncates, passing a JSON filter object in a GET request, reading a SAML or OAuth parameter out of a captured URL, or crafting curl commands where the shell and the URL both want quoting. Paste the suspicious parameter into the decoder and the actual payload appears; encode the fixed version and paste it back.