By LK Wood IV · 2026-06-28 · ~10 min read · St. Louis County, MO

TL;DR · The one-line call

  • Karakeep (formerly Hoarder) = keep + organize + AI. Bookmark links, notes, images, PDFs, and videos; automatic AI tagging (OpenAI or local Ollama). Pick it to build an organized, searchable knowledge base.
  • Linkwarden = archive + preserve. Auto-saves a PDF and a screenshot of every page, so your bookmarks survive link rot. Pick it to keep a permanent, self-owned copy of what you save.
  • Both are AGPL-3.0, self-hostable with Docker, search via Meilisearch, and ship browser extensions + iOS/Android apps. You can't really go wrong; you're choosing a philosophy, not a winner.

Self-hosted bookmark managers all promise the same thing – “own your bookmarks” – but the two that homelabbers actually shortlist in 2026 are Karakeep and Linkwarden, and they answer a different question underneath. One wants to help you organize what you save. The other wants to guarantee it still exists in five years. That difference should drive your choice more than any feature checklist.

This is a researched comparison drawn from both projects’ documentation, GitHub repositories, and community write-ups, current as of June 2026 – not a paid review and not a claim of a months-long side-by-side deployment. Where a number matters (stars, RAM, services), it’s pulled from the source.

What each one actually is

Karakeep (github.com/karakeep-app/karakeep) is a “bookmark-everything” app: links, notes, images, PDFs, and videos, with AI-based automatic tagging and full-text search as the headline features. It was previously called Hoarder and rebranded to Karakeep. It’s an active, popular project – roughly 26.3k GitHub stars at the time of writing, about two years into development, released under AGPL-3.0.

Linkwarden is a self-hosted bookmark manager whose defining feature is archival: it automatically captures a PDF and a screenshot of every page you save, so the content survives even if the original URL dies. It’s the older of the two – around four years of development versus Karakeep’s two, roughly 18.8k stars, also AGPL-3.0. That ~1.9-year head start shows up as a polished, mature archive view and PWA.

So both are genuinely free, self-hostable, and well-supported. The fork in the road is what they optimize for.

The core difference: organizing vs archiving

This is the whole comparison in one sentence: Karakeep focuses on the keeping and organizing part; Linkwarden focuses heavily on the archiving part. Everything else follows from that.

  • If your problem is “I save hundreds of links and can never find anything,” Karakeep’s AI tagging and broad content support (notes, images, PDFs, video) are aimed straight at you. It behaves more like a personal, searchable knowledge base than a bookmark list.
  • If your problem is “the article I bookmarked last year is now a 404,” Linkwarden’s automatic per-page PDF + screenshot archive is the answer. You’re trading some organizational flash for a durable, self-owned copy of everything.

Plenty of people want both, and either tool will technically do both. But each is clearly better at its half, so match the tool to the problem that actually bothers you.

Which one fits your actual problem
Pick by the pain you have, not the feature list
Choose Karakeepkeep + organize"I save hundreds of links andcan never find anything."Links, notes, images, PDFs, videoAI auto-tagging + full-text searchLocal Ollama option (stays private)Build a searchable knowledge baseorChoose Linkwardenarchive + preserve"The article I bookmarked lastyear is now a 404."Auto PDF + screenshot of every pageSurvives link rot for yearsMore mature project (~4 years)Keep a permanent, self-owned copyBoth: AGPL-3.0, self-hosted with Docker, Meilisearch search, browser + mobile apps.You are choosing a philosophy, not a winner.

Feature comparison

DimensionKarakeep (formerly Hoarder)Linkwarden
Primary focusKeep + organize (knowledge base)Archive + preserve (link rot)
Content typesLinks, notes, images, PDFs, videosLinks (with full-page PDF + screenshot archive)
AI auto-taggingYes – OpenAI or local OllamaLimited / not the focus
Full-page archivalYes (headless Chrome)Yes – the core feature, polished archive view
SearchMeilisearch (local, full-text)Meilisearch (local, full-text)
Apps / extensionsChrome, Firefox, iOS, AndroidBrowser extensions, mobile, polished PWA
LicenseAGPL-3.0AGPL-3.0
Maturity~2 years, ~26.3k stars~4 years, ~18.8k stars (more mature)
Managed cloud optionYes (optional)Yes (optional)

The single most important row is AI auto-tagging with a local-LLM option. If you want hands-off organization without shipping your reading habits to OpenAI, Karakeep’s Ollama support is a real differentiator – you can run the entire tagging pipeline on your own hardware. Linkwarden’s standout row is full-page archival, which it does more maturely than anything else in the category.

Self-hosting footprint (the homelab part)

Neither is a one-container drop-in, so size your box accordingly.

Karakeep runs three services: the main web app, a headless Chrome instance (for archival and screenshots), and Meilisearch for search. In practice the core app sits around ~200MB RAM, Meilisearch ~100MB, and the Chromium crawler can spike to ~500MB while it processes a page – so a typical deployment is comfortable on a 2GB-RAM box, with at least ~1GB free recommended so Meilisearch has breathing room (Karakeep Docker docs).

