URL Inspector & Parser
Parse any URL into its components, decode encoded strings, encode text for safe use in URLs, and inspect query parameters — all instantly in your browser.
🔗 Full URL parsing
Breaks any URL into protocol, host, port, path, query string, and fragment — each shown separately with copy buttons.
🔍 Query param inspector
Every query parameter is listed in a table with its raw and decoded value — no more squinting at long query strings.
🔒 Encode for safety
Percent-encode special characters so your text is safe to use in URLs, API calls, and query strings.
🔓 Decode instantly
Convert percent-encoded strings back to readable text. Great for debugging encoded URLs from logs or API responses.
⚡ Live parsing
Results update as you type — no button press needed. Paste a URL and see all components immediately.
🔒 100% private
Your URLs, tokens, and query strings never leave your browser. Safe to use with internal and production URLs.
How to use the URL Inspector
Anatomy of a URL
A URL (Uniform Resource Locator) has several distinct components that work together to identify a resource on the web. The protocol (http:// or https://) tells the browser how to communicate. The host is the domain name or IP address. The port (usually omitted because it defaults to 80 for HTTP and 443 for HTTPS) specifies which service to connect to. The path identifies the specific resource. Query parameters pass additional data. The fragment (after #) navigates to a specific section of the page.
Query parameters explained
Query parameters are key-value pairs appended to a URL after a question mark. Multiple parameters are separated by ampersands. For example in https://example.com/search?q=developer+tools&page=2&sort=newest there are three parameters: q (the search term), page (pagination), and sort (ordering). The URL Inspector breaks these out into a readable table so you can see exactly what your API is sending or receiving.
URL encoding and percent-encoding
URLs can only contain certain characters. Special characters like spaces, &, =, and # must be percent-encoded to be safe in a URL. A space becomes %20, an ampersand becomes %26, and a hash becomes %23. This is why API responses and log files often contain encoded URLs that look like gibberish. The URL Inspector decodes these automatically so you can read them, and also encodes plain text so you can safely embed it in a URL.
Debugging API URLs from logs
When debugging an API issue, server logs often contain full request URLs that are hard to read at a glance. Pasting the URL into the Inspector immediately breaks out the path, query parameters, and any encoded values into a clean table. This makes it easy to see exactly what parameters were sent with a request and whether they contain the expected values — no manual parsing required.
Common use cases
Developers use the URL Inspector to debug OAuth redirect URIs, inspect webhook callback URLs, verify query parameters in API requests, decode percent-encoded strings from log files, check whether a URL's path and parameters match what an endpoint expects, and safely encode user input before embedding it in a URL. It is particularly useful when working with third-party APIs that return complex redirect URLs with many encoded parameters.