URL Encoder
Escape spaces, symbols and non-ASCII characters for use in URLs.
Encoding & Conversion
Use tool
URL Decoder
Turn percent-encoded text back into something readable.
URL Decoder tool
About the URL Decoder
URL Decoder converts percent escapes back into the characters they represent, turning something like hello%20world%21 into hello world!. It is the quickest way to read an encoded redirect target, a tracking parameter or a log entry without decoding it in your head.
Decoding is UTF-8 aware, so a sequence such as %C3%A9 becomes a single accented letter rather than two broken symbols. Plus signs can optionally be treated as spaces, which is what you need when the string came from an HTML form rather than from a URL path.
Double encoding is common and confusing: a value that was encoded twice shows sequences like %2520 where %25 is itself an encoded percent sign. The tool detects this and offers to decode repeatedly until the text stops changing, so you reach the real value in one step.
How to use the URL Decoder
- Paste the encoded textDrop in the URL or parameter value you want to read.
- Choose how plus signs are handledTreat them as spaces if the value came from a form submission.
- Enable repeat decoding if neededUse it when you see %25 sequences, which signal double encoding.
- Copy the readable resultTake the decoded text with the copy button.
Features
- Correct UTF-8 decoding of multi-byte characters
- Optional plus-sign-as-space handling
- Repeat decoding for double-encoded strings
- Clear error when a percent escape is malformed
- Live result as you type
- Copy in one click
Who uses this tool
The url decoder is used by writers, developers, students, marketers and anyone else who needs the job done once without installing software. Common cases include:
- Reading the real destination of a redirect link
- Understanding tracking parameters in a campaign URL
- Making server log entries readable
- Debugging form submissions that arrive encoded
- Recovering file names with accents from a download link
Frequently asked questions
Why does decoding fail with a malformed sequence error?
A percent sign must be followed by exactly two hexadecimal digits. If the text contains a bare percent sign, or the string was cut off mid-escape, decoding cannot continue. Check that the value was copied in full.
What does it mean when I see %2520 in a URL?
The value was encoded twice. The %25 is an encoded percent sign, so after one pass you get %20 and after a second pass you get a space. Switch on repeat decoding to resolve it in one step.
Should plus signs always become spaces?
Only when the value came from an HTML form, where plus historically means space. In a normal URL path a plus sign is a literal plus, so converting it would corrupt the value. That is why the behaviour is a switch rather than a default.
Can I decode a whole URL at once?
Yes. Decoding a full address is safe and useful for reading it, but remember the decoded version may no longer be a valid URL if it contained encoded separators.
Is anything sent to a server?
No. Decoding uses built-in browser functions inside the page, so tokens and parameters you paste stay on your device.
Does decoding tell me if a link is safe?
It reveals where a link actually points, which helps you spot a disguised destination, but it makes no judgement about whether that destination is trustworthy.
Related tools
If the url decoder is not quite what you need, these other free tools solve closely related problems.
URL Parser
Split a URL into every component, including a table of query parameters.
Developer Tools
Use tool
Base64 Decoder
Decode Base64 back to text, with friendly errors for malformed input.
Encoding & Conversion
Use tool
HTML Encoder & Decoder
Escape angle brackets and quotes to HTML entities, or decode them back.
Encoding & Conversion
Use tool
JSON Formatter
Pretty-print and validate JSON, with the exact line and column of any error.
Developer Tools
Use tool