In form-encoded data yes, in a path segment no. This decoder treats it as a space, which is right for query strings.

Developer Encoding

URL encoder

Input

search?q=a b&filter=x/y

What to do

Output

search%3Fq%3Da%20b%26filter%3Dx%2Fy

Processed in your browser · nothing is uploaded

Local · pick the right one or lose data silently

Two encodings, because they do different jobs: component encoding escapes `&`, `=`, `/` and `?` so a value can sit inside a query string; whole-URL encoding leaves those alone because they are the structure.

How to use the url encoder

1 Paste your input. The result appears immediately.

2 Pick the operation you want.

3 Copy the result, or save it as a file.

Using the wrong one is the classic bug. Encoding a whole URL with component encoding turns `https://x.com/a?b=c` into an unusable string with the colons and slashes escaped. Encoding a query *value* with whole-URL encoding leaves an ampersand in it, which splits the parameter and silently truncates the value — a bug that appears as data going missing rather than as an error. Rule of thumb: component encoding for anything going *into* a URL, whole-URL encoding for a URL you are tidying. Decoding also treats `+` as a space, which is right for form-encoded data and not for a path segment.

Questions

What is the difference between the two encodings? −

Component encoding escapes the structural characters too, for values going into a URL. Whole-URL encoding leaves them, for a URL you are cleaning up.

Why did my query value get truncated? +

Does + mean a space? +

Why is a space sometimes %20 and sometimes +? +

Is my URL uploaded? +

Sources

MDN — encodeURIComponent()

Was this tool any good?

INTERNAL SIGNAL ONLY · WE USE IT TO FIND TOOLS WORTH REBUILDING