Skip to content
Toolore

Developer Tools

URL Decoder

Decode a percent-encoded URL back to readable text. If it contains a query string, the parameters are also broken out into a table — which is usually the reason for decoding one in the first place.

Encoding is not encryption

Percent-encoding makes characters safe inside a URL; it hides nothing. Everything here runs in your browser and nothing is uploaded.

How to use this tool

  1. Paste the encoded URL or value.
  2. The decoded text appears below, with any query parameters listed separately.

Notes and limitations

  • A percent sign must be followed by two hexadecimal digits. A literal percent has to be written as %25, and a stray one is the usual cause of a decoding failure.
  • In the parameter table, + is treated as a space, matching how form submissions encode query strings.
  • A parameter that fails to decode is shown as it was rather than being dropped, so a single malformed value does not hide the rest of the URL.
  • Some URLs are encoded more than once. If the result still contains percent escapes, decode it again.
  • Everything runs in your browser and nothing is uploaded. That said, treat any third-party website with caution when handling production data — if a value would cause real damage if leaked, process it with your own local tooling instead.

Frequently asked questions

Why does decoding fail with a malformed sequence error?

Because a % is not followed by two valid hexadecimal digits. Most often the URL contains a literal percent sign that should have been written as %25.

Why does my URL still have %20 in it after decoding?

It was probably encoded twice — a %20 becomes %2520 when encoded again. Run the result through the decoder a second time.

What does %3A or %2F mean?

They are the escaped forms of : and /. Seeing them inside a URL usually means a complete address has been embedded as a parameter value, such as a redirect target.

Related tools