Free Bookmark Dead Link Checker

A bookmark dead link checker tells you which of your saved links no longer work. This free tool reads your exported bookmarks.html (or Chrome’s Bookmarks file), requests every link, and sorts the results into dead, parked, redirected, needs a look and alive. You can then find archived copies of dead pages and download a cleaned bookmarks file, all without signing up.

The rest of this page explains what the results mean, why one check is never the final word, and how to fix each kind of broken bookmark in Chrome, Edge, Firefox and Safari.

What is a bookmark dead link checker?

A bookmark dead link checker is a tool that takes a list of bookmarks and tests whether each page still loads. It works like a website broken-link crawler, except its input is your personal bookmarks export instead of a site you own.

Under the hood, a dead link checker does the same thing your browser does when you click a link, minus the rendering:

1. It resolves the domain name through DNS. If the domain no longer exists, the bookmark is dead.
2. It connects and asks for the page, first with a lightweight HEAD request and, when a server refuses that, with a normal GET.
3. It follows redirects hop by hop (this checker stops after 10) and records where the link finally lands.
4. It reads the final HTTP status code and, for pages that load, looks for signs of a parked domain.

The checker on this page does steps 1–4 on a server, because a normal web page is not allowed to read responses from other sites (the browser’s cross-origin rules block it). That is why the bookmarks file stays in your tab but the link URLs themselves go to the checking service. Titles, folder names and dates are never sent.

Why check bookmarks for broken links at all?

Because a large share of the web you saved has already moved or vanished. A 2024 Pew Research Center study, When Online Content Disappears, found that 38% of webpages that existed in 2013 were no longer accessible by October 2023, and that 23% of news pages and 21% of government pages contained at least one broken link. It also found that 54% of Wikipedia pages had at least one reference link pointing to a page that no longer existed.

Bookmarks age the same way. A folder of recipes, tutorials or research links you started years ago will have broken links in it, and you usually find out at the worst moment: when you need the page. Running a check lets you find broken bookmarks while there is still time to pull an archived copy, and it clears out clutter that makes search and browsing slower.

How does this free dead link checker work?

This free dead link checker parses your file locally, sends the unique links to the checker in batches of 10, and builds the results table as each batch returns. You can cancel at any point and keep what has finished.

A few details matter for how you use it:

• Accepted files. A bookmarks.html export from any browser (the Netscape bookmark format that Chrome, Edge, Firefox, Safari, Brave and Opera all write), Chrome’s raw Bookmarks JSON file from your profile folder, or a Firefox .json backup.
• Folder filter. The folder menu lists every folder that contains web links, with a count. Checking one folder at a time is the fastest way through a big library.
• Duplicates checked once. If the same URL is saved in three folders, it is requested once and the result is shown on all three rows.
• Non-web entries skipped. javascript: bookmarklets, chrome:// pages, file:// links and Firefox place: queries cannot be checked over the internet and are left alone.
• Worst first. The “All” view sorts dead links to the top, then parked, redirected, needs a look and alive.

Why is each run capped at 2,000 links?

Each link is a real request to somebody else’s server, and the checking service is free and shared. The 2,000-link cap keeps a run to a few minutes, keeps the service inside fair-use limits for everyone, and avoids hammering any one site. If your export is larger, the page tells you how many links were left out; pick a folder and run again. Results from different runs can each be exported as a CSV.

What do the results mean? Status codes explained

Each bookmark gets one of five verdicts. The verdict is built from the HTTP status code, the redirect chain and a few extra signals. Here is how the common responses map to what you see:

The official definitions of these codes are in RFC 9110, HTTP Semantics, and MDN’s HTTP response status codes reference explains each one in plainer language.

Dead

A dead bookmark is one where the page or the whole site is gone: a 404, a 410, a domain that no longer resolves, or a server that refuses connections. These are the bookmarks to recover from an archive or delete.

Parked

A parked bookmark points to a domain that expired and was picked up by a parking service or a domain reseller. The page loads, often with a 200 OK, but shows ads or a “this domain is for sale” message instead of the site you saved. Basic link checkers call these alive because the status code looks healthy. This checker looks for known parking services and for-sale page signatures, and the export options let you treat parked links as dead.

Redirected

A redirected bookmark still works, but the address changed: a site moved from http to https, switched domains, or restructured its URLs. The final URL column shows where the link lands now. Redirects are harmless on their own, but chains break over time, so updating the bookmark to the final URL makes it more durable. One export does that for every redirected link at once.

Needs a look

Needs a look means the checker got an answer it cannot trust either way. A login wall (401), a bot block (403, 429), a server error (5xx), a timeout, or a redirect to the home page all land here. Open these yourself before deciding anything; most will load fine in your browser, and a few will turn out to be soft 404s.

Alive

Alive means the page answered with a success status at the address you saved, or after a redirect that stayed on the same path. It does not guarantee the content is what you remember, only that the address still works.

What are soft 404s and parked domains, and why do they fool link checkers?

