URL Decode
Decode URL encoded text
Frequently Asked Questions
What is URL decoding?
URL decoding converts percent-encoded characters back to their original form. %20 becomes a space, %26 becomes &, %3D becomes =. This reverses the encoding applied to make characters safe for use in URLs.
When do I need to decode a URL?
When reading URLs from logs, APIs, or query strings that contain encoded characters. For example, a search query "hello world" appears as "hello%20world" in the URL. Decoding reveals the original text.
What characters are percent-encoded in URLs?
Spaces (%20 or +), special characters (&=%26, =%3D, ?=%3F, #=%23), non-ASCII characters (é=%C3%A9), and reserved characters that have special URL meaning. The decoder handles all standard percent-encoded sequences.
What is the difference between %20 and + for spaces?
%20 is the standard percent-encoding for spaces in URLs. + represents spaces only in query string parameters (application/x-www-form-urlencoded). The decoder handles both conventions correctly based on context.
Can I decode an entire URL with query parameters?
Yes. Paste the full URL and the decoder shows the readable version. It decodes the path, query parameter names, and values. For example, /search?q=hello%20world&lang=en%2Dfr becomes /search?q=hello world&lang=en-fr.