Linkwarden’s standard Docker Compose brings up the app with PostgreSQL plus Meilisearch. Same ballpark – plan on a couple of gigabytes of RAM and a Docker host you already run.

Either fits fine on a mini PC or a small Proxmox LXC/VM. If you don’t already have a Docker host, our Docker Compose starter stack gets you to a clean base in an afternoon, and the best mini PCs for a homelab covers the hardware to run it on.

Which should you pick?

Choose Karakeep if:

  • You save a mix of things – links, notes, screenshots, PDFs – and want them organized, not just listed.
  • You want automatic tagging and are happy to point it at a local Ollama model to keep everything private.
  • You value faster, nicer first-party apps for day-to-day capture.

Choose Linkwarden if:

  • Your top priority is permanence – a self-owned PDF/screenshot of every page that survives link rot.
  • You want the more mature, battle-tested project with the most polished archive view.
  • You mostly save links (articles, references) rather than mixed media, and “find it later” matters less than “still have it later.”

If you genuinely can’t decide, default to Linkwarden for an archive you’ll trust in five years, or Karakeep for a living, AI-organized knowledge base you’ll actually browse. Both are AGPL-3.0 and Docker-native, so trying one and migrating later is a weekend, not a commitment.

Where these fit in a self-hosted stack

A bookmark manager is one of the highest-value, lowest-effort self-hosted apps you can run – it replaces a SaaS you’d otherwise rent, and your data never leaves your network. For the broader picture of which SaaS tools are genuinely worth self-hosting (and which aren’t), see self-hosted apps that replace SaaS, and if you’re weighing other head-to-head homelab choices, the Komodo vs Portainer vs Dockge breakdown uses the same “match the tool to your actual problem” approach.

One category note before you commit to either: both of these are bookmark managers, built to organize and preserve links at scale. If your real goal is reading — a clean reader view for articles you save on your phone and finish on the couch, the job Pocket did until it shut down — that is a neighbouring category with different tools, compared in self-hosted read-it-later apps.

The honest bottom line: in 2026 these are the two best self-hosted bookmark managers, they share a license and a search engine, and they barely compete on quality – they compete on intent. Decide whether you’re organizing or archiving, and the choice makes itself.

Frequently asked questions

What's the main difference between Karakeep and Linkwarden?
Focus. Karakeep (formerly Hoarder) is built around keeping and organizing a mix of links, notes, images, PDFs, and videos, with AI-based automatic tagging as its headline feature. Linkwarden is built around archiving – it automatically saves a PDF and a screenshot of every page you bookmark, so your saved pages survive even if the original site disappears. Pick Karakeep to organize a knowledge base; pick Linkwarden to preserve pages against link rot.
Are Karakeep and Linkwarden free and open source?
Yes. Both are released under the AGPL-3.0 license and are fully self-hostable with Docker, so you keep your data and there is no per-seat fee for self-hosting. Both also offer paid managed cloud hosting if you would rather not run it yourself, but the self-hosted versions are the full apps.
Which is lighter to self-host?
Both are modest, but neither is a single container. Karakeep runs three services – the web app, a headless Chrome instance for archival/screenshots, and Meilisearch for search – and a typical deployment is comfortable on a 2GB-RAM box (the core app ~200MB, Meilisearch ~100MB, and the Chromium crawler can spike to ~500MB while processing a page). Linkwarden’s Docker Compose uses PostgreSQL plus Meilisearch. Plan on at least 1-2GB of free RAM either way.
Does Karakeep need OpenAI, or can the AI tagging run locally?
It can run locally. Karakeep’s automatic tagging works with OpenAI’s API, but it also supports a local LLM through Ollama, so you can keep the whole pipeline self-hosted with no external API calls or per-token cost. That local-LLM option is one of Karakeep’s bigger draws for a privacy-focused homelab.
Which has the better mobile and browser experience?
Both ship browser extensions (Chrome/Firefox) and mobile apps (iOS/Android) for one-tap saving. Karakeep is generally described as having the faster, nicer apps; Linkwarden is praised for its polished archive view and PWA. For day-to-day capture both are good; the difference shows up in what happens after you save – organizing (Karakeep) vs. archiving (Linkwarden).

Evidence ledger

Last updated
Methodology
This homelab guide was written and edited by Lowell K. Wood IV in St. Louis County, MO. Specs, prices, commands, and version numbers are drawn from the official vendor, reseller, and project documentation current on the date above, and were verified before publishing. First-person hardware claims appear only where the article shows a verifiable artifact — a photo, receipt, or measurement — or links to the TechFuelHQ Open Bench Datasets. Every fact is human-verified against its cited source before publishing; AI assists with first-draft structure and source-gathering, not with the verdict. Full editorial standard: methodology.
Update log
  • 2026-07-25 — Last reviewed and updated.
Corrections
Spotted an error or stale price? Email hello@techfuelhq.com. Confirmed corrections are added to the update log above.

About the author

Written by Lowell K. Wood IV. Lowell builds and runs TechFuelHQ from St. Louis, Missouri, pairing thirteen-plus years of hands-on homelab, PC, server, and networking experience with cited third-party testing and first-party benchmarks on the gear he still runs. He also works ground EMS as a Nationally Registered Paramedic (NREMT).