Skip to main content

URL Encoder

Encode or decode URL components, complete URLs, and form values with the correct rules, then inspect repeated query parameters in a readable table.

For a parameter name, value, or one path segment. Reserved characters such as / ? & = are encoded.

0 characters

Output

The converted result appears here.

How to use URL Encoder

  1. 1

    Choose Encode or Decode.

  2. 2

    Select query component, complete URL, or form value rules.

  3. 3

    Copy the result and inspect the parameter table for complete URLs.

What You Can Do

  • ✓Different reserved-character handling for components and complete URLs
  • ✓Form encoding with + for spaces
  • ✓Repeated query parameters displayed in their original order
  • ✓Protocol, host, path, and fragment breakdown

FAQ

Q. Why does decode sometimes fail?

A. The input must be a valid percent-encoded string.

Q. Can I use this for query params?

A. Yes. It is especially useful for parameter encoding checks.

Q. Is data sent outside the browser?

A. No. Processing is local only.

Technical Notes

Components use encodeURIComponent, complete URLs use encodeURI, and form values follow URLSearchParams-style rules. Reserved characters and spaces differ between these contexts, so the selected scope matters.

Malformed percent sequences are surfaced as errors instead of producing a partial result.

Security

Input data is processed locally and never uploaded.

Examples, URL Handling Cautions, and Common Mistakes

Examples

  • Encode search keywords with non-ASCII characters for query parameters.
  • Prepare webhook or API request values before assembling the final URL.
  • Decode an existing URL to inspect which parameters are being passed.

Cautions

  • Usually encode only parameter values, not the entire URL.
  • Encoding an already encoded string creates double encoding.
  • `+` and `%20` may be treated differently depending on form encoding and runtime.

Common Mistakes

  • Encoding the whole URL and turning `https://` into escaped text.
  • Missing double encoding and causing broken links or garbled text.
  • Sharing URLs that still include private tokens or keys.

Related Tools