URL Decoder

Decode Percent-Encoded URLs to Readable Text

Percent-encoded URLs—filled with sequences like `%20`, `%2F`, `%3D`, `%26`, `%C3%A9`—are the normal form that URLs take when they contain spaces, special characters, or non-ASCII text. While this encoding is necessary for correct URL transmission, it makes URLs genuinely difficult to read and analyze. Our free URL decoder reverses the encoding: paste any percent-encoded URL or query string, click Decode, and every `%XX` sequence is converted to the character it represents, producing a clean, readable URL.

The decoder handles standard ASCII percent-encoding as well as multi-byte UTF-8 sequences that represent Unicode characters. An encoded URL containing `%E4%B8%AD%E6%96%87` decodes to the Chinese characters 中文. Emoji encoded as `%F0%9F%98%80` decode to 😀. All standard percent-encoding is decoded correctly regardless of the character set.

Reading Encoded URLs in Practice

Analyzing Tracking and Marketing URLs

URLs with UTM parameters, affiliate tracking codes, and campaign identifiers often contain encoded values that reveal marketing context, campaign names, and audience targeting information. A URL like `?utm_campaign=Black%20Friday%20Sale%202025&utm_source=email&utm_content=header%20CTA` is much more readable after decoding: `?utm_campaign=Black Friday Sale 2025&utm_source=email&utm_content=header CTA`. Decoding UTM parameters is a routine step when auditing marketing campaigns or reconstructing what a shared URL was actually tracking.

Debugging API Requests

HTTP request logs, browser developer tools, and API monitoring dashboards often display request URLs in their encoded form. When debugging why a particular request is producing unexpected results, decoding the URL reveals the actual parameter values that were sent—including special characters, spaces, and international text that might be encoding-related causes of the issue.

Processing Web Scraping Output

URLs extracted from web pages during scraping or crawling often include percent-encoding from the original HTML source. When storing, processing, or displaying these URLs, decoding them produces cleaner data and makes the content easier to work with. Internal links, redirects, and navigation paths all become readable after decoding.

Understanding Error Messages and Server Logs

Web server access logs record the exact URL as received by the server, which is the percent-encoded form. When reviewing logs to understand traffic patterns, investigate errors, or trace specific user sessions, decoding the URL paths and parameters makes the log entries meaningful. A 404 error on `%2Fproducts%2Fcategory%3Fid%3D123%26sort%3Dprice` is immediately understandable as `/products/category?id=123&sort=price` after decoding.

The + Sign in URL Encoding

URL encoding has two slightly different variants with different handling of spaces. In standard percent-encoding (RFC 3986), spaces are encoded as `%20`. In the older HTML form encoding (application/x-www-form-urlencoded), spaces are encoded as `+`. This means a `+` in a query string might represent a literal plus sign or a space, depending on which encoding convention was used.

Most modern URL encoding implementations use `%20` for spaces in query parameters, but older form submissions and some legacy systems still use `+`. If you're decoding a URL that came from an HTML form submission and spaces don't look right in the output, try replacing `+` signs with `%20` before decoding, or use a decoder that explicitly handles both conventions.

Free, Private, and Instant

The URL decoder runs entirely in your browser. No encoded URLs you paste in are transmitted to any server or stored anywhere. The tool is completely free with no account required and works on any device with a modern browser.