URL Decoder

Paste an encoded link, query string or form body and get readable text back: %20 and + become spaces, %C3%A9 becomes é, and every query parameter is listed on its own row. Runs in your browser. Need the opposite? Use the URL encoder.

How to decode a URL

  1. Paste the encoded link, query string or form body into Input. This page starts in Decode URL mode, so the readable text appears as you type.
  2. If the text came from an HTML form or a query string where spaces show up as +, choose Form (+ for space).
  3. For a full address, read the URL breakdown under the tool: scheme, host, path, fragment and one row per query parameter, each value already decoded.
  4. If the tool reports a double-encoded value (%2520, %253A), press Decode fully to remove every layer.
  5. Press Copy output. Decoded JSON gets a Pretty-print JSON button.

What URL decoding does

URL encoding (percent-encoding) writes each unsafe byte as % followed by two hex digits. A URL decoder reverses it: it collects the bytes, reads them as UTF-8 and gives you the original characters. Multi-byte characters take several sequences, so %C3%A9 is one é and %E2%82%AC is one €. Characters that were never encoded, such as letters, digits and - _ . ~, pass through unchanged.

Decoding examples

Encoded inputDecoded outputNote
caf%C3%A9%20%26%20teacafé & teaUTF-8 letter, space and &
https%3A%2F%2Fexample.com%2Fa%3Fb%3D1https://example.com/a?b=1A whole URL stored as one value
red+shoesred shoes (Form mode) / red+shoes (other modes)+ is a space only in form data
%2520%20 after one pass, a space after Decode fullyDouble-encoded
%7B%22id%22%3A7%7D{"id":7}URL-encoded JSON
100% or %E9errorStray %, or a Latin-1 byte that is not valid UTF-8

%20 or +: decoding spaces

Two conventions exist for a space. %20 is the general percent-encoding and is valid anywhere in a URL. + comes from application/x-www-form-urlencoded, the format browsers use for HTML form submissions; it means a space only inside that kind of query string or request body. In a path, /c++/ really contains plus signs. That is why the decoder keeps + by default and turns it into a space only in Form mode. A real plus sign inside form data is sent as %2B.

Decoding query parameters and redirect links

Tracking links, OAuth callbacks and email redirects often carry a second URL inside a parameter, for example ?redirect=https%3A%2F%2Fexample.in%2Fcart. Paste the whole link: the breakdown table shows each parameter decoded on its own row, so you can read the destination without decoding the outer URL by hand. Decode parameter values separately rather than decoding the whole URL first; once %26 becomes &, it can no longer be told apart from the separator between parameters.

Why a URL will not decode

Decoded text can contain <script>, quotes or ../. Decode to read it, but escape it again before you put it into HTML, SQL or a file path.

Decode a URL in code

JavaScript

decodeURIComponent("caf%C3%A9%20%26%20tea");          // "café & tea"
decodeURIComponent("red+shoes".replace(/\+/g, " "));  // "red shoes" (form data)
new URLSearchParams("q=red+shoes&c=caf%C3%A9").get("q"); // "red shoes"
decodeURI("a%2Fb%20c");                               // "a%2Fb c" (keeps reserved chars)

Python

from urllib.parse import unquote, unquote_plus, parse_qs

unquote("caf%C3%A9%20%26%20tea")    # 'café & tea'
unquote_plus("red+shoes")            # 'red shoes'
parse_qs("q=red+shoes&page=2")       # {'q': ['red shoes'], 'page': ['2']}

PHP

rawurldecode("red+shoes%21");  // "red+shoes!"  (+ kept)
urldecode("red+shoes%21");     // "red shoes!"  (+ becomes a space)

Java

URLDecoder.decode("red+shoes%21", StandardCharsets.UTF_8); // "red shoes!" (+ becomes a space)

C#

Uri.UnescapeDataString("red+shoes%21");  // "red+shoes!"
WebUtility.UrlDecode("red+shoes%21");    // "red shoes!"

Go

url.QueryUnescape("red+shoes%21") // "red shoes!", nil
url.PathUnescape("red+shoes%21")  // "red+shoes!", nil

Common questions

How do I decode a URL?

Paste the encoded URL or string into the box. This page starts in Decode mode, so every %XX sequence becomes its UTF-8 character straight away, and a full URL is split into scheme, host, path and a table of decoded query parameters.

Why are there + signs left in my decoded text?

+ means a space only in form-encoded data. Choose Form (+ for space) to turn red+shoes into red shoes. The other modes keep + as a literal plus, which is correct for paths and for values encoded with encodeURIComponent.

What does %2520 mean?

A space encoded twice: the first pass made %20, the second encoded the % as %25. Decode fully repeats decoding until the text stops changing and tells you how many layers it removed.

Why do I get a “URI malformed” error?

A % that is not followed by two hex digits (100%, %G1) or bytes that are not valid UTF-8, such as a lone Latin-1 %E9. Replace a stray % with %25, or re-encode the source as UTF-8.

What is the difference between decodeURI and decodeURIComponent?

decodeURIComponent decodes every sequence. decodeURI leaves reserved characters such as %2F, %3F, %26 and %3D encoded so a full URL keeps its structure. To read one parameter value, use decodeURIComponent.

Is my URL sent to a server?

No. Decoding runs in your browser with the built-in decodeURIComponent, so tokens, emails or tracking IDs inside the link never leave the page.

How do I decode URL-encoded JSON?

Paste the encoded value, for example %7B%22id%22%3A7%7D. The decoder returns {"id":7}, and when the result is valid JSON a Pretty-print JSON button appears. To go the other way, use the URL encoder.