URL Encoder and Decoder

Encode or decode text for URLs and inspect every part of a URL, without sending it anywhere.

  • Runs in your browser
  • Nothing is uploaded
  • Ctrl/⌘ + Enter runs it

Paste text or a URL. Nothing leaves your browser.

How to use this tool

  1. Paste text or a URL, or load the example.
  2. Choose component or full URL encoding.
  3. Select Encode or Decode; tick + as space for form data.
  4. For a URL, read its parts and query parameters in the table.

Quick answers

What is URL encoding?

URL encoding, or percent-encoding, replaces characters that are not allowed or have a special meaning in a URL with % followed by two hex digits, such as %20 for a space.

What is the difference between component and full URL encoding?

Component encoding escapes URL syntax characters like / ? & and =, so a value can sit safely inside a query string. Full URL encoding keeps that syntax so a complete URL stays usable.

Why does decoding fail?

A % must be followed by two hex digits, and the decoded bytes must form valid UTF-8. The tool shows the first sequence that breaks either rule.

Common use cases

  • Encode a query parameter value
  • Read an encoded redirect or callback URL
  • Inspect query parameters

What this tool does

  • Encode a value for a query string, or a whole URL while keeping its structure
  • Decode percent-escapes, optionally reading + as a space
  • Point to the exact malformed escape instead of failing silently
  • Split a URL into protocol, host, port, path, query parameters and fragment

Examples

Debug an OAuth redirect

Paste the callback URL to read its decoded redirect_uri, state and code parameters one by one.

Build a safe query value

Encode a search phrase with spaces, ampersands and accents before adding it to a link.

Common issues

  • Component encoding escapes / ? & = and #; use it for a single value, not for a whole URL.
  • In form submissions + means a space; elsewhere it is a literal plus sign.
  • Encoding a value twice turns % into %25.

Privacy and security

Everything runs in your browser. Your data never leaves your device. The tool logic runs locally and does not send your input, output, files, or generated values to analytics.

FAQ

Is my URL sent anywhere?

No. Encoding, decoding and parsing run in your browser.

Does it handle accents and emoji?

Yes. Text is encoded as UTF-8, so é becomes %C3%A9.

Are repeated query parameters kept?

Yes. Each occurrence is listed in order.

Can I parse a URL without https://?

Yes. Input without a scheme is read as https.