URL Parser
Break any URL into its protocol, hostname, port, path, query parameters, and hash. Everything runs in your browser with the native WHATWG URL API, so your links stay completely private.
How to Parse a URL
- 1
Paste your URL
Paste or type a complete URL into the input box. The parser reacts as you type, so there is no button to press. Make sure the URL includes a scheme such as https:// — without one, the WHATWG URL API treats the string as invalid and the parser shows an error instead of guessing.
- 2
Review every component
The tool lays out the protocol, username, password, hostname, port, pathname, search string, and hash in a clean list. Below that, a key-value table shows each query parameter individually, with values already percent-decoded for readability.
- 3
Copy or open the result
Click the copy icon beside any field to put it on your clipboard, copy the full URL in one click, or open the URL in a new tab to test it. Nothing leaves your machine during any of these steps.
Why Use a URL Parser?
Accurate Standards-Based Parsing
The parser relies on the browser's built-in URL constructor, which implements the WHATWG URL Standard. That means it handles the same edge cases your application code does, so what you see here matches how the URL behaves in production.
Instant Query Parameter Breakdown
Long query strings packed with tracking and configuration values become a readable table. Each parameter sits on its own row with its decoded value, making it easy to spot duplicates, typos, or unexpected entries.
Completely Private
Because parsing runs entirely on the client, you can safely inspect URLs that contain session tokens, signed parameters, or internal hostnames without worrying that they will be logged or transmitted anywhere.
No Setup, Works Everywhere
There is nothing to install and no account to create. The parser loads in any modern browser on desktop or mobile, which makes it a handy companion when you are debugging away from your usual development machine.
Common Scenarios
Decoding URLs From Crawler and Server Logs
Access logs and crawler exports are full of long, percent-encoded URLs that are hard to read at a glance. Paste one into the parser and the query table shows each parameter with its decoded value, so you can immediately tell which campaign, search term, or referrer triggered a request. This turns a wall of %20 and %3D characters into a clear picture of what a visitor actually requested.
Debugging Third-Party API Callback URLs
OAuth redirects, payment callbacks, and webhook URLs often carry a dozen parameters that must be exactly right. Dropping the callback URL into the parser lets you confirm the redirect_uri, state, and signature parameters are present and correctly encoded before you spend time chasing a bug in your own code.
Auditing Links for Leaked Credentials
Some legacy systems still embed a username and password directly in a URL. The parser surfaces those credentials in a dedicated, maskable field, so during a security review you can quickly scan a batch of links and flag any that expose secrets that ought to live in a header or vault instead.
Tips and Best Practices
Always Include the Scheme
The WHATWG URL API needs an absolute URL with a scheme such as https://. If you only have a path like /products?id=5, prepend a dummy origin such as https://example.com before pasting so the parser can read the query string.
Watch the Decoded Values
The query table shows decoded values, which is great for readability. If a value still contains percent escapes after decoding, that usually means it was double-encoded — a common bug worth fixing at the source.
Compare Hostname Versus Host
The parser shows hostname and port separately. When a URL uses a non-default port, check both fields together so you do not accidentally point a request at the wrong endpoint during testing.
Use It Alongside the Query Editor
Once you understand a URL with the parser, switch to the Query String Editor to actually add, remove, or re-order parameters. The two tools cover inspection and editing respectively.
Compared to Alternatives
Many people reach for an online tool like urlparser.com or a generic "URL components" site when they need to dissect a link. Those services work, but they typically send the URL you paste to their server for processing, which is a problem when the link contains a session token or a signed parameter. URL Shuttle parses everything locally with the same WHATWG URL API your browser already ships, so sensitive URLs never leave the page.
Browser developer tools are another option — you can open the console and run new URL(...) yourself. That is accurate and private, but it requires opening devtools, knowing the API, and reading the result as a raw object. This parser gives you the same standards-compliant result in a labelled, copyable layout with a dedicated query-parameter table, which is faster when you just want to glance at a link.
Command-line approaches such as piping a URL through a script also keep data local, but they are overkill for a one-off inspection and awkward on a machine where you have not set up your tooling. A browser-based parser hits the sweet spot: standards-based accuracy, complete privacy, and zero setup, available on any device with a browser.
Frequently Asked Questions
What is URL parsing?
URL parsing breaks a URL string into its individual parts: the protocol, optional username and password, hostname, port, pathname, query string, and hash fragment. This tool uses the browser's native URL constructor, which follows the WHATWG URL Standard, so the breakdown matches how browsers and servers actually interpret the link.
Which protocols are supported?
Any protocol the WHATWG URL API recognizes will parse, including http, https, ftp, file, and mailto. A bare relative path with no scheme cannot be parsed on its own; prepend an origin such as https://example.com if you only have the path and query portion.
Are query parameter values decoded?
Yes. Parameters are read with URLSearchParams, which percent-decodes values automatically. So %20 appears as a space and %40 as @, giving you the readable value rather than the raw encoded text.
Is my data safe?
Absolutely. The parser runs entirely in your browser and never transmits the URLs you paste. You can inspect links containing tokens or internal hostnames without any privacy concern.
Why does my URL show as invalid?
The most common cause is a missing scheme. URLs like example.com/page are rejected because the standard requires an absolute URL. Add https:// to the front and it will parse correctly.
Can it reveal credentials embedded in a URL?
Yes. If a URL includes a username and password, the parser shows the username and a masked password with a toggle to reveal it. This is handy for spotting credentials that should not be present in a shared link.
Ready to inspect more URLs? Explore the full URL Shuttle toolkit.
Back to URL Shuttle