URL Decoder

What is URL encoding?

URL encoding (also called percent-encoding) is the mechanism that lets URLs carry characters that would otherwise have a special meaning or be illegal in a URL. Every “unsafe” character is replaced with a percent sign followed by two hex digits representing the character’s byte value — so a space becomes %20, a / becomes %2F, a ? becomes %3F, and an emoji or non-Latin letter becomes a sequence of two or three percent-escaped bytes (the UTF-8 encoding of the character). The system is defined in RFC 3986 and every web browser, server and HTTP client implements it the same way.

Why decode URL-encoded strings?

You see percent-encoding in three places more than anywhere else:

• Server logs and analytics dumps. Web server access logs record the URL as the client sent it, which means every query parameter, every search term, every path segment with a space or non-ASCII character shows up percent-encoded. Decoding turns /search?q=hello%20world%20%E2%98%95 into the readable /search?q=hello world ☕.
• API debugging. When you copy a request URL out of a browser’s network panel or a tool like Postman, query parameters and path segments are typically encoded. Decoding lets you confirm the client is sending exactly the value you expect — especially important when the value contains spaces, JSON, or international characters.
• Email-tracking and redirect URLs. Marketing emails wrap destination URLs in tracker links where the original URL is percent-encoded as a query parameter. Decoding shows you where the link actually goes — useful for sanity-checking links you’re about to share, or for understanding a phishing email’s structure.

In every case the workflow is the same: paste, pick the right mode, read.

How to decode URLs on ToolJutsu

1. Paste your encoded URL or query string into the input box.
2. Pick a mode. Component (the default) decodes every percent escape — use it for query-string values, form fields, or any single component you’ve pulled out of a larger URL. Full URL preserves the URL’s structural characters — use it when you’ve pasted a whole URL and want it to stay valid.
3. Read the result in the Decoded box. The output updates live as you type or paste; there’s no Convert button.
4. Click the Copy button to put the decoded text on your clipboard.
5. If the input has a malformed percent escape (a % not followed by two hex digits, for example), you’ll see an error that points at the offending sequence.

Common scenarios

When you’re debugging an API call and want to see what value a client actually sent, paste the encoded value into Component mode. That’s the right mode for any single query-string value — even one that itself looks like a URL.

When you’ve copied a full URL out of a chat message or a redirect-tracker link and want to read it without breaking it, use Full URL mode. Structural characters stay encoded so the URL remains syntactically valid; everything else (including spaces inside path segments and query values) becomes human-readable.

When the URL contains non-ASCII characters (emoji, Cyrillic, Chinese, Arabic), the decoder handles them correctly — multi-byte UTF-8 sequences are reassembled into the original character. Most modern URLs use this encoding (the %E2%98%95 you saw above is ☕).

When you need to encode rather than decode — say you’re constructing a URL and need a value escaped — use the sibling URL Encoder. The two together let you round-trip exactly.

Privacy

The decoder reads your input from the textarea and hands it to the browser’s built-in decodeURIComponent or decodeURI function, depending on the mode. Both run synchronously in JavaScript on your device. The page makes no network requests after the initial JavaScript loads, so neither ToolJutsu nor anyone else sees the URLs or query strings you paste — including any tokens, session IDs or sensitive parameters they might contain.

Compatibility notes

decodeURIComponent and decodeURI are part of the ECMAScript standard and have shipped in every browser since the early 2000s, so the decoder works in every modern desktop and mobile browser without polyfills. The same two functions are available in every JavaScript runtime (Node.js, Deno, Bun, browser workers) if you’d rather decode programmatically; the behaviour is identical to what you see here.