URL Opener
Open, check and manage lists of URLs — batch open in tabs or an embedded frame, reachability checks, groups, tags, import/export and monitoring, all in your browser.
Loading tool…
What is a URL opener?
A URL opener takes a list of links and does something useful with all of them at once: opens them in tabs, loads them one at a time in a frame, or pings each one to see whether it still answers. Instead of pasting twenty links into the address bar one by one, you paste the list once and work on it as a set.
The list itself is the point. Once URLs live in a list rather than a chat message or a spreadsheet cell, you can group them, tag them, sort them by response time, strip the tracking parameters off all of them, and export the result as CSV, JSON, XML or a bookmarks file your browser can import.
Why we built this tool — and what a browser can honestly do
QA engineers open the same set of staging pages every morning. Marketers check that a campaign's landing pages are all live before the send goes out. Researchers keep a working set of sources. All three actions are mechanical, and all three are faster when the list is the unit of work rather than the individual link.
One thing deserves to be said plainly, because plenty of tools blur it: a web page cannot read the HTTP status code of another website unless that site opts in with an Access-Control-Allow-Origin header. That is the same-origin policy, and it is a security feature, not a limitation we could code around. So the checker works in two stages. When a site does allow cross-origin reads, you get the real status code, content type, size, and the final URL after redirects. When it does not, the request still tells us whether the server answered at all and how long it took, and the result is honestly labelled as reachable-but-opaque rather than dressed up as a 200.
The same honesty applies elsewhere. SSL certificate details, full redirect chains, and remote page SEO analysis need a server to fetch the page — a browser tab cannot see them. Short codes are stored in this browser only, because a public short link needs a server to resolve it. Scheduled checks run while the tab is open and cannot email you. Everything that can be done locally is: your list, groups, tags, notes and history stay in local storage and are never uploaded.
Tips and common mistakes
- Browsers block popups that are not the direct result of a click. Allow popups for this site before running a large batch, or the first tab opens and the rest are silently swallowed.
- Keep a delay of a second or two between opens. Twenty tabs launched simultaneously will stall a laptop long before the browser refuses them.
- A blank embedded frame almost always means the site sent
X-Frame-Options: DENYor aframe-ancestorspolicy. That is the site refusing to be embedded — nothing about the URL is wrong, so open it in a tab instead. - An "Unreachable" result is not proof a page is down. A firewall, an ad blocker, or a server that rejects cross-origin requests all produce the same network error from a browser. Open the URL to confirm before you report a broken link.
- Strip tracking parameters before you share a list.
utm_*,gclidandfbclidcarry campaign attribution that says more about where you found the link than about the page itself.
Quick start: using URL Opener
- Paste your URLs into the box — one per line, or comma separated — or drop in a TXT, CSV, JSON, XML or browser-bookmarks file.
- Press Add to List. Anything that does not parse is flagged Invalid rather than silently dropped.
- Set how links should open under Opening Options: new tab, new window, a sized popup, or the embedded frame at a phone, tablet or desktop viewport.
- Use Check All to measure which URLs answer and how fast, then sort the list by status or response time.
- Tick the rows you want and use Open Selected, or run the whole list from Batch Open with a delay between opens so the browser keeps up.
- Group and tag what you keep, then export the list as CSV, JSON, XML, Markdown or a bookmarks HTML file.
Because the list, the groups and the history live in your browser's local storage, the tool remembers your working set between sessions and keeps working with no connection — the only network traffic is the requests to the sites themselves when you open or check them.