URL Decode Text

URL-decode (percent-decode) text to restore original characters.

Input
Loading...
Output
Loading...

Example: Before and After

Before (input)

hello%20world%3F

After (output)

hello world?

Related Tools

HTML Decode Text

Convert HTML entities back to regular text characters.

Text

Encoder / Decoder

Encode or decode text.

Text

Base64 Decoder

Popular

Decode Base64 to text. Example: aGVsbG8= → hello

Text

Hex Decoder

Decode Hexadecimal to text. Example: 68656c6c6f → hello

Text
About This Tool

The URL Decode tool converts percent-encoded text back to its original readable form. It reverses URL encoding by converting sequences like %20 back to spaces and %26 back to ampersands. Use this to read encoded URLs, query strings, or data received from web services.

Common Use Cases
  • Decoding URL parameters for readability
  • Reading encoded text from browser address bars
  • Debugging encoded API responses
  • Converting encoded form data to readable text
  • Analyzing URL query strings
How to Use
  1. Paste the URL-encoded text into the input area
  2. The tool automatically decodes all percent-encoded characters
  3. View the decoded, readable output
  4. Copy the decoded text for your use
Features
  • Decodes all percent-encoded sequences
  • Handles both %20 and + for spaces
  • Supports Unicode and special characters
  • Instant decoding as you paste
Tips

If you see strange characters like %C3%A9 in URLs, they represent UTF-8 encoded characters. This tool will decode them back to their original form (é in this example).

Introduction: Make URLs Readable

The URL Decoder (also called Percent Decoder or URI Decoder) transforms percent-encoded URLs and query strings back into human-readable text by converting encoded sequences like %20, %3D, and %26 into their original characters (space, equals, ampersand). URL encoding is a fundamental web standard that ensures URLs only contain safe, ASCII characters - but it makes URLs difficult for humans to read and understand. This tool instantly reverses that encoding, revealing the actual data being transmitted.

When you see URLs with lots of %XX sequences, question marks, ampersands, and equal signs, you're looking at URL-encoded data. Web browsers, APIs, and web servers use URL encoding to safely transmit special characters, spaces, non-English text, and symbols through HTTP requests. Characters like spaces, quotes, ampersands, slashes, and Unicode characters (accented letters, emoji, non-Latin scripts) must be encoded because they have special meaning in URLs or aren't part of the basic ASCII character set.

For example, a URL parameter containing "hello world" becomes "hello%20world" (with %20 representing the space). A search for "cats & dogs" becomes "cats%20%26%20dogs" (with %26 representing the ampersand). This encoding prevents these characters from being misinterpreted as URL delimiters or breaking the URL structure. The decoder reverses this process, making URLs and query strings readable for debugging, analysis, and understanding.

Who Uses URL Decoders?

Web developers use URL decoders constantly when debugging web applications, analyzing HTTP requests, examining query parameters, or troubleshooting API integrations. When examining browser network traffic or server logs, URLs are encoded, and developers need to decode them to understand the actual data being sent. SEO specialists decode URLs to analyze keyword parameters, tracking parameters, and URL structures for search engine optimization and analytics.

Digital marketers decode tracking URLs from email campaigns, social media ads, or affiliate links to understand UTM parameters and attribution data. Backend developers decode form submissions, API parameters, or webhook payloads that arrive URL-encoded. Security professionals decode URLs to analyze potential XSS attacks, injection attempts, or malicious payloads hidden in encoded parameters. Quality assurance testers decode URLs when verifying application behavior, testing edge cases, or documenting bugs.

How URL Decoding Works

URL encoding represents special characters using a percent sign (%) followed by two hexadecimal digits representing the character's ASCII or UTF-8 code. For example, a space (ASCII 32, hex 20) becomes %20. The decoder scans the text for percent sequences, converts the hex codes back to their character equivalents, and reconstructs the original text. It also handles the + character (an older convention for spaces) and properly decodes multi-byte UTF-8 sequences for international characters.

Think of it like translating numeric codes back to letters - if someone writes "72 101 108 108 111" using ASCII codes, you'd translate it back to "Hello." URL decoding does the same but with hexadecimal percent-encoded sequences instead of decimal numbers.

Example: URL Decoding in Practice

Encoded URL:

https://example.com/search?q=cats%20and%20dogs&category=pets%26animals

Decoded URL:

https://example.com/search?q=cats and dogs&category=pets&animals

Another Example (International Characters):

Encoded: name=Jos%C3%A9%20Mart%C3%ADnez

Decoded: name=José Martínez

The %C3%A9 sequence represents é (Latin small letter e with acute) in UTF-8 encoding.

Common Encoded Characters

  • Space: %20 (or +)
  • Ampersand (&): %26
  • Equals (=): %3D
  • Question mark (?): %3F
  • Hash (#): %23
  • Slash (/): %2F
  • Percent (%): %25
  • Quote ("): %22

When to Use URL Decoding

Use URL decoding whenever you need to understand the actual data in URLs: debugging why a search isn't working (decode the query to see what's actually being searched), analyzing marketing campaign URLs (decode UTM parameters to understand tracking data), reading API error messages (decode error parameters to understand the actual error text), examining browser address bars (decode to see readable page parameters), troubleshooting form submissions (decode POST data to verify correct transmission).

For developers, decoding URLs is essential during debugging sessions, log analysis, API testing, and when documenting application behavior. For non-technical users, it helps understand what data websites are collecting and transmitting through URLs.

Why URL Decoding Matters

Without decoding, URLs in logs, analytics, and browser histories are nearly unreadable. A decoded URL reveals the actual search terms, filter parameters, user input, and data transmission - making debugging exponentially faster. In web development, understanding URL encoding and decoding is fundamental because virtually all HTTP communication involves encoded URLs. The ability to quickly decode enables faster problem-solving, better testing, and clearer documentation.

Frequently Asked Questions

What's the difference between %20 and + for spaces?

Both represent spaces, but %20 is the modern standard, while + is an older convention from form submissions. Good decoders handle both. This tool supports both encoding styles.

Can URL decoding break my URL?

No, decoding doesn't modify the URL - it just shows you what the encoded text means. The decoded result helps you understand the data but isn't meant to be used directly as a URL.

Why do international characters use multiple % sequences?

Characters outside ASCII use UTF-8 encoding with multiple bytes. Each byte becomes a %XX sequence. For example, é is two bytes in UTF-8, so it becomes %C3%A9.

Is URL decoding the same as Base64 decoding?

No, they're different encoding methods. URL encoding uses %XX for special characters. Base64 uses a 64-character alphabet to represent binary data. They serve different purposes.

Can I decode an entire URL at once?

Yes, paste the entire URL and it will decode all percent-encoded sequences. The structure (https://, domain, path, parameters) remains intact while encoded values are decoded.

Why would someone encode a URL twice?

Double encoding happens when already-encoded text gets encoded again. This results in sequences like %2520 (which is an encoded %20). You'll need to decode twice to see the original.

Related Tools