About URL Parser
It parses a URL into its parts in your browser, instantly. You get protocol, hostname, port, full path, query parameters, fragment, origin and any username or password. The tool uses the browser's WHATWG URL parser, the same engine that fetch and links use. All parsing happens client-side in your browser; the page does not upload your input. Query values display decoded text (%20 appears as a space and plus signs stay plus). A bare domain is read as https://example.com by default. Results update as you type; there is no calculate button. You can copy individual fields or share a link that reopens the same parsed text. It preserves repeated query keys as separate entries, matching how servers receive them. It shows the origin including port when present. Once the page is loaded the tool works offline and will parse without a network connection. Developers, QA engineers, marketers and security reviewers use it for debugging, testing redirects and checking query tokens. The tool focuses on faithful browser parsing, instant feedback and local processing.
How to use it
- 1Paste a URL into the input box.
- 2Watch the fields update instantly as you type; there is no calculate button.
- 3Copy any field or the full parsed result.
- 4Share the generated link to reopen the same parsed URL.
Worked example
Input: https://user:[email protected]:8080/path/page.html?q=hello%20world&x=1#section Result: Host name: example.com Protocol: https: Port: 8080 Path: /path/page.html Query parameters: q = "hello world", x = "1" Fragment: section Origin: https://example.com:8080 Username: user Password: pass
How it works
Uses the browser's own URL parser (the WHATWG URL Standard), the same one fetch and links use, so the parts match what browsers seeQuery values are shown decoded (%20 becomes a space, + stays +)An address without a scheme is read as https://Results update instantly as the visitor types; there is no calculate buttonVisitors can copy the result and share a link that reopens with their numbersSource: WHATWG URL StandardMDN Web Docs: URL API. Last checked 7 November 2026.
What it is good for
- Parses using the browser WHATWG URL parser so results match real browsers.
- Runs entirely client-side in your browser; nothing is uploaded while parsing.
- Shows decoded query values, preserves duplicate keys, and offers instant updates and share links.
- Does not compute registrable domain or public suffix; it shows the raw hostname only.
- This tool does not edit or rebuild URLs beyond what the browser serializer provides.
Questions people ask
What parts of a URL does this show?
It shows protocol, hostname, port, path, query parameters, fragment, origin, username and password. The query list shows each key and its decoded value and preserves duplicate keys.
Will my pasted URL be sent to a server?
No. Parsing runs in your browser and FreeToolr does not upload your input. Still, avoid pasting secrets or live tokens into any third-party page if you have doubts.
How are repeated query parameters handled?
The parser preserves repeated keys as separate entries. That matches how browsers and servers typically receive repeated parameters.
Does the tool decode percent-encoding like %20?
Yes. The tool displays decoded query values so %20 appears as a space. Plus signs remain plus signs, which matches the browser URL API behavior.
What if I paste a bare domain like example.com?
A bare address is treated as https:// by default. For example example.com/path parses the same as https://example.com/path in this tool.
Are fragments sent to the server with the request?
No. Fragments are client-side only and are not sent in the HTTP request. The parser still shows the fragment value so you can debug client behavior.
Help keep every tool free
FreeToolr stays free because people help it grow. Share a tool you like, tell us what to build next, or support us on Ko-fi.