URL Encoder & Decoder
Encode URL components for HTTP requests, or decode percent-encoded URLs back to readable text.
What is URL encoding?
URL encoding, also called percent encoding, replaces unsafe characters with % escape sequences. It keeps query parameters, path segments, redirect URLs, search terms, and form values safe inside HTTP requests.
Use component mode for one value such as [email protected]&redirect=/docs?tab=api. Use full URL mode when you want to preserve URL syntax such as https://, slashes, question marks, and ampersands.
Practical URL encoding examples
Query value: hello world & more becomes hello%20world%20%26%20more with component encoding.
Redirect parameter: encode a nested URL before placing it inside ?redirect= so its own query string does not break the outer URL.
Debugging: decode strings such as name=DevTools%20Box&tab=json to quickly read copied request URLs and logs.
FAQ
Should I use encodeURI or encodeURIComponent?
Use encodeURIComponent for a single query value or path segment. Use encodeURI for an already assembled full URL when you want to preserve separators.
Why are spaces sometimes plus signs?
Percent encoding represents spaces as %20. Form-encoded query strings may use plus signs for spaces, depending on the parser.
What is double encoding?
Double encoding happens when text that already contains percent escapes is encoded again, turning % into %25 and making URLs harder to read.
Can I decode an entire query string?
Yes. Paste the query string or URL into the encoded side, decode it, then inspect separators such as ampersands and equals signs.