How to use URL Codec
- Choose URL component for one parameter value; choose Full URL only for an already structured address.
- Paste the value, then select Encode or Decode.
- Run the operation and inspect separators before using the result in a request.
Worked examples
Use the inputs below to compare the selected mode with a known result. Loading an example replaces the current input.
Encode a query value
Input
tea & cake
Expected result
tea%20%26%20cake
Insert this after q= in a query. The encoded ampersand remains part of the value.
Preserve an address structure
Input
https://example.com/search?q=tea cake
Expected result
https://example.com/search?q=tea%20cake
The scheme, path, question mark and equals sign remain URL structure.
Decode a plus sign literally
Input
a+b%20c
Expected result
a+b c
Only %20 becomes a space here. Form-style plus-to-space conversion is a different operation.
What this tool does and does not do
The component mode uses encodeURIComponent / decodeURIComponent; full-address mode uses encodeURI / decodeURI. This is not an HTML escaper, a URL validity checker, or an application/x-www-form-urlencoded parser. A literal + is not automatically changed into a space.
Conversions run in the current browser. Input drafts are temporary; copy or download important results before leaving. See the privacy policy for the separate handling of visits and preferences.
Common questions
Why did %20 become %2520?
You encoded an already encoded percent sign. Confirm whether the receiving field expects original text or an existing encoded value.
Why does Full URL decoding leave %26 unchanged?
decodeURI preserves escapes for certain reserved URL characters. Use component decoding when you specifically want the value inside a parameter.
Does encoding make a link safe to visit?
No. Encoding does not check the domain, content or destination. Inspect the actual address separately.