Convert between URLs and percent-encoding both ways, with URI component / full URL modes, and break query parameters into a table.
Encoding mode
Input (plain text or %XX encoded string)
Result
—
Enter content, then click Encode or Decode.
Query parameter parsing (split ?a=1&b=2 into a table)
Supports full URLs or plain query strings; parameters are decoded automatically (readable output).
AD · LEADERBOARD 728×90 (PLACEHOLDER — REPLACED WHEN ADSENSE GOES LIVE)
FAQ
What is URL encoding (percent-encoding) for?
Only a limited set of ASCII characters is safe in URLs. Characters such as spaces, & # ? must be converted to a % sign followed by two hex digits — this is URL encoding (urlencode). Browsers and servers decode it back automatically.
What is the difference between URI component and full URL modes?
URI component mode (encodeURIComponent) also encodes separators like / : ? & = #, which is right for encoding a single parameter value. Full URL mode (encodeURI) keeps those separators, which is right for encoding an entire URL.
What does the + sign mean in a URL?
In query strings, + is often treated as a space, while standard encoding uses %20 for spaces. This tool decodes by the standard %XX rules and does not auto-convert + to spaces, to avoid corrupting real content.
Is my URL uploaded when parsing parameters?
No. Encoding, decoding and parameter parsing all run locally in your browser. The URL is never sent to any server (and the tool never visits that URL).