URL Decoder — Decode Percent-Encoded URLs & Query Strings
Turn %20, %3A, %2F and other encoded characters back into readable text, and inspect query parameters.
Quick answer
To decode a URL, paste it into the KaviForge URL Decoder. Percent-encoded sequences like %20, %3A and %2F are converted back to spaces, colons, and slashes instantly. If you paste a full http(s) URL, the tool also shows its host, path, and every query parameter decoded in a table.
Encoded URLs are hard to read: tracking links, OAuth redirects, and API calls are often full of %XX sequences. Decoding reveals the actual values being passed.
This decoder handles UTF-8 multi-byte sequences, can treat + as a space for form-encoded data, and warns you when an input contains malformed percent-encoding.
How to Decode a URL
- 1Paste the encoded URL or text into the input box.
- 2Keep "Treat + as space" on for form data and most query strings.
- 3Read the decoded result in the output box.
- 4For full URLs, review the host, path, and query parameter table below the tool.
- 5Copy individual parameters or the whole decoded output.
Features
Percent Decoding
Decodes %XX sequences including multi-byte UTF-8 characters and emoji.
Query Parameter Table
Breaks full URLs into protocol, host, path, fragment, and each parameter.
Plus as Space
Correctly decodes form-encoded data where spaces are written as +.
Bulk Decoding
Decode a list of encoded values one per line.
Malformed Input Detection
Clear message when % is not followed by valid hex digits.
Private
Everything runs locally — URLs with tokens never leave your browser.
When to Use the URL Decoder
Inspect tracking and UTM links
See the real campaign, source, and destination values hidden in long marketing URLs.
Debug OAuth and redirect URLs
Decode redirect_uri, state, and callback parameters to find mismatches.
Read server logs
Access logs record encoded request paths — decode them to see what users requested.
Double-encoded URLs
Use "Use as input" to decode again when a value was encoded twice (%2520).
About the URL Decoder
The decoder uses decodeURIComponent, which decodes all percent-encoded sequences, including reserved characters. Query parameters are parsed with the browser’s URL API.
Because URLs can contain session tokens and personal data, decoding locally in the browser is safer than pasting them into server-based tools.
URL Decoder FAQs
How do I decode a URL-encoded string?
Paste it into the KaviForge URL Decoder. The readable text appears instantly in the output box.
What does %20 mean in a URL?
%20 is the percent-encoded form of a space. Similarly %2F is /, %3A is :, %3F is ? and %26 is &.
Why are there + signs instead of spaces?
HTML forms encode spaces as +. Keep "Treat + as space" enabled to convert them back to spaces.
How do I decode a double-encoded URL?
If you see %25 sequences (like %2520), decode once, click "Use as input", and decode again.
Why do I get "Malformed URL encoding"?
A % sign is not followed by two hexadecimal digits. The string may be truncated or contain a literal % that was never encoded.
Is it safe to decode URLs containing tokens here?
Yes. Decoding happens in your browser and the URL is never sent to a server.
Related Tools
URL Encoder
Percent-encode text, query strings, and URLs. Choose component or full-URL encoding.
Base64 Decoder
Decode Base64 and Base64URL strings to text, or back to images and files. UTF-8 safe.
JWT Decoder
Decode JSON Web Tokens to read the header, payload, and claims, and check if a token has expired.