URL Encode

Percent-encode text so it is safe inside a URL. Pick component mode for query values, full URL mode to keep the address structure, or form mode for spaces as plus signs.

Use the tool

Why this tool exists

A query value containing &, = or a space can silently break a link, and a redirect URL pasted into another URL needs its slashes and question marks escaped or the receiver reads the wrong parts. Hand-editing %20 and %26 is slow and easy to get wrong.

This tool applies the same rules as the browser's own functions. Component mode matches encodeURIComponent and escapes nearly everything. Full URL mode matches encodeURI and leaves the address structure alone. Form mode swaps spaces for plus signs, as HTML forms do. Your text is processed locally and never uploaded.

How to use it

  1. Paste the text or URL fragment you want to encode.
  2. Choose a mode: component (encodeURIComponent), full URL (encodeURI) or form (space as +).
  3. Read the percent-encoded result.
  4. Copy it into your link, API call or redirect parameter.

Frequently asked questions

Which mode should I choose?

Use component mode for a single value, such as a search term or a redirect target inside a query string. Use full URL mode when you have a whole address and only want to escape unsafe characters, keeping : / ? & = intact.

Why is a space sometimes %20 and sometimes +?

%20 is the standard percent-encoding for a space and works everywhere in a URL. The + form is only valid inside query strings in form-encoded data. Form mode produces +, the other modes produce %20.

Does it encode non-English characters?

Yes. Characters are converted to UTF-8 bytes and each byte is written as %XX, so ë becomes %C3%AB. This is what modern browsers and servers expect.

Should I encode a URL twice?

No. Double encoding turns % into %25 and breaks the link. Encode each part once, at the moment you assemble the URL.