URL Decoder (Percent Decoding)
Example
Input:
name%3DAli%20Raza%26city%3DFaisalabad
Output:
name=Ali Raza&city=Faisalabad
About this converter
Percent-decoding reverses RFC 3986 encoding: each %XX triplet becomes one byte, consecutive bytes are interpreted as UTF-8, and — in form/query contexts — + becomes a space. Decoding is where broken links confess: a %2520 in the wild means the value was encoded twice, and a bare % not followed by two hex digits means the string was never properly encoded at all (this decoder reports that rather than guessing). One caution: decoding a full URL shows you its readable form, but if you then edit and re-share it, encode the changed parts again — browsers fix some things automatically, servers do not.
Frequently Asked Questions
Why do I see %2520 in some URLs?
The value was encoded twice: %20 (space) was itself encoded, turning % into %25. Decode twice to recover the original — or fix the code that encodes an already-encoded value.
Is + always a space?
Only in query strings and form bodies (the x-www-form-urlencoded convention). In a URL path, + is a literal plus sign.
The decoder reported malformed percent-encoding — what now?
Look for a % that is not followed by two hex digits, or a truncated sequence at the end of the string; the source data was cut off or never encoded.