Developer & Security Processed in your browser · Client-side privacy

URL Encoder & Decoder

Encode special characters into percent-encoded URL components or decode them back to plain text.

Copied!
Processed URL Component —

—

How to Encode and Decode URL Strings

  1. Enter your web URL or query string parameter.
  2. Select "Encode" (percent-encoding unsafe characters) or "Decode" (restoring readable characters).
  3. Copy the safe result to use in your API calls or web addresses.

RFC 3986 Percent-Encoding

  • Replaces reserved characters with a "%" followed by their two-digit hexadecimal ASCII/UTF-8 value (e.g. space becomes %20).

Example

  • Raw: https://example.com/search?q=loan & emi
    Encoded: https%3A%2F%2Fexample.com%2Fsearch%3Fq%3Dloan%20%26%20emi

Common Applications

  • Safely passing query parameters in GET requests.
  • Decoding tracking UTM query parameters.
  • Handling non-Latin characters in web addresses.

Frequently Asked Questions

What is the difference between encodeURI and encodeURIComponent?

encodeURI preserves protocol delimiters (//, ?, &) for full URLs, whereas encodeURIComponent escapes everything including slashes, perfect for single parameters.

Does a space encode as %20 or +?

In standard URL path percent-encoding, spaces become %20. In query string application/x-www-form-urlencoded forms, spaces are often represented by +.