URL Decoder
Safely decode URL-encoded text online.
Configuration
About URL Decoder
Instantly decode percent-encoded strings and URLs back into readable text. Free, offline-capable developer utility processed securely and locally in your browser.
How to use URL Decoder
- Paste the encoded URL or text into the input field.
- Select 'Decode URI Component' for individual query values, or 'Decode Full URI' for complete URLs.
- Click 'Run Tool' to decode the text.
- Review the decoded output in the results panel.
- Use the Copy button to copy the result to your clipboard.
Best Practices
- Use 'Decode Full URI' when decoding an entire URL so reserved characters like ?, =, and & retain their structure.
- Use 'Decode URI Component' when decoding specific query parameter values that may contain encoded reserved characters.
- If your output still contains % sequences, it may have been double-encoded. You can run the decoder again.
- Remember that spaces are represented by %20 in URLs. Form-urlencoded data (where space is +) requires a different decoding method.
Benefits
- All decoding is performed natively in your browser using JavaScript. No data is sent to our servers.
- Safely decodes percent-encoded UTF-8 sequences for emojis, Arabic, CJK, and other international characters.
- Follows native URI semantics where the plus sign (+) is preserved literally rather than incorrectly converted to a space.
- Performs exactly one decoding pass, preventing double-encoded values from being recursively destroyed.
Common Mistakes to Avoid
- Assuming + means space. In standard URI encoding, a plus sign (+) is a literal plus. It is only interpreted as a space in form-urlencoded query strings.
- Decoding full URIs as components. If you decode a complete URL using Component mode, characters like ? and & will be decoded, which can break the URL structure.
- Ignoring malformed errors. If the decoder throws an error, your input likely contains a broken or incomplete percent sequence (e.g., a standalone % without trailing hex characters).
Frequently Asked Questions
What is URL decoding?
URL decoding (or percent-decoding) is the process of translating percent-encoded character sequences back into their original, readable text form.
What does %20 mean in a URL?
%20 is the standard percent-encoded representation of a space character. When decoded, it becomes a normal space.
Does + mean a space in a URL?
In standard URI encoding, a plus sign (+) is interpreted literally. It is only treated as a space in the specific context of application/x-www-form-urlencoded data, such as HTML form submissions.
What does %2B decode to?
The sequence %2B decodes to a literal plus sign (+).
What is the difference between decodeURI() and decodeURIComponent()?
decodeURI() is intended for full URLs and leaves reserved characters (like ?, &, and =) encoded. decodeURIComponent() decodes everything, making it suitable for individual query parameter values.
Can the URL Decoder handle Unicode characters?
Yes. It accurately decodes valid UTF-8 percent sequences, fully supporting emojis, CJK characters, Arabic, and other international text.
Why won't my encoded URL decode?
If decoding fails with an error, the input likely contains malformed percent sequences or invalid UTF-8 (for example, a lone % sign that is not part of a valid hex code).
Does this tool decode a value more than once?
No. The tool performs a single decoding pass to ensure safety. If your input was double-encoded (e.g., %2520), the result will be the single-encoded version (%20).
Is URL decoding the same as Base64 decoding?
No. URL decoding reverses percent-encoding used for web addresses. Base64 is a different binary-to-text encoding scheme.
When should I use the URL Encoder instead?
Use the URL Encoder when you need to safely prepare text or variables to be inserted into a URL without breaking its structure.
In-Depth Guide Available
Learn how to get the most out of URL Decoder with our step-by-step editorial tutorial.