Using the URL encoder and decoder
Encode text so it is safe to drop into a URL, or decode a %-escaped URL back to readable text. Everything runs in your browser – nothing you paste is uploaded or stored, so it is safe for tokens, keys and private data.
What is URL encoding?
URL (percent) encoding replaces characters that are unsafe or reserved in a URL with a % followed by their byte value in hex – a space becomes %20, for example. It lets arbitrary text travel inside a query string, path segment or fragment without breaking the URL structure.
Component encoding vs whole-URL encoding?
Full component encoding (like JavaScript’s encodeURIComponent) escapes every reserved character, so it is right for a single value you are slotting into a URL. Whole-URL encoding (like encodeURI) leaves : / ? & # = intact so an already-formed URL stays usable. Pick the mode in the settings.
Why does my space sometimes become +?
The application/x-www-form-urlencoded format used by HTML form submissions encodes spaces as + rather than %20. Enable “Use + for spaces” to match that behaviour in both directions.
What else can this tool do?
The same converter also handles base64, html entities, jwt, hex, binary, morse code and rot13 / caesar cipher. Pick a format from the menu without leaving the page.
Is any of this encryption?
No. Encoding changes how data is represented so it can travel safely through a channel; it does not protect it. Anyone can reverse Base64, percent-encoding, hex or ROT13. For a one-way fingerprint use the hash generator; to check JSON you have decoded, use the JSON formatter.