Decode encoded spaces
Input
hello%20world
Output
hello world
Useful when you need to read plain text that was encoded for a URL.
Developer Tools
Review practical URL Decoder examples so you can understand expected input, output, and common patterns faster.
Use this free URL Decoder to convert percent-encoded URL text back into readable form. It is useful for inspecting query parameters, debugging redirects, reading encoded API request values, checking tracking links, and understanding what an encoded URL or parameter actually contains. Paste encoded text or a full encoded URL to decode it instantly in the browser.
Example pages are especially useful for developer tools because they show what good input looks like, what kind of output to expect, and how the tool behaves in common scenarios.
Input
hello%20world
Output
hello world
Useful when you need to read plain text that was encoded for a URL.
Input
name%3DJohn%20%26%20role%3Dadmin
Output
name=John & role=admin
Helpful when a parameter value contains equals signs, ampersands, and spaces.
Input
https%3A%2F%2Fexample.com%3Fa%3D1%26b%3D2
Output
https://example.com?a=1&b=2
Useful when one URL is embedded inside another as a parameter value.
Input
https%3A%2F%2Fexample.com%2Flogin%3Fnext%3D%2Fdashboard
Output
https://example.com/login?next=/dashboard
Helpful when debugging redirect flows or next-return URLs.
Input
email%3Duser%40example.com%3Fx%3D1%26y%3D2
Output
email=user@example.com?x=1&y=2
Useful for inspecting what special characters looked like before encoding.
Input
%D0%9F%D1%80%D0%B8%D0%B2%D0%B5%D1%82%20%D0%BC%D0%B8%D1%80
Output
Привет мир
Helpful when checking encoded non-English or Unicode text.
Input
%7B%22name%22%3A%22John%22%2C%22role%22%3A%22admin%22%7D
Output
{"name":"John","role":"admin"} Useful when JSON is transported through query parameters or redirect values.
Input
line%20one%0Aline%20two
Output
line one line two
Helpful for understanding how multiline text was represented in encoded form.
Fix: Check whether the text has already been decoded before running the tool again.
Fix: Confirm that the source actually uses percent-encoding and is not Base64 or another format.
Fix: Use Base64 or JWT tools when the input belongs to those formats instead of percent-encoded URL text.
Fix: Copy the full encoded value so the decoded result makes sense in context.
Fix: Decide whether you are decoding a whole embedded URL or just one encoded parameter string.
After reviewing these examples, run the live tool with your own input. If your task involves a follow-up step, the related page can help you move to the next tool in the workflow.
Open the main URL Decoder page and test your own real input.