Parsing a full URL
Paste https://user:pass@example.com:8080/path/to/page?a=1&b=2#section and click Parse to get protocol https, host example.com, port 8080, path /path/to/page, fragment section, and a table listing a=1 and b=2 as query parameters.
Parse a URL into protocol, host, path and query parameters, or build one — free online.
About
Splits a full URL into its individual parts, and separately builds a URL back up from those same parts.
Developers use it to understand exactly what a long, unfamiliar URL is pointing to, while anyone constructing a redirect or webhook URL uses the builder to assemble it correctly without hand-typing query string encoding. It's one of many free data tools on Toolapt, and like every tool here, it's free to use with no sign-up and no limit on how many times you run it.
Examples
3 worked examples
Paste https://user:pass@example.com:8080/path/to/page?a=1&b=2#section and click Parse to get protocol https, host example.com, port 8080, path /path/to/page, fragment section, and a table listing a=1 and b=2 as query parameters.
Set Protocol to https, Host to example.com, Path to /search, and a query parameter line q=blue shoes, then click Build URL to get https://example.com/search?q=blue%20shoes.
Leave the Port field blank when building a URL for a standard HTTPS site, since the default port doesn't need to appear in the final URL.
FAQ
Quick answers to common questions about the URL Parser and Builder.
It splits a URL into its individual parts, and separately builds a URL back up from those parts.
Yes. It's free, with no sign-up, no watermark and no limit on how many times you use it.
Yes. Parsing and building both happen entirely on your own device using the browser's built-in URL support — nothing you paste is sent to a server.
A complete, valid URL including its protocol, such as https://example.com/path — a bare domain or path without a protocol won't parse.
Enter them as one key=value pair per line in the query parameters box; the builder encodes and joins them into a proper query string automatically.
No. Leave the Port field empty to omit it, which is correct for the vast majority of URLs that use the protocol's default port.
The parser shows whether a username or password is present, but masks the password's actual value rather than displaying it in the clear.
Yes. The page is fully responsive and works on mobile, tablet and desktop browsers alike.
Did URL Parser and Builder work for you?