URL Encode / Decode
Percent-encoding, with the component distinction made explicit
Everything runs in your browser. Your data never leaves your device.
Related tools
How to use
URLs may only contain a limited set of characters. Everything else is percent-encoded as its UTF-8 bytes in hexadecimal. The subtlety is which characters count as reserved, and that depends on whether you are encoding a whole URL or one value inside it.
Choose encode or decode
Decoding reverses percent-encoding. If the input contains a stray % that is not part of a valid sequence, you get a clear error rather than a silent mangling.
Decide on component mode
Leave it on when encoding a single value that will sit inside a query string. Turn it off when encoding a complete URL that must keep its :// ? & = structure intact.
Check the result
Spaces become %20, and non-ASCII characters expand to multiple bytes — a single Korean or Japanese character becomes three percent-escapes, which is expected.
Examples
Encoding a search value
The query value "온라인 도구" becomes %EC%98%A8%EB%9D%BC%EC%9D%B8%20%EB%8F%84%EA%B5%AC. Each Korean character occupies three bytes in UTF-8, so each expands to three escapes.
Why component mode matters
Encoding the full URL https://example.com/search?q=a&b in component mode escapes the :// and ? as well, producing a string that is no longer a usable URL. Turn component mode off for whole URLs.
About this tool
Encode text for safe use in URLs or decode percent-encoded strings back to readable text. The tool exposes the distinction between encoding a whole URL and encoding a single value inside one — the difference between encodeURI and encodeURIComponent, and the source of most percent-encoding bugs.