Soft 404s and parked domains are broken bookmarks that look healthy to a status-code check. Both return a success response, so a naive dead link checker marks them alive and you keep a link that no longer shows what you saved.

A soft 404 is a missing page that the server does not admit is missing. Google’s documentation on HTTP status codes and network errors describes it as a page that tells users it doesn’t exist while returning a success code. Common forms:

• The server returns 200 OK with a “page not found” message in the body.
• Every missing URL redirects to the home page.
• A retired article redirects to a generic category page.

This checker catches the second form by comparing paths: if a bookmark to /guides/sourdough-starter ends up at /, it is flagged as needs a look with the reason “redirects to the home page”. The first form cannot be detected reliably without reading and understanding the page, so some soft 404s will still show as alive. If a result says alive but you suspect otherwise, click the link.

A parked domain is the other disguise. When a domain registration lapses, it is often bought by a reseller and pointed at a parking page full of ads, or listed on a marketplace. The page loads fine; the site you bookmarked is simply not there. Old bookmarks to personal blogs, small shops and defunct startups are especially likely to end up parked.

Why isn’t one check enough to call a bookmark dead?

One check is a snapshot of a single moment, and the web has bad moments. A site can be down for maintenance, a DNS provider can have an outage, or a server can time out under load. If you delete every link that failed once, you will delete some that would have worked tomorrow.

That is the main limit of any one-shot dead link checker, including this one. Practical ways around it:

• Re-check before you delete. Export the CSV, wait a day or two, and run the check again on the same folder. Links that fail both times are much more likely to be really gone.
• Treat needs a look as unknown, not dead. The export that removes dead links keeps needs-a-look links on purpose.
• Recover before you remove. Look for an archived copy of anything you care about, even if you plan to delete the original.

If you would rather not repeat the check by hand, Bookmend’s link health checks saved links in the background at most once a day and flags the dead ones, so the re-check happens without you. More on that below.

Why do working sites show as blocked? Bot-blocking false positives

Some sites that work perfectly in your browser answer an automated checker with 403 Forbidden, 429 Too Many Requests or a challenge page. This is the most common source of false alarms in any bookmark link checker.

The reasons are defensive rather than broken:

• Bot protection. Services such as Cloudflare, Akamai and others screen traffic and challenge requests that do not look like a real browser running JavaScript. A link checker cannot solve those challenges.
• Rate limits. If many of your bookmarks point to the same site (a forum, a news site, a documentation portal), a burst of requests from one checker can trip a limit and return 429.
• Login walls. Pages behind a login, such as private dashboards, paid articles or intranet tools, return 401 or redirect to a sign-in page for anyone who is not you.
• Regional blocks. A few sites refuse traffic from certain countries or from data centres.

None of these mean the page is gone, so the checker puts them all in needs a look. The fix is simple: filter to needs a look, open the links, and delete only the ones that fail for you too.

How do you fix each type of broken bookmark?

Each result type has a different fix. Dead links get recovered or removed, redirects get updated, parked domains get removed, and needs-a-look links get a manual click. This checker’s export buttons handle the bulk work for you.

Find an archived copy of a dead link

Press Find archived copy next to a dead or parked link. The checker asks the Internet Archive’s Wayback Machine for the snapshot closest to the date the bookmark was added, which is usually the version you meant to save. If a snapshot exists, a direct link appears in the row. Find archived copies for every dead link runs the lookup for all of them at once.

The Wayback Machine does not have everything. Pages behind logins, pages excluded at the owner’s request, and pages nobody ever captured will return “No archived copy found”. For a deeper look at a single URL, including the first and last capture dates, use the free bulk Wayback Machine checker. Our guide to how Bookmend recovers dead bookmarks from the Internet Archive explains how an archived copy is chosen and put back in place of a dead link.

Replace, remove or update in bulk

The three bookmarks.html exports each keep your whole file (every folder, title and date) and change only links that were checked:

• Without dead links removes dead bookmarks (and parked ones, if that box is ticked). “Remove folders left empty” cleans up folders that only held dead links.
• With archive links swaps each recoverable dead link for its Wayback URL and adds [archived] to the title so you can tell them apart. Dead links with no snapshot are left as they were.
• With redirects updated rewrites every redirected bookmark to its final URL.

The CSV report lists every checked bookmark with its folder, verdict, HTTP status, reason, final URL, date added and Wayback link. Open it in Excel, Google Sheets or Numbers to sort and filter, or keep it as a record of what you removed.

Import the cleaned file safely

Importing never deletes anything in Chrome, Edge or Firefox; it adds. That makes it safe, but it also means you end up with two copies until you tidy up. The safe order is:

1. Export a backup of your current bookmarks first and keep it somewhere safe.
2. Import the cleaned file. In Chrome: ⋮ → Bookmarks and lists → Bookmark manager → ⋮ → Import bookmarks (see Google’s help page on importing bookmarks into Chrome). Chrome places the result in a folder called Imported.
3. Compare the Imported folder with the originals, then delete the old folders and drag the imported ones into place.

