It turns percent-encoded sequences like %20 back into the original characters, and may map '+' to space in form-style strings, recovering human-readable text.
Malformed percent sequences or mixed encodings cause errors. Ensure the input is valid percent-encoded UTF-8 and try decoding smaller chunks.
In query-string style encoding, '+' often means space. The tool applies the decoding rules shown in its options.
Decoding is for inspection here. In your own app always decode with trusted libraries and validate output before using it in HTML or SQL.
Some pipelines decode multiple times by mistake, corrupting strings that legitimately contained '%'. Decode exactly at trust boundaries, not repeatedly.
They normalize and parse URLs for routing and caching. Wrong encoding can change cache keys or route to the wrong origin; consistency matters in infra.
Reserved characters differ by segment. Query values often need stricter encoding than some path segments; RFC 3986 defines allowed unreserved vs reserved sets.
Servers log percent-encoded requests. Decoding locally helps verify unicode, emojis, and punctuation the client actually sent before blaming the backend.
Server-Side Request Forgery tricks servers into calling internal URLs. Decoding user-controlled URL parts is one step; never fetch arbitrary decoded URLs blindly.
HTML entities like & protect markup in pages. URL percent-encoding protects URI syntax. Use the right encoding for HTML attributes vs href query strings.