URL Encode / Decode

URL Encode Decode converts text to and from percent-encoding, the escaping scheme defined in RFC 3986 that lets URLs safely carry characters they could otherwise never contain. When you encode, the tool walks through your input byte by byte, leaves the "unreserved" characters alone (A-Z, a-z, 0-9, and the marks - _ . ~), and rewrites everything else as a percent sign followed by two hexadecimal digits. A space becomes %20, an ampersand becomes %26, a question mark becomes %3F, and a Cyrillic or emoji character is first turned into its UTF-8 bytes and then each byte is percent-escaped. Decoding reverses the process, reading each %XX triplet back into the original byte and reassembling the UTF-8 string. Everything happens locally in your browser using the JavaScript engine's own encoding routines, so nothing you paste is ever uploaded, logged, or sent to a server. This matters when the "URL" you are debugging is actually a signed API request, an OAuth callback, or a query string carrying a customer email or session token. Real uses are everywhere: fixing a link that breaks because it contains a & or a # in the middle, building a redirect_uri for a login flow, encoding search terms before appending them to an endpoint, reading a webhook payload that arrived double-encoded, or decoding a UTM-tagged campaign URL to see the raw parameters. Developers, QA testers, marketers checking tracking links, and support staff pasting a mangled URL from a ticket all benefit. A practical tip: encode only the component (a single parameter value) rather than a whole URL, otherwise you will escape the :// and slashes that need to stay literal. Watch for double-encoding, where %2520 means a %20 was itself encoded again. If decoding fails on a stray % that is not followed by two hex digits, that is usually the real bug in the link you were given, not a fault in the tool.