linkding vs Linkwarden

Linkding and Linkwarden are two self-hosted bookmark managers that approach the job from opposite ends. linkding is a small Python and Django app whose README promises "minimal, fast, and easy to set up using Docker". Linkwarden is a TypeScript and Next.js app that stores a screenshot, a PDF and an HTML copy of every page, with team collections on top. We rate linkding 1 out of 5 to deploy and Linkwarden 2 out of 5, and the gap in what each one costs to run is bigger than the gap in what they save.

How they differ in practice

linkding gives you tags, search across titles, descriptions, notes and URLs, bulk editing, Markdown notes, a read-it-later flag and a reader mode. Its README lists automatic page archiving as either a local HTML file or a snapshot on the Internet Archive, sharing with other users or guests, import and export in Netscape HTML format, a REST API, SSO via OIDC or an authentication proxy, extensions for Firefox and Chrome, and installation as a PWA. A single container with one volume runs it.

Linkwarden goes further on preservation. Its README lists an automatic screenshot, PDF and single-file HTML copy of every page, a reader view with highlighting and annotation, an optional Wayback Machine snapshot, optional local AI tagging, and collections with sub-collections. For teams it adds per-member permissions, public sharing, API keys and user administration, and it has native iOS and Android apps. RSS feed subscription and image and PDF uploads are listed too.

What it costs to run

linkding's whole install was a single docker run command with one named volume. Idle on our GCP test box it used about 148 MB of RAM and about 566 MB of disk. We estimate a 256 MB minimum.

Linkwarden's official install is a Docker Compose stack of the app, PostgreSQL and Meilisearch, with three generated secrets in an .env file. We estimate a 4 GB minimum, but idle it used about 503 MB of RAM and about 3 GB of disk. Every bookmark carries several stored files, so plan disk around how many pages you will save.

Licence and sign-in

linkding is MIT-licensed. Linkwarden is AGPL-3.0. Both list SSO: linkding through OIDC or an authentication proxy, Linkwarden for self-hosted users.

Our take on the trade-off

If you are the only user and only want to find a link again, most of Linkwarden's weight is something you pay for and never use. The archive copies matter when a page vanishes, and that is the reason to accept the heavier stack. linkding's archive option keeps a local HTML copy, which covers the same failure for text pages without screenshots or PDFs.

Which to choose

Choose linkding if you want the smallest thing that works, one container, a low memory footprint and a plain interface for you and a few other people.

Choose Linkwarden if preserving the page itself matters, you want a reader with highlights and annotations, or you will share curated collections with a team under different permissions.

Related reading

Both are Pocket replacements; the wider field is on our Pocket alternatives page. See how Karakeep stacks up in Karakeep vs linkding and Karakeep vs Linkwarden. The Linkwarden setup is in the deploy guide, and the linkding page is here.