Link Inspector — URL Parser & Breakdown
Paste any URL to instantly parse and inspect its protocol, domain, path, query parameters, fragment, and more.
How it works
- 1Paste or type any URL into the input field
- 2The URL is parsed instantly in your browser — nothing is sent to a server
- 3View every part of the URL and copy individual fields or the full JSON
What to do next
About Link Inspector
Link Inspector handles a focused step in the modern PDF document workflow workflow. Paste any URL to instantly parse and inspect its protocol, domain, path, query parameters, fragment, and more. The page loads with the upload area, controls and result panel all visible at once, so the path from "I have a file" to "I have the result" is one screen long.
Under the hood, Link Inspector uses standard browser APIs to do the actual work. Input runs through the same engine, with a per-file ceiling of 0 MB so memory usage stays predictable on lower-end laptops and tablets. The engine ships as part of the page bundle, so once the page is loaded the tool keeps working even if your network connection drops.
The right moment to reach for Link Inspector is when you have a focused PDF document workflow job that fits inside a browser tab. Open the page, drop in the file or paste your input, choose the options that matter, and the tool returns the result.
The architecture is local-first by design. Once the page is loaded, you can disconnect from the network and the tool still completes the job. The processing stack — standard browser APIs and the small UI shell wrapping it — ships with the page itself, so the tool keeps working in offline conditions, on a captive-portal Wi-Fi, or behind a corporate proxy that limits what the tab can reach.
The 0 MB ceiling on input size is the only fixed limit. Output files are produced in standard formats that every common viewer recognises, and the tool runs the same way regardless of how many times you have used it during the session.
If your task needs more than one step, chain Link Inspector with PDF Inspector, PDF Page Dimensions, and Meta Tag Analyzer. Each tool produces output that is a clean input to the next, so multi-step workflows are just a matter of opening the next tool in a new tab and continuing.
Link Inspector is shaped around the recurring needs of two audiences: small-business owners sending invoices, who use it as a quick utility between bigger tools, and real-estate agents bundling disclosures, who use it as their primary way of getting the job done. Both groups get the same defaults and the same speed.
Once the engine finishes, the output is offered as an immediate download. There is no preview gate, no email-wall, and no "register to download" intermediary — the file is yours the moment it is ready.
Link Inspector keeps the control set focused. Every option on the page is there because a real workflow needs it, and the defaults aim at the most common case so a first-time user can get the right output without changing any settings.
Link Inspector is structured around the idea that a useful tool should be its own page. Open the page, do the work, close the tab — the page is the entire product. There is no onboarding flow because there is nothing to onboard into.
Pro tip: Link Inspector works just as well in a private/incognito window as in a normal one, which is occasionally useful when you want zero browser-history footprint of the job. Another tip: if the tool ever feels slow, it is almost always because the browser tab is competing for CPU with another tab — pausing or closing the heavy ones gives the engine room to work.
Link Inspector is built around the moment of need: a focused page you open when you have a specific task, complete the task, and close. The catalog contains many adjacent tools so the same model serves the surrounding parts of a typical PDF document workflow workflow.
For most failure modes, refreshing the page and re-running the job is enough — the engine has no persistent state to corrupt. If the same input fails twice in a row, the input itself is most likely the problem (a truncated file, an unexpected variant of the format, or a stream the engine does not recognise).
That is the whole tool. Use Link Inspector for as long as it stays useful to you, and if it does, the catalog has many more tools built the same way. Each applies the same single-purpose discipline, so the way you used this page transfers to the next one you try.
How it works
- 1Land on the Link Inspector page. The tool is ready to use the moment the page renders.
- 2Drop a PDF file onto the upload area, or click to pick one from your device.
- 3Adjust the options to match what you need. Sensible defaults cover the most common case, so you can usually skip this step.
- 4Hit the run button. standard browser APIs does the work in your browser tab.
- 5Save the output when it is ready.
- 6Run additional jobs as needed. The same controls and defaults apply on every run.
Common use cases
- Shrink a scanned report so it fits past an email gateway using Link Inspector.
- Extract a specific signed page from a long contract bundle.
- Strip blank or test pages from a scanned document.
- Reorder pages of a multi-chapter scan into the correct reading order.
- Compress a marketing deck so the email send-out finishes in seconds.
- Split a 200-page exhibit bundle into one PDF per exhibit.
- Combine a CV into a single application packet.
- Convert a bundle of invoices into a single archival PDF.
- Send a polished, print-ready PDF to a client without watermarks.
FAQ
What does this tool extract?
Protocol, domain, subdomain, root domain, TLD, port, path, path segments, query string, each query parameter, fragment, HTTPS status, URL length, and URL encoding.
Does it visit the URL?
No — this is a parser only. It never makes any network request to the URL you enter.
What URL formats work?
Any HTTP, HTTPS, or FTP URL. If you omit the scheme, https:// is assumed.
Private?
Yes — parsing happens entirely in your browser. The URL never leaves your device.
Can I copy individual fields?
Yes — every field has a copy button, and there is a "Copy all as JSON" button at the bottom.
Does it handle encoded URLs?
Yes — percent-encoded URLs are detected and the fully decoded version is shown.
Are there any usage limits on Link Inspector?
Inputs are capped at 0 MB per file, which keeps memory usage stable across phones, tablets and older laptops. You can run Link Inspector as often as you need; every run produces a full-quality result.
Is Link Inspector licensed for business use?
Link Inspector can be used for personal and commercial work alike — there is no separate "business" licence to purchase. The output you generate is yours to use however you want, including in client deliverables, internal documents, or commercial products. Favtoo's only ask is fair, individual use; the tool is not designed to be embedded as a backend service or wrapped behind an API for resale.
Which file formats does Link Inspector accept?
The accepted formats are listed in the upload area on the tool itself. If your input is in a format that is not directly supported, convert it first using one of Favtoo's converter tools — every Favtoo converter outputs a file that is a clean input to the next tool in the chain.
Does Favtoo keep a copy of files I process with Link Inspector?
Favtoo keeps no copy of your file because Favtoo never receives your file. Link Inspector runs entirely in your browser, the input is held only in your tab's memory, and closing the tab discards it. There is no opt-in cloud history, no "recent jobs" panel synced to an account, and no server-side retention to configure — the architecture simply has nowhere for your file to be stored.
Can Link Inspector run inside a corporate firewall?
Link Inspector is a static page running an open-source engine in your browser, so a typical corporate firewall does not get in the way as long as it allows JavaScript to load from Favtoo. For teams that need to host it themselves on an internal network, the underlying engine (standard browser APIs) is open-source and can be packaged into a private build with the same behaviour. Reach out via the Contact page if that is something you are exploring.
Can I use Link Inspector on iOS or Android?
Link Inspector runs in any modern mobile browser — Safari, Chrome, Firefox and the in-app browsers in most messaging apps all support the underlying APIs. Performance depends on the device: a recent phone handles typical inputs nearly as fast as a laptop, while older devices may take a few seconds longer near the 0 MB ceiling. The interface lays out cleanly on small screens, so you do not need to pinch-zoom to see the controls.
Does Link Inspector ask for any browser permissions?
Link Inspector only needs the standard web platform — file picker access for the inputs you choose to load, and optionally clipboard access if you copy the result rather than downloading it. There is no microphone, camera, geolocation or background-permission request, because none of those are needed for the work the tool does.
Is there a programmatic version of Link Inspector?
Link Inspector is a browser-only tool by design and does not expose a hosted API. The reason is the same as the privacy story: there is no Favtoo backend doing the work, so there is no service to call. If you need to script the same transformation, the underlying engine (standard browser APIs) is open-source and can be used directly from your own code.
How accurate is Link Inspector?
Link Inspector is built on standard browser APIs, which is the same class of engine used by professional PDF document workflow pipelines. For deterministic operations, the output is byte-identical to what an equivalent CLI run would produce; for operations involving a codec or a model, the result is well within the range of what comparable tools generate. If you have a specific reference output you need to match, run a small test job first to confirm the configuration produces what you expect.