Search query
hello%20worldhello world
URL Decode
Turn `%20` and `%C3%A9` sequences back into readable characters when inspecting links, logs, or API responses. After decoding a query string, use URL Encode if you need to safely re-encode it.
URL Decode
Decodes percent-encoded text — invalid input shows an error.
URL-encoded string to decode
Human-readable decoded text
Input: 0
Output: 0
Encoded: 0
Spaces: 0
Unicode: 0
URL decoding happens locally in your browser.
How to Use
- Paste a percent-encoded string from a URL bar, log file, or API response.
- View decoded plain text in the output panel — errors appear for invalid sequences.
- Toggle Treat + as space when decoding form-encoded data.
- Copy readable text or pair with URL Encode to re-encode values.
Before and After Examples
Ampersand
a%26ba&b
Unicode
caf%C3%A9café
Plus as space
user+nameuser name
Emoji
Hello%20%F0%9F%98%8AHello 😊
Path
My%20Folder%2FFile.txtMy Folder/File.txt
How URL Decoding Works
Percent sequences
%20 becomes space.
UTF-8 bytes
%C3%A9 becomes é.
Reserved characters
%26 becomes &.
Plus signs
Optional + → space conversion.
Malformed input
Invalid sequences may throw errors.
Double encoding
Some URLs need two decode passes.
Common Uses
Reading query strings
Inspecting API responses
Decoding redirect URLs
Analytics exports
Email subjects
UTM parameters
OAuth callbacks
Log analysis
Invalid or Broken Encoded Text
Valid
hello%20world
Invalid
hello%2
Broken
abc%ZZ
Malformed sequences may cause decoding errors.
Double Encoding
Some systems encode already encoded URLs.
hello%2520world
First pass
hello%20world
Second pass
hello world
Query String Examples
name%3DJohn%26city%3DNew%20Yorkname=John&city=New York
utm_campaign%3Dsummer%2520saleutm_campaign=summer%20sale
Popular Workflows
Real-World Examples
Google query
hello%20worldhello world
API value
New%20YorkNew York
UTM campaign
summer%20salesummer sale
Email subject
Hello%20TeamHello Team
Filename
Report%202026.pdfReport 2026.pdf
Notes & Limitations
- Uses
decodeURIComponentsemantics. - UTF-8 is supported.
- Optional plus-sign conversion.
- Invalid sequences may fail.
- Processing happens locally in your browser.
Frequently Asked Questions
What if decoding fails?
Invalid or incomplete percent sequences trigger an error message. Check for truncated codes like hello%2 or invalid hex like abc%ZZ.
Are plus signs decoded as spaces?
When Treat + as space is enabled, plus signs convert to spaces — common in form-encoded data. Disable it if + should remain literal.
Can I decode an entire URL?
You can paste a full URL or query portion. Decoding works on encoded segments; structure characters like https:// pass through unchanged if not encoded.
Does this support Unicode?
Yes. UTF-8 byte sequences decode to Unicode characters. For example, caf%C3%A9 becomes café.
Can emoji be decoded?
Yes. Emoji encoded as UTF-8 percent sequences decode correctly. For example, Hello%20%F0%9F%98%8A becomes Hello 😊.
What is double encoding?
Double encoding happens when an already encoded string is encoded again. hello%2520world needs two decode passes to reach hello world.
Can malformed text break decoding?
Yes. Incomplete sequences (hello%2) or invalid hex digits (abc%ZZ) cause decodeURIComponent to fail with an error.
Should I decode query parameters only?
Usually yes. Decode individual parameter values or query strings rather than re-processing an entire URL that may contain unencoded structure characters.
Does this upload my text?
No. URL decoding runs entirely in your browser — nothing is sent to a server.
Can I download the result?
Yes. Use Download .txt to save the decoded string as a plain-text file.