URL Decoder

URL decoding reverses percent-encoding: each %XX sequence is read as a hexadecimal byte value and converted back to the character it represents, turning something like %40 back into @ and %20 back into a space. It's the inverse of the encoding process and, like Base64 decoding, is fully deterministic — there's no ambiguity about what a valid percent-encoded sequence decodes to.

This is useful for reading query strings and paths that come back from a browser's address bar, a server log, or an API response, since encoded values, long strings of %XX sequences, are hard to read at a glance. Decoding them here makes it immediately obvious what a link actually points to or what parameters a request contains, which is handy when debugging redirects, tracking links, or webhook payloads.

Decoding can fail or produce unexpected results if the input contains a % that isn't part of a valid two-digit hex sequence, or if a value was encoded twice — in that case the first decode still leaves percent-encoded text behind, and decoding a second time is needed to fully recover the original.