URL Encoder and Decoder
Turn text into a form that is safe inside a web address, or decode percent signs such as %C3%A9 back to readable text. Pick the right kind of encoding for what you are building, and paste a link with a query string to see each parameter decoded on its own line.
How it works
- Choose Encode or Decode, and the kind of encoding.
- Type or paste your text.
- Read the result. A query string is also split into its parameters.
- Copy the result.
What people use it for
Building a link
Put a search term or a return address into a query string without breaking it.
Reading a messy link
Decode a long tracking link to see its real parameters.
Debugging an API call
Check why a space, a plus sign or an ampersand arrives wrong.
Questions
- Which encoding should I use?
- Component encoding for a single value placed inside a URL, such as a query parameter. Full address encoding for a whole URL, which keeps : / ? & = # as they are. Form encoding for the body of an HTML form, which writes spaces as +.
- Why is a space sometimes %20 and sometimes +?
- %20 is the general rule for URLs. The + for a space is only the convention of HTML forms and many query strings. When decoding, tick the option that reads + as a space only if the text came from a form or a query string.
- What does the strict option do?
- It also encodes ! ' ( ) and *, which the standard URL syntax (RFC 3986) allows to appear as they are but which can confuse some systems. It follows that standard for data placed in a URL.
- Why can decoding fail?
- A lone % that is not followed by two hexadecimal digits is invalid, and so are byte sequences that are not valid UTF-8 text. The message tells you where the problem is.