What percent-encoding does
URLs can only carry a limited set of characters. Anything else, such as a space, an accented letter or an emoji, is written as a percent sign followed by the hexadecimal value of each of its UTF-8 bytes. A space becomes %20 and é becomes %C3%A9. Decoding turns those sequences back into the original text.
One value or a whole URL
The most common mistake is using the wrong scope. Encoding one value is for a single piece, such as a search term that goes after q=. It escapes every character that could be mistaken for structure, including ? & = / and #, so a term like "fish & chips" cannot break your query string. Encoding a whole URL is for a complete address that is already structured. It leaves : / ? # & = alone and only fixes spaces and non-ASCII characters.
If you encode a complete URL as one value you get https%3A%2F%2Fexample.com..., which is correct only when that URL is itself a parameter of another URL, such as a redirect target.
Spaces: %20 or +
In a URL path, a space is always %20. In the query part of an HTML form submission, a space is traditionally written as +, and a real plus sign is written %2B. Many servers accept both in query strings, but only %20 is safe everywhere, which is why it is the default here. Switch on the plus options when you are working with form data.
Broken and double-encoded text
Real-world text is often not clean. A stray % in the middle of a sentence, or bytes from an older Latin-1 system, make a strict decoder fail on the whole string. This tool decodes everything it can, leaves the rest exactly as written, and lists each problem with its position so you can see what to fix. If the result still contains percent sequences, the text was probably encoded twice, and you can decode it again with one click.
Reading a URL
When your text is an address, the tool also breaks it into scheme, host, port, path and fragment, and lists each query parameter with its value decoded. That is the quickest way to see what a long tracking link actually contains.