URL Decoder

Welcome to the URL Decoder, a professional-grade tool for decoding percent-encoded URLs and text. Whether you are debugging API requests, analyzing web traffic, inspecting form submissions, or working with internationalized URLs, this decoder provides instant results with deep analysis features that no other tool offers.

What is URL Decoding?

URL decoding (also called percent-decoding) is the process of converting percent-encoded characters back to their original form. When data is included in a URL, certain characters must be represented using a percent sign (%) followed by two hexadecimal digits. URL decoding reverses this process.

For example:

• %20 → space character
• %26 → & (ampersand)
• %3F → ? (question mark)
• %E4%B8%AD → 中 (Chinese character, UTF-8 encoded)

URL encoding is defined in RFC 3986 (Uniform Resource Identifier syntax) and is essential for transmitting data safely in URLs, since many characters have special meaning in the URL syntax.

How to Use This Decoder

1. Paste your encoded text: Enter a URL-encoded string in the input area. It can be a full URL, a query string, a form data payload, or any percent-encoded text. Use the quick examples above the form for common patterns.
2. Choose plus-sign handling: Select whether + should be decoded as a space (standard for HTML form query strings) or kept as a literal plus sign (strict RFC 3986 mode).
3. Get instant results: The live preview shows decoded output in real time as you type. Click "Decode URL" for full analysis including URL component breakdown, multi-layer detection, and encoding statistics.
4. Review the analysis: For full URLs, see the component breakdown (protocol, host, path, query parameters). For multi-layer encoded strings, see each decoding layer visualized step by step.
5. Copy the result: Click the copy button to copy the decoded text to your clipboard.

Feature Highlights

Real-Time Live Decoding

The decoder processes your input directly in your browser using JavaScript. Results appear instantly as you type — no server round-trips needed. Your data never leaves your device, ensuring complete privacy.

URL Component Breakdown

When you decode a full URL, the tool automatically parses it into its components: scheme (protocol), host, port, path, query string, and fragment. Query parameters are displayed in a clean key-value table for easy inspection.

Multi-Layer Decoding

Sometimes URLs get encoded multiple times (double or triple encoding). This happens when encoding functions are applied more than once — for example, %2520 is a double-encoded space (% → %25, then %2520 = %20 = space). Our decoder detects all encoding layers and shows each step.

Encoding Analysis

See exactly which characters were percent-encoded in your input, their hex values, decoded characters, and frequency counts. This is invaluable for debugging encoding issues.

Understanding URL Encoding

Why URL Encoding Exists

URLs can only contain a limited set of ASCII characters. Characters outside this set — including spaces, special symbols, and non-Latin characters — must be percent-encoded to be safely transmitted. The encoding ensures URLs are unambiguous and can be correctly parsed by browsers, servers, and proxies.

Reserved vs Unreserved Characters

Unreserved characters (safe, never need encoding):

• Letters: A-Z, a-z
• Digits: 0-9
• Special: - _ . ~

Reserved characters (have special meaning in URLs, must be encoded when used as data):

• : / ? # [ ] @
• ! $ & ' ( ) * + , ; =

The Plus Sign (+) vs %20 for Spaces

There are two ways spaces appear in URLs:

• + (plus sign): Used in HTML form data (application/x-www-form-urlencoded). When a form submits hello world, it becomes hello+world in the query string.
• %20: The standard percent-encoding for space as defined in RFC 3986. Used in URL paths and other contexts.

When decoding query strings from HTML forms, decode + as space. When decoding URL paths or strict RFC 3986 URIs, keep + as a literal plus sign.

Common Percent-Encoded Characters

What is Double (Multi-Layer) URL Encoding?

Double encoding occurs when an already-encoded string is encoded again. This is a common source of bugs in web applications:

• Original: hello world
• Single encoded: hello%20world (space → %20)
• Double encoded: hello%2520world (% → %25, so %20 → %2520)

This typically happens when:

• An encoding function is called twice by mistake
• URL parameters are encoded before being inserted into an already-encoding-aware context
• Middleware or proxies apply additional encoding

Our multi-layer decoder automatically detects all layers and decodes step by step, showing you exactly what happened.

Common Use Cases

• Debugging API requests: Inspect and decode query parameters from API calls to verify correct values
• Analyzing web traffic: Decode URLs from server logs, analytics reports, or browser developer tools
• Form data inspection: Decode application/x-www-form-urlencoded form submissions
• SEO analysis: Decode URLs containing internationalized content (non-Latin characters) for readability
• Security testing: Detect and decode multi-layer encoded payloads during security audits
• Email and social media links: Decode tracking URLs and redirect chains

Frequently Asked Questions

What is URL decoding?

URL decoding (also called percent-decoding) is the process of converting percent-encoded characters back to their original form. For example, %20 becomes a space, %26 becomes &, and %3D becomes =. This reverses the URL encoding process defined in RFC 3986.

What is the difference between + and %20 for spaces?

Both + and %20 represent a space character, but in different contexts. The + sign is used as a space in HTML form data (application/x-www-form-urlencoded), while %20 is the standard percent-encoding for spaces defined in RFC 3986. When decoding query strings from forms, + should be decoded as space. When decoding URI paths, + should be kept as a literal plus sign.

What is double URL encoding?

Double encoding occurs when an already-encoded string is encoded again. For example, a space becomes %20 after first encoding, then %2520 after second encoding (since % is encoded as %25). This often happens accidentally in web applications when encoding functions are applied multiple times. Our multi-layer decoder detects and resolves all encoding layers.

Is URL decoding done in my browser or on a server?

Our URL decoder performs all decoding directly in your browser using JavaScript. Your data never leaves your device. This ensures complete privacy and instant results without any server round-trips. The server-side form submission is only used as a fallback.

Which characters need URL encoding?

According to RFC 3986, reserved characters (: / ? # [ ] @ ! $ & ' ( ) * + , ; =), spaces, and all non-ASCII characters must be percent-encoded in URLs. Unreserved characters (A-Z, a-z, 0-9, -, _, ., ~) never need encoding.

Additional Resources

• Percent-Encoding - Wikipedia
• URL (Uniform Resource Locator) - Wikipedia