What if I get an error decoding?
This usually means the input contains a malformed percent sequence — a stray % not followed by two valid hex digits.
Developer Tools
Decode a Percent-Encoded URL Component
Decode a percent-encoded value back into readable text, right in your browser.
What this actually reverses
This tool runs decodeURIComponent on your input, converting percent-encoded sequences (like %20 or %3D) back into their original characters. It's the exact reverse of this site's URL Encoder, so a value encoded there decodes back here to the original text precisely.
If the pasted text contains a malformed percent sequence — like a stray % not followed by two valid hex digits — decodeURIComponent will throw an error rather than silently guessing, which this tool surfaces directly rather than papering over.
Workflow at a glance
Use this quick flow to understand where the tool fits in your work and what to review before relying on the output.
Review checklist
Before
Copy the complete encoded string, since a truncated percent sequence will cause a decode error.
After
Check whether the result still contains % sequences, which would mean it needs decoding again.
When you need to decode an encoded value
Use it whenever you have a percent-encoded string — copied from a URL's query string, a log file, or a bug report — and need to read its actual, human-readable content.
Who needs URL decoding
Developers debugging a URL
Decode a query parameter to see the actual value a user or system submitted.
Support engineers
Decode an encoded value from a bug report or log to understand what was actually sent.
Anyone reading a shared link
Decode an encoded parameter to see the readable text it represents.
Students learning about URL encoding
See how percent-encoded sequences map back to their original characters.
What this decoder does
Uses decodeURIComponent
Reverses percent-encoding back into readable characters.
Instant decoding
Output updates as you type or paste.
Surfaces malformed input as an error
A broken percent sequence produces a clear error rather than a silently wrong result.
Runs entirely client-side
Nothing you paste is sent to a server.
Decoding a value step by step
- 1Paste the percent-encoded value you want to decode.
- 2Read the decoded text as it updates automatically.
- 3Check the result for any error indicating a malformed sequence.
- 4Copy the decoded text if you need it elsewhere.
Where this comes up
Decoding a query parameter to see the actual value a user or system submitted.
Decoding an encoded value from a bug report or log to understand what was actually sent.
Decoding an encoded parameter from a shared link to see the readable text.
Seeing how percent-encoded sequences map back to their original characters.
Where your encoded text goes
Decoding happens directly in your browser using decodeURIComponent — nothing you paste is sent to a server.
Reading the result correctly
- Paste the complete encoded string — a truncated percent sequence will cause a decode error.
- If you get an error, check for a stray % character that isn't followed by two valid hex digits.
- Use this alongside URL Encoder to confirm a full round-trip produces the original text.
- Remove any accidental double-encoding first if the decoded result still contains % sequences.
URL decoding mistakes to avoid
Pasting an already-decoded string
Running decodeURIComponent on plain text that has no percent sequences just returns it unchanged, which can look like nothing happened.
Not noticing a malformed sequence error
A stray % not followed by two valid hex digits will throw an error rather than silently decode.
Assuming this decodes a double-encoded value fully
A value encoded twice needs to be decoded twice — running this once may leave % sequences in the result.
Confusing decoded output with the final destination format
The decoded text is the raw value — how it should be interpreted still depends on where it's used.
If decoding produces an error
URL Decoder reliably reverses percent-encoded values back to readable text, and it's upfront about malformed input rather than guessing. If a result still contains % sequences, it likely needs decoding more than once.
Need hands-on help?
Get help with documents, SEO, content, or website fixes
Use this tool for quick work. If you need a real file prepared, a page reviewed, or a website issue fixed, send the URL and describe the problem.
FAQ
URL Decoder FAQ
Answers for using URL Decoder on I Love Tool XYZ.
Can this decode a value that's been encoded twice?
You'll need to run it through the decoder twice — once won't fully reverse double-encoding.
Does plain, unencoded text change when decoded?
No, text with no percent sequences passes through unchanged.
Is my text sent to a server?
No. Decoding happens entirely in your browser.