URL Parser

How URL Parser works

Break any URL into protocol, host, path, query parameters and hash, using the browser parser. Everything happens inside this page: the tool reads your input, runs the calculation or conversion locally, and hands the result back to you. Nothing is transmitted, because there is no backend to transmit it to.

That design choice is deliberate. Most free tool sites upload your files to a server, process them there, and quietly keep a copy. Toolcin cannot do that — the site is a set of static files. If your connection dropped the moment the page finished loading, every tool would still work.

The five parts of a URL

A URL is scheme, host, port, path, query and fragment — and this page labels each one for the URL you paste. For https://example.com/blog/post?id=42&ref=google#comments, the scheme is https, the host example.com, the path /blog/post, the query id=42&ref=google and the fragment #comments.

Seeing them separated is the fastest way to answer “why is my query parameter ignored” — usually because it ended up after the # and is therefore part of the fragment, which never reaches the server.

Parameters, decoded

Query parameters are shown as key–value pairs with their values percent-decoded, so %20 appears as a space. That matters when a value looks empty in a log but is actually a single space.

Repeated keys are kept as separate entries rather than merged, which is how most servers read them.

Where this is used

Debugging a campaign link, checking that a tracking parameter survived a redirect, and confirming which of two similar URLs is canonical. It is also the quickest way to spot a trailing slash difference that creates a duplicate page.

Good to know

• Works offline once loaded, including on flights and in locked-down networks.
• No file size limit beyond your device's own memory.
• Free to use, with no account and no usage counter.
• Results are produced locally, so they are not logged or shared with anyone.

Questions