Toolsky

Free Online Tools & Utilities for Every Task.

URL Decoder

Decode any URL that has been encoded.

Links rarely arrive in your inbox looking clean. They turn up as long strings of percent signs and numbers, copied out of an email client, a redirect chain, an analytics report or a browser's address bar, and you cannot tell where they lead or what they say. The URL Decoder on ToolSky reverses the encoding instantly: paste in the encoded address and read the plain, human-legible version, percent signs translated back into the spaces, punctuation and characters they were hiding.

What Percent-Encoding Hides in a URL

URLs are only allowed to contain a limited set of characters, so everything else, spaces, ampersands inside values, accented letters, symbols, is rewritten as a percent sign followed by two hexadecimal digits representing the character's byte value. A space becomes %20, a colon %3A, a question mark %3F. This is called percent-encoding, and the MDN glossary entry on percent-encoding documents which characters must be escaped and why. The encoded form is perfectly valid and browsers handle it silently, but to a human it reads like static, and worse, it conceals the destination of links you might not want to click blindly.

What the URL Decoder Unpacks

  • Fully encoded URLs, such as those produced when a whole address is passed as a parameter inside another link.
  • Encoded query strings and individual values, revealing search terms, page names and tracking codes in plain words.
  • Encoded fragments of text copied from logs, emails and spreadsheets, where %20 and friends make manual reading miserable.

Decoding is a reading task; the companion job of writing is handled by the URL Encoder, and once a link is readable you can take it apart properly with the URL Parser, which separates its protocol, host, path and parameters.

How to Decode a URL

  1. Copy the encoded URL or text fragment exactly as you found it, percent signs and all.
  2. Paste it into the decoder's input field.
  3. Run the decode action.
  4. Read the plain result and confirm the destination and parameters are what you expected.
  5. If percent signs remain in the output, the text was probably encoded twice; decode it once more, as explained below.
  6. Copy the decoded URL for use in your browser, document or report.

Decoding a Real String, Character by Character

Consider this charmless string: https%3A%2F%2Fexample.com%2Fsearch%3Fq%3Dblack%20coffee. Working through it, %3A is the colon after https, each %2F is a forward slash, %3F is the question mark that opens the query string, %3D is the equals sign, and %20 is the space in the search term. Decoded, the whole thing resolves to https://example.com/search?q=black coffee, an ordinary search link. The same logic frees non-English text: a sequence like %C3%A9 represents the two bytes of the letter é in UTF-8, so a decoded café menu link reads as words again instead of escape codes.

Decoding Traps: Double Encoding and Plus Signs

The most confusing case is double encoding, where text was encoded twice, often by two systems each doing their job. A space becomes %20, and then the percent sign itself is encoded as %25, leaving %2520. One pass of decoding turns it back into %20, which looks unfinished, and a second pass completes the job. If your decoded output still contains percent codes, run it again rather than assuming the tool failed.

Plus signs cause the other classic misunderstanding. In query strings produced by form submissions, a + commonly stands for a space, a convention from form encoding, but in a URL path a + is a literal plus. A careful decoder treats the two contexts differently, and when you inspect results, check any + in a path before assuming it means a space. Finally, a lone % or an invalid pair like %ZZ has no meaning at all; well-behaved decoders leave it visible so you can see the source data was flawed.

One place fully encoded URLs appear constantly is the redirect parameter. Login pages, payment gateways and unsubscribe links routinely carry an entire destination address encoded as a single value, so the outer link reads as one long string of percent codes after a return= or redirect= label. Decoding peels that parameter back into a readable address, which is the fastest way to verify that a "sign in to continue" link really returns you to the site it claims, rather than somewhere with a similar name and worse intentions.

Frequently Asked Questions About URL Decoding

Why does my link still contain %20 after I decode it?

It was encoded twice. The first decode removed the outer layer, turning %2520 into %20. Decode the result a second time to reveal the original character.

Is a plus sign the same as %20?

Only in query strings and form data, where + traditionally represents a space. In the path portion of a URL, + is a literal plus character and should stay one.

Does decoding a URL visit the website or run anything?

No. Decoding is pure text translation done on the string you paste. Nothing is fetched, opened or executed, which is why decoding is a safe first step for inspecting a suspicious link.

Can the decoder handle accented and non-English characters?

Yes. Non-ASCII characters are encoded as UTF-8 byte sequences, such as %C3%A9 for é, and the decoder reassembles those bytes into the correct characters.

Should I decode the whole URL or just part of it?

Either works for reading purposes. Decoding just a query value is handy when the rest of the link is already readable, while decoding the whole string is right for links that were encoded end to end as a single parameter.

What does %25 mean?

It is the encoding of the percent sign itself. Seeing %25 in decoded output usually means the original text contained a literal % or that another layer of encoding remains.

Why do some decoded URLs still look wrong?

The source may have been encoded with a different or broken process, truncated during copying, or encoded three times. Decode repeatedly until no valid percent codes remain, and check the string was not cut off at either end.

Read the Link Behind the Link

An encoded URL is not broken, just dressed for travel. Decode it before you click, quote or debug it, and the destination, the search terms and the tracking baggage all become plain to see.