URL Decoder Online — Percent Decoding

Every non-Latin letter takes two bytes in UTF-8, and each byte is written as a percent plus two hex digits, which is why you see pairs such as %D0 and %D1. Paste the entire run at once: decoding half a letter produces nothing meaningful. After you press decode, the word reassembles.

A plus only means a space inside form data encoded as application/x-www-form-urlencoded; elsewhere in a URL it is just a character. Standard decoding is not required to touch it. If you are unpacking a submitted form and want the spaces back, swap the plus signs for %20 first.

A lone percent sign, or a percent not followed by two hex digits — typically a truncated link, or a literal percent inside a password. Check that you copied the fragment whole and did not lose the tail. A literal percent has to be written as %25 or removed by hand before decoding.

Yes. The scheme and host rarely contain percent sequences and pass through untouched, while the query string is unpacked. Remember that a nested link stops being safe to re-embed once decoded — it has to be encoded again before it goes back into a parameter.

For reading, yes; for navigation, not always. Many systems accept a decoded address with spaces and non-Latin letters, but nesting that string inside another parameter breaks it, because & and = are then read as separators. Encode it again to restore a usable link.

No. Decoding runs in the page script inside your tab, and the fields empty when you press clear or reload. Internal links carrying tokens or order ids can be unpacked here without ending up in somebody else's logs.