URL Parser & Query String Splitter
Parse any URL into its components and split query strings into key-value pairs. Decode encoded values, sort parameters, and build custom query strings.
Options
URL Insights
URL Components
Query Parameters (0 params)
Query String Builder
Add parameters above to build a query string
What It Does
A URL packs several distinct pieces of information into one string, and this tool pulls them apart so you can see each one on its own. It splits any link into its scheme (http or https), hostname, optional port, path, query string and fragment, then breaks the query string into individual key-value parameters. It also decodes percent-encoded characters — so %20 becomes a space and %40 becomes @ — so the real values are readable instead of hidden behind escape codes. Because parsing happens in your browser using the same URL engine browsers use, what you see matches exactly how a real request would be interpreted. It is the fastest way to confirm where data lives in a link and whether anything is malformed, missing or unexpectedly encoded.
When to Use It
- A tracking or campaign URL has a dozen UTM and ad parameters jammed together and you need to read each key-value pair cleanly instead of squinting at one long string.
- An API request is failing and you want to confirm the path, query parameters and encoding are exactly what you expect before blaming the backend.
- Someone sent you a link with %20, %2F or other percent-encoded characters and you need to see the human-readable values they actually represent.
- You are auditing a link for security and need to spot embedded credentials (user:pass@), a non-standard port, or an http:// scheme that should have been https://.
Worked Examples
https://example.com:8080/path/to/page?name=John%20Doe&age=30&tags=a,b,c#section
A full URL exercising every component. The parser shows the https scheme, a non-default port 8080, three query parameters, a percent-encoded value (%20 decodes to a space in "John Doe"), and a #section fragment that the browser keeps client-side.
http://admin:[email protected]/dashboard?token=abc123
Insecure and risky. The parser flags the http:// scheme (no encryption) and detects embedded user:pass@ credentials baked into the URL — a real-world mistake that leaks passwords into logs, history and referrer headers.
https://shop.example.com/search?q=red%20shoes&filter=size%3A10&sort=price#results
A typical search link. The parser separates the query string (q, filter, sort) from the #results fragment, and reveals that %20 is a space and %3A is a colon once decoding is applied.
Features
How to Use
1. Paste or type a URL in the input field. 2. The URL is parsed in real-time into its components. 3. Toggle options: auto-decode encoded values, show raw values, or sort parameters. 4. Click copy buttons to copy individual parts or the full URL. 5. Use the Query Builder to add parameters and generate a URL. 6. Click Clear to reset.
Common Mistakes
- Confusing the query string with the fragment. Everything after ? is sent to the server; everything after # stays in the browser and is never transmitted. Putting data after # means the server never sees it.
- Reading encoded values as literal text. %20 is a space, %2F is a slash and %26 is an ampersand — treating the raw percent codes as the real value leads to wrong comparisons and broken lookups.
- Forgetting the scheme. A string like example.com/path is not a valid URL on its own; without http:// or https:// the parser (and browsers) cannot resolve it reliably.
- Assuming http and https are interchangeable. http sends everything in clear text, including any credentials or tokens in the URL, while https encrypts the connection. Shipping links over http exposes their contents.
Frequently Asked Questions
All processing happens locally in your browser. No data is sent to any server. Your URLs remain completely private.