Runs locally in your browser
URL Decoder
Decode percent-encoded URLs and query strings back to readable text. Invalid sequences are flagged without a network call.
Paste a copied address bar value or a query fragment full of percent signs and recover the original characters. This page only decodes.
decodeURIComponent runs in the browser. Malformed escapes show an error instead of fetching a URL.
How to use
- Paste the encoded string.
- Decode.
- Read the readable text or the error for a broken sequence.
How it works
Percent sequences such as %20 and %C3%A9 become space and é. Plus signs are not turned into spaces here, unlike some form parsers.
A truncated % or a non-hex pair fails. That protects you from silently corrupting a token.
Examples
Query peek
q=caf%C3%A9%20table decodes to q=café table so you can see the real search phrase.
Broken escape
A trailing %3 without a second hex digit raises an invalid encoded URL error.
FAQ
Will plus become a space?
No. Plus stays plus. If your source used plus for spaces, replace plus with %20 first.
Can I decode a slug?
Slugs rarely contain percent sequences. Use this for encoded queries and paths.
Does this fetch the URL?
No. It only transforms the string in this tab.
Is decoding local?
Yes. Nothing is requested from the network.
Related tools
- URL EncoderPercent-encode query values and path segments with encodeURIComponent. Spaces become %20. Encoding stays in your browser.
- Base64 DecoderDecode Base64 back into readable UTF-8 text so you can inspect tokens and payloads. Decoding never leaves this browser tab.
- Slug GeneratorTurn a page title into a URL slug: lowercase, accents stripped, words joined with hyphens. The conversion stays in your browser.
- JSON ValidatorCheck whether JSON is syntactically valid and see the line and column of the first error. Validation stays in your browser.
- Base64 EncoderEncode UTF-8 text to Base64 for data URIs, headers, and embeds. Encoding uses the Web APIs in this tab, with no server hop.