URL Decoder - Decode %20 and Percent-Encoded URLs

URL Decoder - Decode %20 and Percent-Encoded URLs

 What Is a URL Decoder? 

A URL decoder converts percent-encoded characters back into the plain text they represent. In an encoded address, characters that are unsafe or reserved appear as a percent sign followed by two hexadecimal digits — %20 for a space, %26 for an ampersand, %3F for a question mark.  Decoding reverses that substitution, turning a string of escape sequences back into something you can actually read. To go the other way and prepare a value for use in a URL, use the URL encoder.

 How to Use This Tool 

1. Paste the encoded URL or text into the input field
2. Click the decode button
3. Read or copy the decoded plain-text result

 When You Need to Decode a URL 

- Reading a long tracking or campaign link to see what parameters it actually carries
- Checking what a redirect URL points to when the destination is embedded as a parameter
- Debugging an API request by confirming exactly what value the server received
- Reviewing form submissions or query strings recorded in server logs
- Reading non-English text such as Urdu or Arabic that appears as long %XX sequences

 Common Sequences You Will See 

- %20 is a space (a plus sign also means a space in form-encoded query strings)
- %26 is an ampersand &
- %3F is a question mark ?
- %3D is an equals sign =
- %2F is a forward slash /
- %3A is a colon :
- %23 is a hash #
- %25 is a literal percent sign %

 Reading Non-English Text 

Characters outside the basic Latin set are encoded as multiple bytes under UTF-8, so a single Urdu, Arabic, or Chinese character can appear as three or more percent sequences in a row. This is why a short phrase in Urdu can expand into a long unreadable string in a URL. Decoding restores the original characters in a single step, which is far more reliable than manually interpreting the sequences.

 Double Encoding 

If a value passes through an encoder twice, the percent signs themselves get encoded, and %20 becomes %2520. A single decode of such a string returns %20 rather than the space you expected. When the output still contains percent sequences after decoding, run it through the decoder a second time.  Double encoding is a common cause of broken redirects and malformed API requests. If a redirect built this way has stopped working, a website status check will show whether the destination is responding at all. 

 Frequently Asked Questions 

How do I decode a URL with percent signs in it?

Paste the encoded string above and run the decoder. Every % followed by two hexadecimal digits is converted back to the character it represents, so %20 becomes a space and %2F becomes a slash. The result is the URL as it was written before encoding.

What do the most common percent codes mean?

%20 is a space, %2F a slash, %3F a question mark, %26 an ampersand, %3D an equals sign, and %25 a literal percent sign. Our guide to percent-encoding explains why each one has to be encoded in the first place.

How do I read a tracking link that has another URL inside it?

Decode the whole string. Campaign and click-tracking links usually carry the real destination in a parameter, encoded so its :// and & do not break the outer URL. Decoding turns %3A%2F%2F back into ://, which makes the inner address readable. If the link is shortened rather than encoded, the URL unshortener expands it instead.

How do I decode non-English characters in a URL?

The same way — paste the string and decode it. Characters outside ASCII are encoded as their UTF-8 bytes, which is why one accented letter can appear as several codes: %C3%A9 decodes to é. The decoder reassembles the bytes automatically.

Why does my decoded text still contain % symbols?

The string was probably encoded twice. Run the result through the decoder again — %2520 decodes to %20, which then decodes to a space.

Why did a plus sign become a space?

In form-encoded query strings, a plus sign represents a space. This is standard behaviour for that context, not an error.

Can I decode any URL I find?

Decoding only reveals what characters a link contains. It does not bypass authentication, access private data, or reveal anything the URL was not already carrying in plain view.

Does decoding tell me if a link is safe?

No. It shows you what the link contains, not whether the destination is trustworthy. A perfectly readable URL can still lead somewhere harmful.

 An Important Caution 

Encoding is not a security measure, and decoding is not a way to bypass one. Percent-encoding only changes how characters travel across a network — it hides nothing. Anyone can decode a string instantly, which is exactly why sensitive information should never be placed in a URL. Decoding also tells you what a link contains, not whether the destination is safe to visit. If you want to check where a shortened link actually leads, a URL unshortener is the appropriate tool.