URL Decoder

Decode a percent-encoded URI component.

Use this tool

Result

The result appears in this panel after you run the tool.

About this tool

Percent-escapes are turned back into characters. A sequence the decoder rejects is shown as an error instead of a partial string.

The encoder is the reverse: it percent-encodes UTF-8 text.

How to use it

  1. Paste the encoded text.
  2. Decode.
  3. A malformed % sequence is reported on the page.

Limitations

Malformed escapes fail the entire value

decodeURIComponent is strict

The decoder calls decodeURIComponent on the textarea as typed, with no extra cleanup. A well-formed escape becomes the character those UTF-8 bytes represent. A percent sign that is not followed by two hex digits, or a pair that is not hex, throws, and the panel shows the exception. There is no best-effort mode that skips the bad escape and continues. One broken sequence rejects the whole paste.

A plus sign stays a plus sign. This is not a form-urlencoded parser, so a query that used + for spaces will still show plus signs after a successful decode. Spaces that were written as %20 come back as spaces. The call does not look for a scheme, and it never partitions the string at ampersands or equals signs. If those characters were encoded, they return as characters. If they were literal, they stay literal, and any other escape in the same string is still decoded.

Round-trip losses that the encoder does not have

The matching encoder emits only valid escapes, so its output decodes. The reverse path is where spelling is lost. Uppercase and lowercase hex both decode, and a fresh encode writes uppercase. Unreserved characters that someone encoded by hand decode to literals and will be re-encoded as literals, so the escape text shrinks. A double-encoded value decodes once: %2520 becomes %20, not a space. Run the decoder again if you still see percent digits and you expected characters.

Decoding cannot invent a key or prove who produced the string. The result is the same text the escapes spelled. Treat it as data, not as an authentication result.

What still looks encoded after a successful run

Literal question marks, slashes, and hashes that were never escaped remain, so a full URL often “decodes” into another URL with a few sequences expanded. A successful decode still says nothing about whether opening that address is wise. Fragments and queries are not interpreted. Internationalized host names are not converted to Unicode here; the IDN page does that job for a hostname. A string of only unreserved characters is returned unchanged, which is easy to mistake for a failed run. If the box looks identical, the input had nothing this function rewrites.

Privacy

Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.