URL Decode Text
Convert URL-encoded text back to a readable string. Decodes %20 to spaces and other symbols.
Settings
Live Statistics
Continue with Related Tools
What is URL Decoding?
URL Decoding (or unescaping) is the reverse process of percent-encoding. It takes a string that has been formatted for safe transmission across the internet—where special characters are replaced by `%` followed by hex digits—and converts it back into its original, human-readable form.
This is commonly used to debug query strings, read parameters from a web address, or decipher messy text that has been "escaped" by a system.
Features
Instant Decoding
Paste any URL or string, and see the clean, unescaped text immediately.
Bulk Decoder
Decode long lists of URLs or log entries at once using the Batch Processing mode.
File Support
Upload a `.log` or `.txt` file containing encoded data and download the clean version.
UTF-8 & Emojis
Robust support for decoding multi-byte characters, emojis, and international scripts.
Query Param Mode
Smartly handles `+` signs from legacy forms, converting them to spaces.
Secure & Private
Decoding happens in your browser. We never see your data, tokens, or private URLs.
How to use
- Input: Paste the text or URL that contains percentage signs (e.g.,
%20). - Check: The tool is already in URL Decode mode.
- Options: Enable "Form Mode" if you want `+` signs to be converted to spaces.
- Result: Copy the clean text or download it as a file.
Example - Convert URL to Text
Frequently Asked Questions
What is URL decoding?
URL decoding is the process of converting percent-encoded characters back into their original form. For example, it turns %20 back into a space and %26 into an & symbol.
How do I use this URL decoder?
Simply paste your encoded string (containing % signs) into the input box. The tool will automatically detect the encoding and display the readable text in the result box.
What does %20 mean in a URL?
%20 represents a space character. Usage of spaces is not allowed in URLs, so when a browser sends a request, it replaces spaces with %20 (ASCII hex 20).
Does this handle '+' signs?
Yes! By enabling 'Form Mode' in the settings, this tool will treat + signs as spaces, which is the standard behavior for application/x-www-form-urlencoded data (often used in query strings).
Can I decode non-English characters?
Absolutely. This tool supports UTF-8 decoding. Percent-encoded sequences representing Emojis (like %F0%9F%98%80) or foreign scripts will be correctly converted back to their visual representation.
What happens if the encoding is broken?
If a string has a malformed sequence (like %2 instead of %20), standard decoders might crash. Our tool attempts to robustly handle the input and will display a clear error message if the specific decodeURIComponent function fails.
Is my data sent to your server?
No. All decoding happens entirely in your browser. We do not transmit or store your URLs, making it safe to decode private tokens, session IDs, or sensitive query parameters.
Can I decode a huge log file?
Yes. Use the 'Batch Mode' toggled in settings. This allows you to paste (or upload) a large list of URLs, and the tool will decode each line individually, which is perfect for processing server logs.
Difference between decodeURI and decodeURIComponent?
Both reverse their respective encoding functions. Generally, decodeURIComponent is more aggressive and will decode special characters like / and ? if they were encoded, whereas decodeURI might leave them. Our tool uses the standard decoding logic consistent with JavaScript.
Why does my result still look weird?
If you decode a string and it still looks encoded (e.g., still has %2520), it might have been double-encoded. You can simply click 'Copy Result', paste it back into the Input, and decode it a second time.