URL encoding guide

Convert URL spaces to %20

Spaces are not safe inside URLs. Percent-encoding changes each space to %20 so the link can travel cleanly through browsers, APIs, and logs.

Open URL Encode Decode Tool View all tools

Why this happens

A pasted search term, filename, or callback value may contain a normal space. Some software handles it for you, but many APIs and logs expect the space to be encoded first.

Example

Input

https://example.com/search?q=url space encoder

Output

https%3A%2F%2Fexample.com%2Fsearch%3Fq%3Durl%20space%20encoder

How to convert spaces

Copy the URL value or the part of the URL that contains spaces.
Open the URL Encode Decode Tool and choose Encode.
Check that spaces are now %20 before pasting the result into a request, document, or redirect URL.

Whole URL or one value?

If you are fixing a normal link, you may only need to encode the part that contains the space. If you are putting one full URL inside another URL, encode the full nested URL.

That difference matters because structural characters like colon, slash, and question mark should stay readable in a normal URL, but must be escaped when the URL becomes a query value.

Common mistakes

Encoding the same value twice and ending up with %2520
Encoding an entire URL when only one query value needed encoding
Leaving spaces in callback URLs used by OAuth or webhook settings
Replacing spaces with plus signs when the target expects %20

FAQ

Is %20 the same as a normal space?

%20 is the percent-encoded form of a space. It represents the same character in a URL-safe way.

Should I use + or %20 for spaces?

%20 is the safer general choice for URL paths and most encoded values. Plus signs are mainly used in form-style query encoding.

Can the URL tool convert only the query value?

Yes. Paste just the query value if you do not want the rest of the URL encoded.