Data tools

URL Encode/Decode

Encode and decode URI components, full URIs, and form URL-encoded text.

Processed locally in your browser. Your input is not uploaded to our server.

0 characters
0 characters

Enter or load data to begin

How to use URL Encoder

  1. Paste the component, URI, or form text to transform.
  2. Choose encode or decode and the component, full-URI, or form rule set.
  3. Verify separators, plus signs, and percent sequences before copying the output.

Supported behavior

URL Encode/Decode applies the correct percent-encoding rules for three different contexts. Component mode behaves like encodeURIComponent, escaping characters that would otherwise separate URL structure. Full-URI mode behaves like encodeURI and retains structural separators such as colon and slash. Form URL encoding follows application/x-www-form-urlencoded conventions, representing spaces as plus signs; form decoding converts plus to space before percent-decoding. Corresponding decode modes reverse valid sequences into plain text. A malformed percent sequence produces a precise error and leaves the input plus any prior valid result intact instead of guessing. Pasted values and selected .txt files are processed entirely in your browser and are never uploaded or requested as addresses. Encoding does not validate that a URL exists or make untrusted destinations safe, and applying the wrong mode can double-encode percent signs or hide separators. Choose component mode for a query value, full URI only for an already structured address, and form mode for form bodies.

  • The tool transforms text but does not fetch, validate ownership of, or assess the safety of a URL.
  • Already encoded input can become double-encoded if encode is applied a second time.

Examples

                coffee & tea

Result: coffee%20%26%20tea

                city=S%C3%A3o+Paulo

Result: city=São Paulo

Common use cases

  • Encode a search phrase for placement inside one query parameter.
  • Decode a percent-escaped path during local debugging.
  • Prepare or inspect an application/x-www-form-urlencoded value.

Frequently asked questions

Why are spaces sometimes + and sometimes %20?

Form encoding uses + for spaces, while URI component encoding uses %20.

When should I use component mode?

Use it for one path or query value so reserved URL separators are escaped as data.

What happens to a malformed % sequence?

Decoding stops with a precise error and preserves the original text.

Does full-URI encoding escape slashes?

It follows encodeURI-like behavior and preserves structural URL separators such as slashes.