URL Decode

Turn percent-encoded text like %3D, %20 and %C3%AB back into readable characters. An option lets you treat plus signs as spaces for query strings from HTML forms.

Use the tool

Why this tool exists

Links copied from analytics, server logs and redirect chains are full of %2F and %3F, and you cannot tell where a nested URL begins and ends. A search query stored in a log is unreadable until it is decoded.

This tool reverses percent-encoding with the browser's decodeURIComponent, so multi-byte UTF-8 sequences become proper characters. One checkbox handles the form convention where + means a space, which the standard function leaves alone. If the text contains a broken sequence such as a lone %, you get a clear message. Nothing leaves your browser.

How to use it

  1. Paste the encoded text or URL into the box.
  2. Tick "Treat + as space" if the text comes from an HTML form or a query string.
  3. Read the decoded text in the output.
  4. Copy the result, or fix the input if it reports malformed encoding.

Frequently asked questions

When should I treat + as a space?

Use it for application/x-www-form-urlencoded data, which is what HTML forms and most query strings use. Leave it off for paths and for plain percent-encoded text, where a plus sign is a real plus sign.

What does "Malformed percent-encoding" mean?

A % is not followed by two hex digits, or the bytes do not form valid UTF-8. This happens with truncated links or text that was never encoded. Fix or remove the broken sequence and try again.

My result still contains %25 or looks encoded. Why?

The text was probably encoded twice. Run the decoder a second time on the output. %25 is an encoded percent sign, which is the usual sign of double encoding.

Will it decode a whole URL?

Yes, but it decodes everything, including characters that were escaped on purpose, such as %26 for an ampersand. To inspect the parts safely, use the URL Parser, which splits the address first.