DN

URL Encoder & Decoder

Percent-encode and decode URLs, and break down query strings.

Treat input as

Component mode encodes every reserved character (like / ? & =) — use it for a single query value or path segment.

Text or URL

Encoded

The result appears here as you type

About the URL Encoder/Decoder

Encode text so it's safe to put in a URL, or decode percent-encoded strings like hello%20world back into readable text. Results update live as you type, and non-English characters and emoji are handled correctly as UTF-8.

Paste a full URL and DevNest also breaks it down into its protocol, host, path and fragment, and lists every query parameter with its decoded value.

How to use the URL Encoder/Decoder

  1. 1

    Choose a direction

    Select Encode to make text URL-safe, or Decode to turn percent-encoding back into text.

  2. 2

    Pick the scope

    Use Component for a single value or path segment, or Full URL to keep characters like / ? & intact.

  3. 3

    Paste your text

    The result appears instantly. Turn on form encoding if spaces should be written as +.

  4. 4

    Inspect the URL

    For full URLs, check the breakdown and query parameter table, and copy any value.

Frequently asked questions

What is URL encoding?

URL encoding, also called percent-encoding, replaces characters that aren't allowed or have special meaning in URLs with a % sign followed by two hexadecimal digits. For example, a space becomes %20 and é becomes %C3%A9.

What's the difference between Component and Full URL mode?

Component mode (encodeURIComponent) encodes every reserved character, including / ? & = and #, so use it for individual query values or path segments. Full URL mode (encodeURI) leaves those structural characters alone so a complete URL still works.

Should spaces be %20 or +?

In most of a URL, spaces are encoded as %20. In HTML form submissions (application/x-www-form-urlencoded), spaces in the query string are written as +. Turn on form encoding to use + for spaces and to decode + back into spaces.

Why do I get an error when decoding?

The input contains a % sign that isn't followed by two valid hexadecimal digits, or a sequence that isn't valid UTF-8. A literal percent sign must itself be encoded as %25.

Is URL encoding the same as encryption?

No. URL encoding only makes text safe to include in a URL. Anyone can decode it, so it provides no security or privacy.