URL Encoder & Decoder

How to use

1. Choose Encode to make text safe for a URL, or Decode to read percent-encoded text.
2. Choose Component for one value, Whole URL to preserve link separators, or Form value when spaces must become `+`.
3. Paste or type the input. The result changes immediately and remains only in this browser.
4. When the input has a query string, edit its decoded names and values in the Query parameters table; the rebuilt URL replaces the input.
5. Copy the result, or choose Use result as input to check the reverse conversion.

Choose the scope before encoding

A URL component is one piece of data: a search term, redirect target, path segment, or query value. In that situation `&`, `=`, `?`, `/`, and `#` must be encoded so they cannot become URL separators. Component mode follows RFC 3986 and encodes those reserved characters; for example, `a&b=c` becomes `a%26b%3Dc`.

Whole URL mode is for a complete address that already has structure. It keeps delimiters such as `:`, `/`, `?`, `&`, `=`, and `#` readable while encoding spaces and Unicode text. It should not be used for one query value, because an unencoded `&` or `=` inside that value would change the meaning of the link.

Percent encoding and form encoding are not identical

RFC 3986 defines a percent-encoded byte as `%` followed by two hexadecimal digits, so a space is `%20`. It reserves characters such as `?`, `&`, and `=` because they delimit parts of a URI; the unreserved set is letters, digits, `-`, `.`, `_`, and `~`. Unicode text is first represented as UTF-8 bytes, which is why Korean and emoji use several `%XX` sequences.

HTML forms use the related `application/x-www-form-urlencoded` convention. In a form value, a space becomes `+`, and a literal plus sign must be `%2B`. Query tables use that convention because it matches ordinary form-generated query strings. Decode errors are shown instead of guessed: a percent sign must have exactly two hexadecimal digits, and those bytes must form valid UTF-8.

Inspect query values without breaking delimiters

A query string begins after `?`; `&` separates parameters and the first `=` separates each name from its value. The editable table decodes those names and values individually, so a value such as `redirect=https%3A%2F%2Fexample.com%2Fnext%3Fa%3D1%26b%3D2` is readable without turning its embedded `&` into a new outer parameter.

Editing a row rebuilds the query with form-style escaping and preserves the base URL and fragment after `#`. A parameter written without `=` is retained as a name-only parameter until you enter a value. This is useful for checking UTM links, OAuth redirect URLs, and API requests before copying the corrected address.

Frequently asked questions