Tech
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 anything that goes inside a URL: query string values, form fields, and path segments. It encodes every reserved character, including ":/?#&=", so they don't break the URL's structure. Use Full URI mode when your input is an entire URL you want to make transport-safe. It preserves those reserved characters so the URL stays valid and clickable.
Why does my decoded text show a malformed-sequence error?
Every percent sign in a URL must be followed by exactly two hex digits (0-9, A-F). Sequences like %ZZ, a lone %, or %A at the end of the string are invalid and trigger this error. If you want a literal percent sign in your output, encode it as %25 first, then decode.
How is a space encoded?
This tool encodes a space as %20 in both Component and Full URI modes, following the URL standard (RFC 3986). The plus sign (+) means a space only in HTML form bodies (application/x-www-form-urlencoded), which is a different encoding scheme. If you paste a URL that contains a +, this tool leaves it as + when decoding rather than turning it into a space.
How are non-ASCII characters handled?
Each non-ASCII character is first converted to its UTF-8 byte sequence, then each byte is percent-encoded. An accented letter like "e" with an accent produces two percent triplets, and a 4-byte emoji produces four. Decoding reverses the process and gives back the original character.
Is this tool safe to use for sensitive URLs or tokens?
Yes. All encoding and decoding runs entirely in your browser using JavaScript's built-in functions. Nothing is sent to a server, stored, or logged. You can safely paste URLs that contain API keys, session tokens, or other credentials.