URL Encoder & Decoder

Percent-encode text for URLs and query strings, or decode encoded URLs back to readable text.

Updated October 7, 2026 By

Runs in your browser Free · No sign-up

Loading tool…

How to use the URL Encoder & Decoder

  1. Choose “Encode” or “Decode”.
  2. Paste your text or URL. Tick “Encode a full URL” to keep characters like : / ? & =.
  3. Copy the result.

About this tool

Spaces, accents and special characters must be percent-encoded before they can be used in a URL. Use this tool to build safe query parameters or to read encoded links from logs and analytics.

  • Private: your data is processed on your device and never uploaded.
  • Free with no account, limits or watermarks.
  • Fast: results appear instantly, even offline once the page has loaded.

What the URL Encoder & Decoder does

URLs may only contain a limited set of characters. Spaces, umlauts, Persian or Chinese letters and symbols such as “&”, “?”, “#” or “=” have to be written in a special form called percent-encoding: a space becomes %20, “ä” becomes %C3%A4 and “&” becomes %26. This tool converts text to that format and back, instantly and in both directions.

By default the tool encodes a single component, such as a search term or a query-string value, which escapes every reserved character. Switch on “Encode whole URL” when you have a complete address and only want to fix characters that are not allowed at all, while keeping the slashes, question mark and ampersands that give the URL its structure.

When decoding, plus signs are treated as spaces, matching how web forms submit data. All processing happens in your browser, so URLs containing tokens or private parameters never leave your device.

When to use it

  • Building links with parameters

    Encode search terms, email addresses or redirect targets before adding them to a query string such as ?q= or ?redirect=.

  • Reading tracking links

    Decode long marketing or redirect URLs to see where they really lead and which parameters they carry.

  • APIs and webhooks

    Make sure values in GET requests and callback URLs are encoded correctly so the server reads them as intended.

  • International addresses

    Convert paths with non-Latin letters to the encoded form that every system accepts, or decode them back to readable text.

Tips for the best results

  • Encode each parameter value separately, not the whole query string. Otherwise “&” and “=” are escaped and the parameters can no longer be told apart.
  • Avoid encoding something twice: %20 would become %2520. If you see %25 in a URL, it has probably been double-encoded.
  • Use “Encode whole URL” only for a complete address that is already structured correctly.
  • If decoding fails, the text contains an incomplete escape sequence such as a lone “%” — check that you copied the whole URL.

How the URL Encoder & Decoder works

Text is converted to UTF-8 bytes, and every byte that is not allowed in that part of a URL is written as a percent sign followed by two hexadecimal digits. Letters A–Z, digits and a few characters such as “-”, “_”, “.” and “~” stay unchanged.

In component mode the tool uses JavaScript’s encodeURIComponent, which also escapes reserved characters like “/”, “?”, “&” and “=”. In whole-URL mode it uses encodeURI, which leaves those structural characters intact.

Decoding uses the matching functions, decodeURIComponent and decodeURI, after converting “+” to spaces in component mode. Invalid sequences produce an error message instead of a wrong result.

Frequently asked questions

When should I encode a full URL versus a parameter?

Encode a single parameter value (the default) when you insert user text into a query string. Use full-URL mode only for a complete address that already has the right structure.

Why does a plus sign become a space when decoding?

In HTML form submissions a “+” in the query string stands for a space, so the decoder treats it that way.

Is %20 or + correct for a space?

Both are used. %20 is correct everywhere in a URL; “+” only means a space in query strings submitted by HTML forms. When in doubt, use %20.

Which characters need to be encoded?

Everything except letters, digits and - _ . ~ when encoding a component. In a full URL, characters such as / ? & = # keep their special meaning.

Is URL encoding the same as Base64?

No. URL encoding only escapes problematic characters and keeps the rest readable; Base64 rewrites all data with a 64-character alphabet.