Linkding vs Linkwarden for Self-Hosted Bookmarks: Fast Links or Full-Page Archives

Browser bookmarks are where good links go to die. They are locked into one browser, impossible to search properly, and when a page disappears from the web, the bookmark becomes a dead end. Self-hosted bookmark managers fix this by keeping your links on your own server, searchable from any device, and two of the most popular are Linkding and Linkwarden.

They look like the same idea, but they answer different questions. Linkding asks: how fast can I save and find a link? Linkwarden asks: what if the page I saved disappears? I run a small homelab and have used both for my research links, reading lists and documentation. Here is how they differ in practice.

Two philosophies of saving a link

Linkding is minimal by design. It stores the link, a title, a description, tags and notes, and gives you a fast, clean list with excellent search. It is a small Python application that typically uses SQLite, so it runs comfortably on a Raspberry Pi or the smallest virtual machine. It can optionally save a snapshot of each page, but the focus is the link itself.

Linkwarden is built around preservation. Every link you save can be archived automatically as a screenshot, a PDF and a cleaned-up readable copy, so you still have the content if the page changes or vanishes. It organises links into collections that can be shared with other people, adds tags, and offers a richer interface. It is a heavier application, built on Node.js with a PostgreSQL database, and it runs a headless browser to capture pages.

Saving links day to day

Both have browser extensions for Chrome and Firefox, and both work with bookmarklets and mobile sharing, so saving a link takes a click or two either way.

Linkding’s extension is quick: it fills in the title and description, suggests tags you have used before, and saves. Its search is the real strength. You can type a few words and filter by tags, and results appear almost instantly, even with thousands of bookmarks. It feels like a tool that gets out of your way.

Linkwarden’s extension saves the link into a collection and kicks off archiving in the background. A few moments later, the link has a preview image and its archived copies. Browsing your library is more visual, with cards and previews, which is pleasant for reading lists and research but slightly slower for pure lookup.

What happens when a page disappears

This is the question that decides between them. Link rot, pages that move, change or vanish, is a constant problem. Studies of web citations regularly find that a sizeable share of links break within a few years, and news articles, documentation and forum posts are especially prone to it.

With Linkwarden, a dead link is not a disaster: you open the saved readable copy, the PDF or the screenshot and still have what you saved it for. For research, recipes, technical guides, receipts and anything you may need years later, that is a big deal.

Linkding can also archive pages, either by saving HTML snapshots locally using a single-file capture or by submitting links to the Internet Archive’s Wayback Machine. The local snapshot option has improved and covers many needs, but Linkwarden’s multiple formats and default-on archiving make preservation its core feature rather than an option.

If your main use is reading articles later rather than keeping them forever, a read-later service may be a better fit than either; that workflow is covered in Readwise Reader vs Instapaper on e-ink.

Organising thousands of links

Linkding is tag-first. Every bookmark can have many tags, and saved searches called bundles let you group links by combinations of tags and terms. It is flexible and fast, but there is no folder-like hierarchy, which some people miss.

Linkwarden uses collections, which work like folders and can be nested, plus tags across them. Collections can be shared with family members or colleagues with view or edit permissions, which makes Linkwarden good for shared research, project link libraries or a household’s recipe and manual collection.

Both import bookmarks from browsers and other services using the standard HTML bookmark export, so moving between them, or moving your browser bookmarks in, is straightforward.

Running it at home

Linkding is one of the lightest self-hosted applications around. A single container with SQLite uses well under 100 MB of memory at idle, backups are just a copy of one database file, and upgrades are rarely eventful. It is a natural first service on a new homelab.

Linkwarden needs more. You run the application alongside a PostgreSQL database, and archiving uses a headless browser, which takes noticeable CPU and memory while capturing each page. Idle use is moderate, often several hundred megabytes, with spikes during archiving. Storage also grows over time: screenshots and PDFs add up, often to a few megabytes per link, so a library of several thousand links can reach many gigabytes. Plan disk space and include the archive folder in your backups, along with the database.

Both run well in Docker, and both are typically put behind a reverse proxy with HTTPS for access from phones and other devices. As with any service holding personal data, avoid exposing them openly to the internet without authentication you trust, and back them up the same way you back up documents. The approach in Paperless-ngx vs Nextcloud for household documents applies here too: keep the database and the stored files together in your backups.

Phones, tablets and integrations

Neither has a perfect mobile experience, but both are usable. Linkding’s web interface works well on phones, and community apps for Android and iOS add native share-sheet saving. Linkwarden offers a responsive web app and has been developing official mobile apps, alongside community options.

Both have APIs, so you can connect automation tools, scripts or other apps. Linkding’s API is simple and well supported by third-party tools, including integrations in some read-later and launcher apps. Linkwarden’s API covers its collections and archives, and it supports RSS feeds for collections and importing from some other services.

Moving ten years of browser bookmarks in

Most people arrive with a messy export: thousands of links in nested folders, many already dead, some duplicated across browsers. How each tool handles that first import shapes the first month.

Export from your browser as an HTML bookmarks file, then import it. Linkding turns your old folder names into tags, which works surprisingly well: a link that sat in “Work / Docker” becomes tagged with both. The import is quick even for large files, because nothing is fetched from the web.

Linkwarden turns folders into collections and, depending on your settings, will try to archive every imported link. With a few thousand old bookmarks, that means hours of headless browser work, a lot of disk space, and many failed captures for pages that no longer exist. It is often better to turn automatic archiving off for the import, then archive only the collections you care about, or let archiving apply to new links from then on.

Whichever you pick, the import is a good moment to clean up:

• Delete the obvious junk first. Old login pages, shopping carts and search results are not worth keeping.
• Check for dead links. Linkding can show which links have archived snapshots, and some community scripts check links in bulk. Linkwarden marks failed archives, which is itself a useful dead-link report.
• Keep tags few and broad. Twenty tags you actually use beat two hundred you will never filter by.

After that, change your browser’s new-tab or toolbar habit so saving goes to the new tool rather than the browser. That habit change, more than any feature, decides whether the setup sticks.

Common reasons people switch

People move from Linkding to Linkwarden when they lose a page that mattered, or when they want to share collections with family or a team. The archive becomes the reason to accept the extra weight.

People move from Linkwarden to Linkding when the archive grows larger than expected, when the server is small, or when they realise they rarely open the saved copies and mostly want quick search. Speed and simplicity win.

Some run both: Linkding for the everyday stream of links, and Linkwarden, or a dedicated archiving tool, for the smaller set of pages worth preserving forever.

A simple way to decide

Ask yourself how often you have gone back to a bookmark and found it broken, and how much that cost you.

If the answer is “rarely, and it didn’t matter much”, choose Linkding. It is fast, tiny, reliable, and its search makes thousands of links easy to find. It is the right choice for developers, quick reference links and anyone on a small server.

If the answer is “often, and it hurt”, choose Linkwarden. It costs more memory and disk space, but you keep the content, not just the address, and shared collections make it useful for families and teams.

Either way, getting links out of a single browser and onto your own server is the real improvement. Both import standard bookmark files, so you can try one for a month and switch without losing anything.