If Chrome sync is on, the broken bookmarks Chrome copied to your other signed-in devices are cleaned up too once you replace the folders. While you are cleaning, the free duplicate bookmark finder is worth running on the same file, since dead links and duplicates tend to pile up together.

How to find broken bookmarks in Chrome, Edge, Firefox and Safari

No major browser includes a dead link checker. To find broken bookmarks in Chrome or any other browser, you export the bookmarks, check the file, and import the result. The export paths as of September 2026:

Mozilla documents the Firefox steps in Export Firefox bookmarks to an HTML file.

Broken bookmarks in Chrome: using the raw Bookmarks file

Chrome stores bookmarks as a JSON file named Bookmarks in your profile folder. You can drop that file on the checker directly instead of exporting. Copy it first rather than working on the live file:

• Windows: %LOCALAPPDATA%\Google\Chrome\User Data\Default\Bookmarks (other profiles use Profile 1, Profile 2 and so on)
• macOS: ~/Library/Application Support/Google/Chrome/Default/Bookmarks
• Linux: ~/.config/google-chrome/Default/Bookmarks

The checker only reads this file. Exports it creates are standard bookmarks.html files, so use Chrome’s Import command to bring the results back; never paste anything into the profile folder while Chrome is running. For a gentler walkthrough of fixing broken bookmarks in Chrome by hand, see our guide on how to find and fix broken bookmarks in Chrome.

What are the other ways to check bookmarks for dead links?

You can check bookmarks for dead links with an extension, a desktop app, a command-line tool, a one-off web checker like this page, or by hand. Each suits a different situation.

• Bookmend Our product — an AI-native bookmark manager for Chrome and the web. Import your bookmarks.html and its link health feature checks saved links in the background at most once a day, flags dead ones and offers the Wayback Machine copy closest to when the page last worked. Link health is Premium, free during early access.
• This free web checker — best for a one-off audit of an export, for checking Firefox or Safari bookmarks, or when you cannot install anything. It runs once per visit and caps each run at 2,000 links.
• Desktop link checkers — Windows tools such as AM-DeadLink can read browser bookmarks and check them locally. Good for very large libraries if you are comfortable installing software, but they run from your own internet connection, so bot blocking hits them too.
• Command-line tools — open-source checkers such as LinkChecker can crawl a local HTML file, including a bookmarks export. Flexible and scriptable, but you need to be comfortable in a terminal and to interpret raw output yourself.
• Other browser extensions — several extensions in the Chrome Web Store scan bookmarks for broken links. Quality varies, and some older ones stopped working after Chrome’s move to Manifest V3, so check the last-updated date and permissions before installing.
• Manual checking — opening bookmarks one by one works for a folder of 20 links. Chrome’s “Open all” on a folder helps, and a bulk URL opener can open a pasted list in batches. It does not scale past a few dozen.

Where this page is weaker: it is a single snapshot, it cannot see pages behind your logins, and it does not watch your bookmarks over time. Where it is stronger than most: it reports parked domains and soft-404 redirects separately instead of calling them alive, looks up the archived copy closest to your save date, and hands you ready-to-import bookmarks.html files rather than just a list of failures.

Troubleshooting the free bookmark link checker

Most problems come from the file, the network, or sites that block automated checks. Here are the fixes.

If your export is huge and you just want to browse or search it first, the free bookmarks HTML viewer opens it as a searchable folder tree. And if you want a quick picture of your library before checking any links, the free bookmark rot check shows counts, duplicates and your oldest saves without any network requests at all.

When a one-time check isn’t enough: what Bookmend does automatically

A dead link checker on a web page is a one-time audit. Bookmarks keep breaking after you run it, so the next audit will find new dead links. Bookmend, an AI-native bookmark manager for Chrome and the web, does that ongoing job for the bookmarks you keep in it.

Getting your bookmarks in is one step: import the bookmarks.html from Chrome or any other browser (up to 20,000 bookmarks per import, folders included), or the cleaned file this checker gives you. From then on:

• Link health checks saved links in the background, at most once a day per bookmark, and flags the ones that have died.
• Wayback recovery offers the Wayback Machine snapshot closest to when the page last worked as a replacement for a dead link.
• Saved page text means Bookmend keeps the readable text of each page you save, so the content stays available if the site changes.
• Ask your library answers plain-language questions from your saved pages with numbered citations, and search works by meaning, not just titles.

Link health and the AI features are part of Premium, which is free for every new account during early access, with no card needed. The free plan is the bookmark manager itself: saving, collections, tags, search, import and export. Your library lives in your Bookmend account, the same in the Chrome extension (Chrome, Brave, Edge, Arc and Opera; Firefox coming soon) and the web app. See the full list on the features page, or read how Bookmend works.

Written by Nafiul Hasan, Founder, Bookmend. Last updatedSeptember 26, 2026.