Use this tool to percent-encode text so it can be placed safely in a URL, or to decode a messy link full of %20 and %C3%A9 back into readable text. It offers both JavaScript styles: component encoding for query values and path segments, and full-URL encoding that keeps the structure of a link intact.
When the input is a URL, the parser below splits it into protocol, host, port, path, query and fragment, and lists every query parameter with its decoded value. That makes it quick to debug tracking links, OAuth redirects and API calls, all without sending the URL to any server.
How to use the URL Encode / Decode tool
- Paste text or a URL into the input box.
- Choose Encode component, Encode full URL or Decode. The output updates as you type.
- Tick Spaces as + for HTML form style encoding (application/x-www-form-urlencoded).
- Read the URL parts and query parameter table if your input is a link.
- Copy the output, or swap it into the input to reverse the operation.
Why use ToolOrca URL Encode / Decode
- encodeURIComponent and encodeURI modes
- Decodes UTF-8 percent sequences
- Plus-as-space option for form data
- URL parser with query parameter table
- Clear message for broken % sequences
- Runs locally in your browser
encodeURIComponent vs encodeURI
Encode component (encodeURIComponent) escapes every character that has a meaning in URLs, including / ? : @ & = + $ #. Use it for a single value, such as a search term or a redirect address placed inside a query parameter.
Encode full URL (encodeURI) leaves those structural characters alone and only escapes spaces, non-ASCII letters and a few unsafe symbols. Use it when you already have a complete URL that just contains spaces or accented characters.
Getting this wrong is a classic bug: encoding a whole URL with encodeURIComponent turns https:// into https%3A%2F%2F, while encoding a parameter with encodeURI lets an & in the value split it into two parameters.
Why URLs need encoding
URLs may only contain a limited set of ASCII characters. Everything else is written as a percent sign followed by two hex digits for each UTF-8 byte, so a space becomes %20 and “é” becomes %C3%A9.
Frequently asked questions
Should a space be %20 or +?
In paths and most APIs, use %20. The + form is only used in HTML form submissions and query strings encoded as application/x-www-form-urlencoded. This tool can produce and decode both.
Why do I get “URI malformed” when decoding?
The text has a percent sign that is not followed by a valid UTF-8 sequence, such as a lone % or a cut-off %E2%8. Fix or remove that part and decode again.
Can I decode a URL that was encoded twice?
Yes. If you still see sequences like %2520 after decoding, press Use output as input and decode again.
Is my URL sent anywhere?
No. Encoding, decoding and parsing all happen in your browser, so private links, tokens in query strings and internal hostnames are not shared.