Free URL Parser Online
Parse any URL into its components. View protocol, host, pathname, query string and hash. Inspect query parameters in a table.
Key Features
Everything you need to inspect URLs
Splits any URL into all components: protocol, origin, host, hostname, port, pathname, search and hash.
Automatically parses all query string parameters into a clean key-value table for easy reading.
Results update as you type. No button press needed. Uses the browser native URL API for accurate parsing.
Key Takeaways
- Parsing runs entirely in your browser using the native URL constructor, so the URL you paste stays on your device, making it safe for internal, staging, or localhost links.
- You must paste an absolute URL that includes a scheme like https://, because relative paths such as /path?id=1 have no base and will be rejected as invalid.
- Beyond the nine component cards (Full URL, Origin, Protocol, Host, Hostname, Port, Pathname, Search, Hash), a Query Parameters table appears only when a query string is present and lists every key with its decoded value, keeping duplicate keys visible.
- Query values are shown decoded, so percent-encoded characters like %20 become plain text and a plus sign may render as a space; check the raw Search card if you need the encoded form.
How to Parse a URL Into Its Components
Paste an Absolute URL
Drop a full URL that includes a scheme, such as https://example.com/path?id=42#top, into the input field. Parsing happens on your device using the browser native URL constructor, so the value you type stays on your device. Relative paths without a scheme will not parse because the URL API needs a base.
Read the Component Cards
The tool instantly fills nine cards: Full URL, Origin, Protocol, Host, Hostname, Port, Pathname, Search and Hash. Empty parts, such as a missing port or hash, are shown as (empty) so you can tell a blank field from a parsing gap at a glance.
Inspect the Query Parameters
If the URL has a query string, a Query Parameters table lists every key and its decoded value. Percent-encoded characters are unescaped for you, and a key that repeats appears once per occurrence so duplicate parameters stay visible.
What Each URL Component Means
The parser exposes the same properties the browser URL API returns. Knowing what each one holds makes it easier to debug links, redirects and API calls. The table below maps every card to its meaning using the example https://api.example.com:8443/v1/users?role=admin#list.
| Component | Holds | Example Value |
|---|---|---|
| Origin | Scheme, host and port together | https://api.example.com:8443 |
| Protocol | The scheme with a trailing colon | https: |
| Host | Hostname plus port when present | api.example.com:8443 |
| Hostname | Domain only, without the port | api.example.com |
| Pathname | The path after the host | /v1/users |
| Search and Hash | Query string and fragment | ?role=admin and #list |
When This Parser Helps
Debugging Query Strings
When a link carries a long list of tracking or filter parameters, the key-value table separates each one so you can confirm the exact values being sent without counting ampersands by hand.
Checking Encoding
Because values are decoded with the URLSearchParams API, you can paste a percent-encoded URL and immediately read what a parameter such as %20 or %2F actually resolves to.
Verifying Origin and Port
For API and CORS work, the Origin, Hostname and Port cards let you confirm whether a request targets the host and port you expect, including non-default ports like 8443.
Quick Offline Lookups
Since parsing runs in your browser with no upload, you can inspect internal, staging or localhost URLs that you would not want to send to a remote service.
Common Problems and Fixes
It says the URL is invalid
The parser uses the strict browser URL constructor, which rejects anything missing a scheme. Add a prefix such as https:// to the front of the value and try again.
My relative path will not parse
Relative URLs like /path?id=1 need a base URL for context, which this tool does not supply. Prepend a full origin, for example https://example.com/path?id=1, to parse it.
The query table is missing
The Query Parameters table only appears when the URL contains a query string after a question mark. A URL with no parameters shows the component cards only.
A value looks different than I typed
Query values are shown decoded, so percent-encoded characters are converted back to plain text and a plus sign in the query may render as a space. Compare against the raw Search card if you need the encoded form.
About This Tool
This free URL parser breaks down any URL into its individual components using the browser native URL API. Paste or type a URL and instantly see the protocol, host, pathname, search string, hash and all query parameters.
Frequently Asked Questions
Is this tool completely free?
Yes. The tool is 100% free to use with no registration, no subscription and no usage limits.
You can use it as many times as you need for personal or commercial projects without any cost.
We believe developer tools should be accessible to everyone without paywalls.
Is my data private?
Yes. Everything runs locally in your browser using JavaScript. No URLs are transmitted to our servers — nothing leaves your device.
The tool uses the built-in browser URL API which runs entirely client-side.
We do not log or store any input you provide to this tool.
What URL formats are supported?
Any URL with a valid protocol such as https://, http://, ftp:// or custom schemes is supported.
The tool uses the standard browser URL constructor so any URL your browser can parse will work here.
Relative URLs without a protocol are not supported as they require a base URL context.
How are query parameters parsed?
Query parameters are extracted from the search portion of the URL using the browser URLSearchParams API.
Each parameter is displayed as a separate row with its key and decoded value. Percent-encoded characters are automatically decoded.
Parameters with the same key appearing multiple times will each appear as a separate row in the table.
Works in Chrome, Firefox, Safari, Edge, Opera, and other modern browsers on Windows, macOS, Linux, Android, and iOS. No software installation or sign-up required. All conversions run directly in your browser, so your files never leave your device and are never uploaded to a server. Free to use with no account needed.
Sources and References
Format and tool details on this page are based on the official specifications and documentation below.
- RFC 3986: Uniform Resource Identifier (URI)- IETF
- encodeURIComponent()- MDN Web Docs