Encode text so it is safe inside a URL, decode a percent-encoded link back to readable text, or paste a full URL to see its parts and every query parameter.
Pyalm builds custom software, APIs and integrations for businesses in India and the UAE. We made these developer tools for our own team — use them free, and talk to us when you need something built.
Only a limited set of characters is allowed in a URL. Spaces, ampersands, Arabic or Hindi text and emoji must be percent-encoded — a space becomes %20 — or the link breaks or the server reads the wrong parameter. Encoding a value before you add it to a query string prevents both.
Encoding a single value (a search term, a redirect URL inside a parameter) should escape &, = and / too — that is component encoding. Encoding a whole URL should leave its structure alone. The tool offers both, matching JavaScript's encodeURIComponent and encodeURI.
📖 Read the full guide: URL Encoding Explained: %20, + and When to Encode
Encode text to Base64 or decode it back — with full UTF-8 and URL-safe support.
Send GET, POST, PUT, PATCH and DELETE requests from your browser and inspect the response.
Decode a JSON Web Token's header and payload and read its claims and expiry.
Both can represent a space. %20 is valid everywhere in a URL; + means space only in the query string of form-encoded data (application/x-www-form-urlencoded). The decoder can treat + as a space when you need it to.
Just the values, almost always. Build the URL from its parts and encode each parameter value with component encoding. Encoding an already-built URL can double-encode characters or leave & and = ambiguous.
%25 is an encoded percent sign — a sign that something was encoded twice. Decode once and check whether the result still contains %XX sequences.