URL Encoder

Popular

Mode

Plain text / URL

Encoded

About URL Encoder

The URL Encoder/Decoder converts special characters to and from percent-encoded format used in HTTP URLs. It handles full URL encoding and individual component encoding, plus a dedicated form-urlencoded mode for HTML form payloads (spaces as +, extra reserved characters escaped). Query parameters, path segments, and form bodies are correctly escaped for transmission over the web.

Frequently Asked Questions

What is URL encoding?

URL encoding replaces unsafe characters with a % followed by two hexadecimal digits. For example, a space becomes %20 and & becomes %26.

When do I need to URL encode?

When passing user input as query parameters, when a value contains &, =, ?, # or spaces, or when constructing URLs programmatically in any language.

What is the difference between encodeURI and encodeURIComponent?

encodeURI encodes a full URL and leaves structural characters like / and ? intact. encodeURIComponent encodes a single value and escapes those characters too — use it for individual query parameter values.

When should I use Component mode vs Form (x-www-form-urlencoded) mode?

Use Component mode for query string values and path segments in URLs — it matches encodeURIComponent. Use Form mode when building an application/x-www-form-urlencoded HTTP request body (classic HTML form POST): spaces become + and !'()* are also escaped, matching what browsers send.

Why does + sometimes mean a space in URLs?

In HTML form POST encoding, + represents a space as shorthand. In modern URL percent-encoding, %20 is the correct and unambiguous representation.

Related Tools

Base64 HTML Entities

Command Palette

About URL Encoder

Frequently Asked Questions

About URL Encoder

Frequently Asked Questions