Encode or decode any URL in one paste

Component mode uses encodeURIComponent and escapes characters like ":/?#[]@" so the value is safe inside a single URL segment or query parameter. Full URL mode uses encodeURI and leaves those reserved characters alone so the entire URL stays a valid URL.

Switch to component mode, paste the parameter value and the encoder replaces spaces with %20, equals signs with %3D and so on. Drop the result into the URL after "?key=" or "&key=" and the link works on any browser, server or REST client.

Those characters are reserved by the URL syntax — they separate the scheme, path, query and fragment. Encoding them as %2B %2F %3A %3F %23 lets the value carry them literally without confusing the parser on the other side.

Yes. When the input contains a stray "%" that is not followed by two hex digits, the decoder shows an "Invalid input" message instead of producing garbled output. Fix the offending sequence and the result updates instantly.

No. The encoder uses the browser's built-in encodeURI / encodeURIComponent functions, so nothing crosses the network. That makes the tool safe for tokens, file paths and any other sensitive value you need to embed in a URL.

Yes. UTF-8 characters like ñ, 漢, ✓ and emoji are encoded into the corresponding %xx byte sequences. Modern browsers and servers decode them back to the original characters automatically, so the round-trip is loss-free.

Yes. Switch the mode toggle to Encode to percent-encode raw text, or to Decode to turn %XX sequences back into readable characters. The same Component and Full URL options apply in both directions, so you can round-trip a value and get exactly what you started with.

The at sign becomes %40 in percent encoding. In Component mode the tool escapes it automatically, which matters for email addresses in query strings — user@example.com becomes user%40example.com. Other common escapes: a space is %20, '#' is %23, '&' is %26 and '?' is %3F. Paste any text to see the full encoded result instantly.

Yes — they are two names for the same mechanism defined in RFC 3986: unsafe characters are replaced with a percent sign followed by two hex digits of their UTF-8 bytes. 'URL encoding' is the everyday name and 'percent encoding' the specification term. This tool applies it with encodeURIComponent or encodeURI depending on the mode you choose.