KitJade
Developer ToolsRuns in your browser

URL Encoder

Percent-encode values or whole URLs, correctly.

Use the URL Encoder tool

Runs in your browserUpdated Report a problem

What this url encoder does

URL Encoder converts characters that are unsafe in a URL into percent-encoded triplets. It offers two modes: component encoding, which is correct for a single query value, and full-URL encoding, which leaves structural characters such as : / ? & = intact.

Choosing the wrong mode is the most common cause of broken links. Encoding an entire URL as a component will turn its own separators into %3A, %2F and %3F, producing a URL that no server can route.

Why use it

  • Build correct query strings for search, pagination and UTM parameters.
  • Encode file names containing spaces, ampersands or non-ASCII characters.
  • Debug redirect URLs that double-encode their parameters.

How to use it

  1. 1Paste the text or URL.
  2. 2Select Component (query value) or Full URL mode.
  3. 3Copy the encoded output.
  4. 4Round-trip it through the URL Decoder to confirm it restores the original.

Worked examples

Query value

Input

shoes & bags / size 9

Output

shoes%20%26%20bags%20%2F%20size%209

Full URL

Input

https://example.com/search?q=red shoes&page=2

Output

https://example.com/search?q=red%20shoes&page=2

Full-URL mode preserves ? = & so the link still works.

Common mistakes

  • Encoding an entire URL as a component, which destroys its structure.
  • Encoding a value twice — %20 becomes %2520.
  • Using + for spaces outside form-encoded bodies; in a path, + is a literal plus sign.

Frequently asked questions

Should I use %20 or + for spaces?
Use %20 in paths and query strings. The + shorthand only applies to application/x-www-form-urlencoded bodies.
Does URL encoding protect against XSS?
It prevents URL-structure breakage, but output encoding for HTML and JavaScript contexts requires separate, context-specific escaping.
All tools