URL Encoder / Decoder
Percent-encode or decode URLs and query string values. Component mode escapes every reserved character, URI mode keeps :/?# usable.
URL encoder and decoder
Your encoded text will appear here.Frequently Asked Questions about the URL Encoder / Decoder
When should I use component encoding versus full URI encoding?
Use Component mode for query string values, form fields, and path segments. It escapes every reserved character, so :, /, ?, #, and = all become percent codes. Use Full URI mode when the input is an entire URL you only want to make transport-safe. It preserves :/?# so the URL still works.
Why does my decoded text show a malformed-sequence error?
A percent sign in a URL must be followed by two hex digits (0 to 9, A to F). Inputs like %ZZ, a lone %, or %A with nothing after it are not valid percent encoding. Fix the input or, if the % is meant as a literal character, encode it first as %25.
How is a space encoded?
Inside the path or query string, a space is encoded as %20. In application/x-www-form-urlencoded form bodies, a space is encoded as a plus sign instead. This tool follows the URL standard and emits %20 for spaces in both Component and URI modes.
How are non-ASCII characters handled?
The tool follows RFC 3986: the character is first encoded as UTF-8 bytes, then each byte becomes a percent triplet. So accented characters become two percent triplets and a four-byte emoji becomes four. Decoding reverses that and gives the original character back.
Is this tool safe to use for sensitive URLs or tokens?
Yes. All encoding and decoding runs locally in your browser. Nothing is sent to a server, stored remotely, or logged. You can safely paste URLs containing API keys, session tokens, or other secrets.