URL-Decoder

Dekodiert Percent-Encoded URLs & Query Strings

URLs can't contain certain characters—spaces, special punctuation, non-ASCII characters. So Browsers and servers percent-encode them: replacing special characters with % followed by their hexadecimal code. A space becomes %20, a slash becomes %2F, and emoji become multi-character sequences. When you copy URLs from Browsers or logs, they often appear heavily encoded and are nearly unreadable. This URL Dekodiertr instantly Transformierts them back to human-readable form.

Drop in an encoded URL or query string and see the original, Dekodiertd version immediately.

What Gets Dekodiertd

Percent-Encoded Characters: Any %XX sequence (where XX is hex) Konvertierts back to its character:

• %20 → space
• %2F → /
• %3A → :
• %26 → &
• And so on for all 256 possible byte values

Unicode Sequences: Multi-byte UTF-8 encoded characters (like emoji or non-ASCII characters) are properly reassembled from their percent-encoded parts.

Preserves Structure: The rest of the URL (scheme, domain, path, fragment) remains intact, so you get a fully readable URL.

Why You Need This

URL Inspection: Browser address bars often show Dekodiertd URLs, but logs, API responses, and HTTP headers show encoded versions. Decoding makes them readable for debugging.

API Debugging: When inspecting API requests and responses, URLs are percent-encoded. Dekodiert them to understand what URLs were being called and what parameters were sent.

Log Analysis: Server logs, Browser console logs, and request logs all contain percent-encoded URLs. Decoding helps you quickly understand which resources were accessed.

Query Parameter Inspection: URL query strings are heavily encoded. Dekodiert the entire URL to see parameter names and values clearly:

• Encoded: https://example.com/search?q=hello%20world&category=tech%2Fai
• Dekodiertd: https://example.com/search?q=hello world&category=tech/ai

Redirect Debugging: When investigating redirects, encoded redirect URLs are hard to read. Dekodiert them to understand where the redirect goes.

Error Reporting

If the URL contains malformed encoding (odd number of hex digits after %, invalid hex characters, etc.), the tool reports the specific error. This helps you identify and fix encoding issues.

Common Debugging Scenarios

Network Tab Inspection: Copy a URL from the Browser DevTools Network tab (which shows encoded URLs) and paste it here to read it clearly.

CI/CD Logs: Deployment logs often contain percent-encoded URLs. Dekodiert them to verify the right resource was accessed.

Email URLs: URLs in emails are sometimes encoded. Dekodiert to verify they're safe before clicking.

Database Content: If URLs are stored in your database, they may be encoded. Dekodiert them for readability and verification.

OAuth & API Flows: Redirect URLs in OAuth flows and API documentation are often percent-encoded. Dekodiert to understand the flow.

One-Click Copy

Dekodiertd output copies to your Zwischenablage with a single click. Paste directly into your Browser, documentation, or testing tools.

100% Local Decoding

Decoding happens entirely in your Browser using standard JavaScript functions. Your URLs never leave your machine, so you can safely Dekodiert URLs containing sensitive inFormatiertion, internal paths, or proprietary data.