URL Decoder
Decode percent-encoded URL strings back to readable text.
DecodeURIClient-sideFree to use
0 / 500,000
Try It Out
How to use
- Paste the encoded URL. With %20, %2F, etc.
- Copy the decoded text. Readable output.
Common use cases
- Debugging redirect URLs
- Reading webhook payloads
- Inspecting browser URLs
Frequently asked questions
- What does this URL decoder accept?
- Any string that contains percent-encoded sequences (%XX) plus optional unreserved characters. Full URLs, isolated query string values, single path segments, and Base64-percent-encoded payloads all work.
- Why does my decoded text contain garbage characters?
- That usually means the original encoding used a different character set (e.g. legacy Windows-1252) instead of UTF-8. This decoder follows the WHATWG URL spec and decodes percent-encoded bytes as UTF-8.
- Can I decode a + as a space?
- In strict URL decoding, + stays as +. The convention of decoding + to space comes from the older application/x-www-form-urlencoded MIME type for HTML form bodies. If you are decoding a form body, replace + with space before pasting.
- What is the difference between this and the URL Parser?
- The decoder turns percent-encoded characters back into readable text. The URL Parser also splits a URL into protocol, host, path, query parameters, and fragment for inspection.
- Does decoding happen in the browser?
- Yes. decodeURIComponent runs locally with no network round-trip.
Related tools
How to use
- Paste the encoded URL. With %20, %2F, etc.
- Copy the decoded text. Readable output.
Common use cases
- Debugging redirect URLs
- Reading webhook payloads
- Inspecting browser URLs
Frequently asked questions
- What does this URL decoder accept?
- Any string that contains percent-encoded sequences (%XX) plus optional unreserved characters. Full URLs, isolated query string values, single path segments, and Base64-percent-encoded payloads all work.
- Why does my decoded text contain garbage characters?
- That usually means the original encoding used a different character set (e.g. legacy Windows-1252) instead of UTF-8. This decoder follows the WHATWG URL spec and decodes percent-encoded bytes as UTF-8.
- Can I decode a + as a space?
- In strict URL decoding, + stays as +. The convention of decoding + to space comes from the older application/x-www-form-urlencoded MIME type for HTML form bodies. If you are decoding a form body, replace + with space before pasting.
- What is the difference between this and the URL Parser?
- The decoder turns percent-encoded characters back into readable text. The URL Parser also splits a URL into protocol, host, path, query parameters, and fragment for inspection.
- Does decoding happen in the browser?
- Yes. decodeURIComponent runs locally with no network round-trip.