URL encoding, use it like this
You can encode URL components such as search terms or decode characters expressed as percents.
Example usage
Spaces are replaced with %20. & in the search term is replaced with %26 to distinguish it from other parameters.
Please note
Apply encodeURIComponent to individual components rather than the entire address. When decoding, the + is retained.
Step-by-step instructions
- Enter one search term or URL parameter value.
- Select encoding or decoding.
- Check for double encoding when putting into a completed address.
The entire address and parameter values are different
This tool uses encodeURIComponent and decodeURIComponent. The purpose is to safely pass some values of the URL. If you encode the entire address, : and / are also converted, so it cannot be used directly as a regular link. Re-encoding an already encoded %20 results in %2520, which is different from the original intent.
| Original text | Encoding result |
|---|---|
| a b | a%20b |
| a&b | a%26b |
| 한글 | %ED%95%9C%EA%B8%80 |
Frequently Asked Questions
Decoded + does not change to space.
This tool follows URI component rules, so leave the + as is. This is different from the application/x-www-form-urlencoded rule for HTML forms.
I get an error saying it's an invalid URI.
The hexadecimal format following % may be incorrect or not a valid UTF-8 byte combination. Make sure the original is not cropped.
Can URL encoding prevent XSS?
URL encoding alone does not solve all security problems. Proper handling is required for each HTML output, URL whitelist, and script context.
Written and operated by: Moyoutil · Content review: 2026-09-30 · Error report