Sharing a link with & or spaces inside a parameter breaks it; receiving %20%26%3F gibberish tells you nothing. Percent-encoding is the bridge, and this tool converts both directions cleanly.
Updated August 12, 2026, after a fresh review, with updated visuals and links.
Paste a value, encode it for safe travel inside a URL, or decode a messy parameter back into human language.
When encoding saves the link
Query values containing &, =, spaces or non-Latin characters must be encoded or the URL splits wrong: 'café & tea' becomes 'caf%C3%A9%20%26%20tea'.
This tool uses component-level encoding (encodeURIComponent): aggressive enough for query values, which is almost always what you need.
Decoding reveals tracking parameters, redirect targets and search terms hidden inside shared links: a quiet superpower for marketers and developers alike.
Worth remembering
- Whole URLs are not component-encoded: leave the https:// and slashes structural, and encode only the piece that goes after the ? or &.
- Double-encoded text (%2520) means someone encoded twice: decode twice here to recover the original.
Frequently asked
What does %20 mean in a URL?
It is the percent-encoding of the space character: 20 is its hexadecimal byte value. Every unsafe character becomes % plus its hex code.
Encoder vs encodeURIComponent difference?
Component encoding (what this tool uses) escapes everything unsafe including / and &, which is what query values require; naive whole-URL encoding would leave = and & intact and corrupt parameters.
