Runs in your browser. Your files and text never leave your device - nothing is uploaded.
Decode URL-Encoded Text Online
The Tools Kit’s free URL Decoder turns percent-encoded links back into text you can read. Paste a string full of %20, %3A and %2F sequences and the decoded version appears as you type, so https%3A%2F%2Fexample.com%2Fsearch%3Fq%3Dhello%20world becomes https://example.com/search?q=hello world. It works on a whole URL, a query string or a single parameter value.
Decoding uses the browser’s built-in decodeURIComponent function and runs entirely on your device, so URLs containing tokens, email addresses or session IDs are never uploaded. Need to go the other way? The URL encoder turns plain text into a safe, percent-encoded value.
How to Decode a URL
- 1
Paste the encoded text
Paste a percent-encoded URL, query string or single parameter value into the Encoded URL box. A full link such as https%3A%2F%2Fexample.com%2Fsearch%3Fq%3Dhello%20world works as well as a lone value.
- 2
Read the decoded output
The readable result appears in the Decoded Output panel as you type; there is no button to press. If the input contains a malformed sequence, the panel shows an Invalid encoded URL warning instead.
- 3
Decode again if needed
If the output still contains sequences such as %20 or %3A, the value was encoded twice. Copy the result, paste it back into the input and it decodes one more layer.
- 4
Copy or clear
Click Copy to put the decoded text on your clipboard, or Clear to empty the input and start over.
There is no sign-up and no limit on how many strings you decode.
What Is URL Encoding (Percent-Encoding)?
A URL may only contain a limited set of characters, and some of those, such as ?, &, = and #, have a job: they separate the path, the query string and the fragment. When a value itself contains one of those characters, or a space or a non-English letter, it is written as a percent sign followed by the two hexadecimal digits of each byte. A URL decoder simply reverses that, reading each %xx pair and putting the original character back.
Characters outside ASCII are first converted to UTF-8 bytes, which is why one letter can turn into several sequences. The accented é is two bytes, so caf%C3%A9 decodes to café, and an emoji such as %F0%9F%98%80 takes four. For plain ASCII text the hex digits are the character code itself (%41 is A), and the ASCII converter lists the hex code for each character you type.
| Encoded | Decoded character | Example |
|---|---|---|
%20 | Space | hello%20world → hello world |
%2F | / | a%2Fb → a/b |
%3A | : | https%3A → https: |
%3F | ? | page%3Fid → page?id |
%3D | = | q%3Dtest → q=test |
%26 | & | a%26b → a&b |
%23 | # | top%23intro → top#intro |
%2B | + | c%2B%2B → c++ |
%25 | % | 100%25 → 100% |
Why a URL Will Not Decode, and Other Gotchas
Invalid encoded URL. The decoder rejects the whole input when it meets a sequence it cannot read: a lone percent sign (as in 100% off), a % that is not followed by two hex digits, a multi-byte character cut short such as %C3 on its own, or bytes that are not valid UTF-8 such as %FF, which usually means the text was encoded as Latin-1 by an older system. A real percent sign has to appear as %25.
Plus signs stay as plus signs. In HTML form submissions a space is often sent as +, but that rule belongs to form encoding, not to URLs in general. decodeURIComponent only turns %20 into a space, so a+b stays a+b. If your string came from a form post, swap each + for a space yourself.
Double encoding. Redirect and tracking links often wrap one encoded URL inside another, so the percent sign itself gets encoded as %25 and a space ends up as %2520. Each pass through the decoder removes one layer; keep pasting the output back in until no %xx sequences remain.
URL Decoding vs Other Encodings
Percent-encoding is not the only way text gets disguised on the web, and decoded output often reveals a second layer. A long run of letters, digits and = padding in a parameter is frequently Base64, which the Base64 decoder can unpack. Login callbacks and API links sometimes carry a token made of three dot-separated parts; paste it into the JWT decoder to read its header and claims.
Sequences like & or ' are HTML entities rather than URL encoding, and they turn up when a link has been copied out of page source; the HTML entity encoder handles those. And when a decoded parameter turns out to be a JSON object, drop it into the JSON formatter to make it readable.
Common uses
- Reading a long redirect, tracking or affiliate link pulled from a log or email
- Inspecting query parameters captured from a browser network tab or server request
- Checking what a UTM or campaign parameter actually contains
- Unwrapping a double-encoded return URL during OAuth or SSO debugging
- Making an encoded link readable before sharing it in a ticket or document
Debugging a request you copied from the browser with Copy as cURL? Once the URL makes sense, the cURL converter turns the command into Python, JavaScript and other languages. For more encoders, formatters and converters, browse all developer tools.
URL encoding terms explained
| Term | What it means here |
|---|---|
| Percent-encoding | Writing a byte as % followed by two hexadecimal digits, so %20 is a space and %2F is a slash; also called URL encoding |
| Reserved characters | Characters with a structural meaning in a URL, such as : / ? # & = and +, which must be encoded when they appear inside a value |
| decodeURIComponent | The JavaScript function this tool uses; it turns every valid %xx sequence back into a character and rebuilds UTF-8 text |
| UTF-8 | The character encoding URLs use for non-ASCII text; one character can take two to four bytes, such as %C3%A9 for é |
| Double encoding | Encoding an already encoded value, so the % itself becomes %25 and %20 turns into %2520 |
| Form encoding | The application/x-www-form-urlencoded format used by HTML form posts, where + stands for a space |
Frequently Asked Questions
Paste the encoded URL or parameter into the Encoded URL box and the decoded text appears instantly in the output panel. Every %xx sequence is turned back into its character, so %20 becomes a space and %3A%2F%2F becomes ://. Click Copy to take the result.
%20 is the percent-encoded form of a space. URLs cannot contain literal spaces, so the space byte (hex 20) is written as %20. Other common ones are %2F for a slash, %3A for a colon, %3F for a question mark, %3D for an equals sign and %26 for an ampersand.
Yes. The decoder converts every valid %xx sequence wherever it sits, so a fully encoded link such as https%3A%2F%2Fexample.com%2Fsearch%3Fq%3Dhello%20world decodes to https://example.com/search?q=hello world in one pass.
The tool uses decodeURIComponent, which only treats %20 as a space and leaves + unchanged. The plus-as-space rule belongs to form-encoded data (application/x-www-form-urlencoded). If your string came from a form post or a query string built that way, replace each + with a space before or after decoding.
decodeURIComponent rejects the whole input when it finds a malformed sequence: a lone % (as in 100% off), a % not followed by two hex digits, a multi-byte character that was cut off such as %C3 on its own, or bytes that are not valid UTF-8 such as %FF. Fix or remove that part and the rest decodes. A literal percent sign must be written as %25.
Double encoding happens when an already encoded value is encoded again, so the % turns into %25 and %20 becomes %2520. One pass through the decoder turns %2520 into %20; paste that result back in and decode again to get the space.
Yes. Percent-encoded UTF-8 is rebuilt into the original characters, so caf%C3%A9 decodes to café and four-byte sequences such as %F0%9F%98%80 decode to an emoji. Text that was encoded in an older single-byte encoding such as Latin-1 is not valid UTF-8 and shows the invalid warning.
No. URL decoding reverses percent-encoding, where each special byte is written as % plus two hex digits. Base64 is a different scheme that packs binary data into letters, digits, + and /. If a decoded value still looks like a long run of letters and digits, it may be Base64 and needs a Base64 decoder.
No. Decoding runs entirely in your browser with JavaScript. The text you paste is not uploaded, stored or logged, which matters when a URL contains tokens, email addresses or session IDs.
Yes. It is free to use with no sign-up and no limit on how many strings you decode.
Reviewed by Raja Jahangir · Last reviewed: October 7, 2026
How do you decode a URL encoded string?
To decode a URL, paste the percent-encoded text and the readable version appears instantly: %20 becomes a space, %3A%2F%2F becomes ://, and %3D becomes an equals sign. Decoding uses the browser's decodeURIComponent, so a broken sequence such as a lone % is flagged as invalid rather than silently mangled, and nothing is sent to a server.
