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.
Open URL Opener with a link
Assistants and scripts can open URL Opener with its input already in the link, after the #, which never leaves your device:
#text=— the text to work on
Example: https://mygadgets.ink/tools/url-opener/#text=... · also compressed gz fields and ?url=. How tool links work
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.
Start with the list, not the link
Paste your URLs into the URL Opener, one per line or comma separated, and press Add to List. You can also drop in a file: plain text, CSV, JSON, an XML sitemap, or the bookmarks HTML your browser exports.
Once the URLs are a list rather than a blob of text, everything else becomes a bulk operation — select rows, then open, check, tag, group or delete them together.
Opening: tabs, windows, or an embedded frame
Five opening modes cover the usual needs:
- New tab — the default, and the one browsers cooperate with most reliably.
- New window and sized popup — useful for putting a page beside your work at a fixed size.
- Embedded frame — loads the page inside the tool at a phone (320×480), tablet (768×1024), desktop (1200×800) or custom viewport.
- Current tab — navigate away, with a confirmation first.
Two practical notes. Browsers block popups that are not the direct result of a click, so allow popups for the site before running a large batch. And a blank embedded frame is not a bug: most large sites send X-Frame-Options: DENY or a frame-ancestors policy that forbids embedding, and there is no way for a page to override that.
Batch opening without melting the browser
Batch Open adds the controls that make a long list survivable: a delay between opens, a batch size that pauses between chunks, a maximum total, and random or list order. Two seconds between opens and batches of five is a sensible starting point. Twenty tabs opened at once will stall the machine long before the browser refuses them.
Checking: what a browser can and cannot see
This is the part most tools are vague about, so it is worth being exact.
A web page cannot read the HTTP status code of another website unless that site sends an Access-Control-Allow-Origin header allowing it. That is the same-origin policy — a core browser security rule, not something a tool can code around. The consequence is a two-stage check:
- When the site allows cross-origin reads: you get the real status code, content type, content length, whether it redirected, and the final URL.
- When it does not: the request still either completes or fails. A completed request proves the server answered and gives you a response time; the status code stays unreadable. The tool labels this "reachable, opaque" rather than pretending it saw a 200.
The same boundary rules out a few things people reasonably ask for. SSL certificate details, full redirect chains, and SEO analysis of a remote page all require fetching and reading that page, which needs a server. Setting a custom User-Agent or extra request headers is a privileged browser capability that pages do not have.
Read an "Unreachable" result carefully, too. A firewall, an ad blocker, a DNS failure, and a server that simply rejects cross-origin requests all surface as the same network error. Confirm by opening the URL before you report a link as broken.
Keeping the list organised
Groups, tags, categories and notes turn a scratch list into something worth keeping. Categories are guessed from the domain automatically — social, search, developer, news, e-commerce and so on — and you can override any of them. Groups carry a colour and an icon, and a whole group can be opened in one click.
Sorting by status or response time is the fastest way to find what needs attention: the broken and the slow float to the top.
Cleaning URLs before you share them
The normalizer applies the tidying rules you would otherwise do by hand: lowercase the hostname, drop the default port, collapse duplicate slashes, sort query parameters, remove the fragment, force HTTPS, and strip tracking parameters such as utm_source, gclid and fbclid. Preview the changes before applying them to the list.
Stripping tracking parameters matters more than it looks. They describe where you found a link, not what the page is, and they travel with every copy of it you paste to someone else.
Exporting and monitoring
Export as plain text, CSV, JSON, XML, Markdown, a printable report, or a bookmarks HTML file your browser can import directly. Scheduled checks re-run the list on an interval and log every status change, which is useful for watching a deploy — with the honest caveat that it only runs while the tab is open, and cannot email you when something breaks.
Your list, groups, tags and history stay in your browser's local storage. Nothing is uploaded; the only network traffic is the requests to the sites themselves when you open or check them.