URL Encoder / Decoder
Percent-encode and decode URLs and query string parameters.
Frequently Asked Questions
Should I use `encodeURIComponent` or `encodeURI` mode here?
Use `encodeURIComponent` for a single query value or path segment, because it escapes separators like `&`, `=`, and `?`. Use `encodeURI` only when you already have a full URL and want to keep the structural characters intact.
Why did `:` and `/` stay readable in full URL mode?
That is expected from `encodeURI`. It preserves characters that are meaningful in a complete URL, which is why the output is less aggressively escaped than component mode.
Why does decoding not turn `+` into a space?
The tool uses `decodeURIComponent()`, and that function does not treat `+` as a space. If you pasted form-style query data, replace `+` with a space before decoding if that is the behavior you want.
Can it decode malformed percent-encoding?
No. If the input has bad escape sequences, the browser throws and the tool shows the error instead of guessing what you meant.
Does this run live while I type?
No. Encoding and decoding both happen only when you click the corresponding button.