Skip to main content

URL Decode

​

Result

Copied links often turn into long strings like %C3%A9%20%E2%82%AC. Paste them here and they are decoded to readable text instantly. For a full URL, the domain, path and every parameter are listed in a table, so search terms and tracking codes (utm) are easy to read. Legacy encodings such as Windows-1252 or Shift_JIS are supported too. To encode text for a URL, switch to the encode tab above or use URL Encode. Decoding runs entirely in your browser.


How to use the URL decoder​

  1. Paste a URL or %XX string; the decoded result appears immediately – caf%C3%A9 becomes “café”.
  2. For a full URL (starting with https://), “URL parts” shows the domain, path, fragment (#) and every parameter name and value.
  3. Options: “+ as space” (on by default) for search and form URLs – turn it off if a + really is a plus sign; “Decode repeatedly (e.g. %2520 → %20 → space)” for URLs encoded twice or more (%25C3); and “Character encoding” if the result is still garbled.
  4. Click “Copy” or “Send to encode” to re-encode and compare.

Why do URLs look like %C3%A9 garbage?​

URLs only allow a limited set of ASCII characters, so accented letters, other scripts and spaces are replaced by % plus two hexadecimal digits. The address bar usually shows the readable version, but when a link is pasted into chat, email or code you see the raw encoding. In UTF-8, every non-ASCII character becomes two to four %XX groups.

Why URL decoding fails or stays garbled​

  • An incomplete %: % must be followed by two hex digits (0–9, A–F). Strings like 100% or a cut-off %C3 fail; this tool shows the position. A literal % should have been written as %25.
  • A different character encoding: older sites and systems often used legacy encodings – for example Windows-1252, where “café” is caf%E9. Decoding as UTF-8 fails; switch “Character encoding” to Windows-1252.
  • Double encoding: redirects and tracking links sometimes encode a URL twice, so % itself becomes %25, e.g. %25C3%25A9. Tick “Decode repeatedly (e.g. %2520 → %20 → space)”.
  • + turned into a space: if the original was a real plus (such as C++), untick “+ as space”.

Reading URL parameters​

Everything after ? is the query string: parameters separated by &, each written as name=value. For example:

https://www.google.com/search?q=caf%C3%A9&hl=en&utm_source=newsletter

ParameterMeaning
utm_source, utm_medium, utm_campaignMarketing tracking codes: source, medium, campaign
fbclid, gclidFacebook and Google Ads click IDs
q, keyword, querySearch term
page, pPage number
redirect, return_urlWhere to go after login or checkout (the value is often another encoded URL)

Before sharing a link, you can delete utm_ and fbclid parameters to make it much shorter.

URL decoding in each programming language​

LanguageStandard decoding (%XX)Form format (+ → space)
JavaScriptdecodeURIComponent(s)new URLSearchParams(s).get('q')
Pythonurllib.parse.unquote(s)urllib.parse.unquote_plus(s)
JavaURLDecoder.decode(s.replace("+", "%2B"), UTF_8)URLDecoder.decode(s, UTF_8)
C#Uri.UnescapeDataString(s)WebUtility.UrlDecode(s)
PHPrawurldecode($s)urldecode($s)
Gourl.PathUnescape(s)url.QueryUnescape(s)

JavaScript’s decodeURIComponent() throws a URIError on an incomplete %, so wrap it in try…catch. For a legacy charset in Python use unquote(s, encoding='cp1252').

Frequently asked questions​

How do I turn %C3%A9 in a URL back into readable text?​

Paste the whole URL or %XX string into this tool and it is decoded instantly – for example caf%C3%A9 becomes “café”. Full URLs are also broken down into their parameters.

What if the decoded text is still garbled?​

Try another character encoding such as Windows-1252 for older Western sites. If the result still contains %25 or other %XX sequences, the URL was encoded twice – tick “decode repeatedly”.

What does the “incomplete %” error mean?​

In URL encoding, % must be followed by two hexadecimal digits. The error appears when a string was cut off, or when a literal % (as in 100%) was not encoded as %25. The tool shows where it happens.

Should a + in a URL be treated as a space?​

In query strings (after ?), + usually means a space, as in Google search URLs. In a path, or when the text really contains a plus (such as C++), it should stay a plus. This tool treats + as a space by default; you can turn that off.

Is my data uploaded?​

No. Decoding happens directly in your browser; URLs and their contents are never sent to this site or any third-party server.

Other useful tools