URL TOOLS · NO REQUESTS ARE MADE

URL Decoder

Turn %XX-encoded URLs back into readable text, with double-encoding detection.

Input

Result

https://example.com/%E6%90%9C%E5%B0%8B

About this tool

Paste an encoded URL or parameter to get readable text back. The tool detects double encoding: `%2520` is `%20` encoded a second time, which means the data passed through two encoding steps — common in redirect chains and third-party tracking links. An incomplete escape, such as a trailing lone `%`, produces an explicit error rather than being skipped, because it usually means the string was truncated.

How it works

  1. Choose a decoding mode; component covers most cases.
  2. Paste the encoded text.
  3. Read the decoded result and any double-encoding warning.

Limits and rules

Up to 8,000 characters. An incomplete %XX sequence is reported as an error rather than silently dropped.

Privacy

URLs are parsed inside this browser only. A URL often carries tokens, internal paths, and personal data in its query, so nothing is uploaded, stored, or logged.

Frequently asked questions

Why do some URLs need decoding twice?
Because they were encoded twice. When an already-encoded URL is placed inside another URL as a parameter value — normal in redirects and tracking links — the `%` itself is encoded to `%25`, turning `%20` into `%2520`. The tool detects this and says so, so you know another pass is needed.
What does a decoding failure mean?
The string contains an incomplete or invalid escape, such as a trailing lone `%` or a non-hexadecimal pair like `%ZZ`. That usually means the URL was truncated or joined incorrectly. Reporting it is deliberate: silently skipping produces output that looks fine but is wrong.