URL Parser
Break any URL into its parts — scheme, host, port, path, query parameters and fragment.
Paste a URL above — it is split into its parts as you type, right here in your browser.
URL components
- Scheme
- —
- Username
- —
- Password
- —
- Host
- —
- Hostname
- —
- Port
- —
- Origin
- —
- Path
- —
- Query string
- —
- Fragment
- —
- Subdomain
- —
- Root domain
- —
- TLD
- —
Path segments
This URL has no path segments.
Query parameters (0)
| # | Key | Value (decoded) |
|---|
This URL has no query parameters.
How it works
Paste any link and this URL parser breaks it into every part of a URL: the scheme
(protocol), optional username and password, host, hostname, port, origin, path, query
string and fragment (hash). It also splits the hostname into subdomain, root domain and
TLD — including two-level suffixes such as .co.uk — and lists the path
segments so you can see the structure at a glance. Query parameters are shown one per
row with their values percent-decoded, which makes long tracking URLs full of
utm_source and %20 escapes readable again.
Parsing uses the browser's own URL and URLSearchParams APIs, so
the breakdown matches exactly what a browser, fetch() or a server-side URL
library would see. If you leave the scheme off, https:// is assumed and the
page tells you it did that. Copy the whole breakdown as JSON or download it as a
.json file. Everything runs locally in this page — the URL you paste is
never sent anywhere, which matters when the link contains a session token, a signed S3
link or a password reset code.
Frequently asked questions
What are the parts of a URL?
A URL is made of a scheme (https), optional username and password, a host (hostname plus port), a path, a query string after the ? and a fragment after the #. This parser shows every one of them, and additionally splits the hostname into subdomain, root domain and TLD — handling two-level suffixes such as .co.uk correctly.
How do I extract the query parameters from a URL?
Paste the URL and the query parameters appear in a table, one row per key with the value percent-decoded, so %20 shows as a space and encoded JSON or redirect URLs become readable. Repeated keys are listed separately instead of being collapsed, and you can copy the whole breakdown — parameters included — as JSON.
Is it safe to parse a URL that contains a token?
Yes. The parsing runs entirely in your browser with the built-in URL and URLSearchParams APIs, so the link is never uploaded, logged or sent to a server. That matters for signed S3 links, password reset links and OAuth callbacks, where pasting the URL into someone else's website would leak a live credential.