linkding

TL;DR

• What it is: A minimal, fast, self-hosted bookmark manager built on Django + SQLite, distributed under MIT, shipped as a single Docker image. Clean UI, tags, markdown notes, archiving, browser extensions, REST API.
• Who it’s for: Anyone who saved links in Pocket before Mozilla shut it down in 2025, Pinboard users tired of the closed-source SaaS, Raindrop Pro users who don’t want to pay for bookmarks, and any self-hoster who wants a bookmark manager that starts in one Docker command.
• Cost savings: Raindrop.io Pro is $3/month ($28/year if you pay annually). Pinboard is $22/year + $25/year for archival. Pocket Premium was $45/year before the shutdown. Self-hosted linkding is $0/year for the software plus whatever a small VPS or Raspberry Pi costs.
• Key strength: Ruthlessly simple deployment. Single Docker container, SQLite by default, zero-config bootstrap, browser extensions for Firefox and Chrome, bookmarklet, REST API, SSO via OIDC, PWA. “Simple and reliable bookmark storage without overhead.”
• Key weakness: Minimal by design means no full-content archiving search, no native mobile apps (PWA only), and no nested collections — it’s tag-based, flat, and intentional.

---

What is linkding

linkding is a self-hosted bookmark manager created by Sascha Ißbrücker, licensed MIT, built on Django with a SQLite backend, and packaged as a single Docker container. The name is a play on link + Ding (German for “thing”) — “something for managing your links.” The repository sits at 10,304 GitHub stars with “minimal, fast, and easy to set up” as its core design principle.

What you actually get falls into four buckets. Day-to-day capture covers the things you’ll touch every day — a tag-only flat structure (no folders), bulk edit, Markdown notes on each bookmark, read-it-later marking, and the unread filter. Capture surfaces include browser extensions for Firefox and Chrome, a bookmarklet, and an installable PWA — your three ways to fire a save without leaving the page you’re on. Sharing and access wraps user accounts (single instance, multiple users), public link sharing, OIDC single sign-on or auth-proxy compatibility (Authelia, oauth2-proxy), plus a REST API and an admin panel. Preservation handles the parts that quietly matter long-term: snapshots to local HTML or to the Internet Archive, automatic title/description/icon/preview-image fetching, and Netscape-HTML import/export so you can move in and out without lock-in.

Underneath, linkding is a Django app fronted by uWSGI, with Supervisord coordinating Huey for background work and SQLite (in WAL mode for concurrent reads) for storage. The Docker build is multi-stage to keep the final image lean, and ships in four flavours — Standard or Alpine for the minimal install, plus a “Plus” variant of each that bundles Chromium and Node.js so SingleFile can save full-page HTML snapshots locally instead of relying on the Internet Archive.

The positioning is important: linkding is not trying to be Raindrop, Linkwarden, or Pocket. It’s trying to be the bookmark manager equivalent of a well-designed ls command — fast, minimal, reliable, composable with other tools.

---

Why people choose it over Raindrop, Pocket, Pinboard, Shiori, and Linkwarden

Versus Pocket (RIP 2025)

Pocket shut down in 2025, and that’s why most of the current self-hosted bookmark literature exists. Mozilla pulled the product, and anyone who’d relied on Pocket for read-it-later and bookmark storage needed a new home. Linkding sits in the “simple bookmark replacement” slot, not the full read-later slot. If all you did in Pocket was save links to revisit later and tag them, linkding does that job and does it faster than Pocket ever did. If you relied on Pocket’s full-article extraction and offline reading, linkding isn’t a drop-in — Shiori is closer.

Versus Raindrop.io

Raindrop is the polished, commercial, closed-source competitor. It has nested collections, rich web app, native mobile apps, cross-device sync, a free tier, and a $3/mo Pro tier. It’s genuinely good, and for non-technical users who don’t want to run infrastructure, it’s often the right answer.

linkding’s counter-pitch: $0 instead of $3/mo, MIT licensed, and you own your data. The feature gap is mostly on polish (no nested collections, no native mobile app) rather than fundamentals. For a user who primarily tags and searches bookmarks and occasionally archives a page, linkding feels like 90% of Raindrop at 0% of the cost, with the added benefit that nobody is going to raise the price or shut it down.

Versus Pinboard

Pinboard is the oldest and most opinionated player in this space — minimal, tag-based, no venture funding, no feature bloat. It costs $22/year for the basic tier and $25/year for archival. It’s closed source and single-developer. The migration path from Pinboard to linkding is the open-source, self-hostable version for users who want to own the infrastructure while keeping the same philosophy (minimal + tags + text + speed).

Versus Shiori and Linkwarden

Shiori focuses on content archiving — it fetches the full article text of each bookmark, enables full-text search over archived content, and supports offline reading. Pick Shiori if content archiving and offline reading is the priority.

Linkwarden is the feature-rich option: nested collection organization, link health monitoring, collaboration features, and webhooks. Pick Linkwarden if you’re setting up for a team rather than a solo user, or if you need more than linkding gives you. The practical rule: Linkwarden for teams, linkding for individuals and small groups.

---

Features: what it actually does

Core bookmark management:

• Tag-based organization (flat, no nested collections)
• Full-text search of titles and descriptions (not archived content)
• Bulk editing and bulk operations on selections
• Markdown notes attached to bookmarks
• Read-it-later functionality (mark as unread, filter by read status)
• Share bookmarks with other users or as public guest links
• Import/export in Netscape HTML format

Web metadata and archiving:

• Automatic fetching of titles, descriptions, icons, and preview images
• Local HTML archiving of full pages
• Internet Archive integration — push bookmarks to the Wayback Machine
• Plus variants of the Docker image bundle Chromium + Node.js for SingleFile-based HTML snapshots

Access and integrations:

• Progressive Web App (installable on phones, tablets, desktop)
• Firefox extension
• Chrome extension
• Bookmarklet for browsers without extension support
• REST API for third-party tools and scripts
• SSO via OIDC or authentication proxies (Authelia, oauth2-proxy)
• Admin panel for user self-service and raw data access
• Multi-user with sharing

---

Pricing: SaaS vs self-hosted math

SaaS competitors:

• Pocket: free tier + $44.99/year Premium — SHUT DOWN in 2025
• Raindrop.io: free tier (limited) + $28/year Pro or $3/month
• Pinboard: $22/year basic + $25/year archival add-on ($47/year total)
• Instapaper: $2.99/month = $36/year Premium

Concrete math for an individual:

If you were paying Raindrop.io Pro at $28/year and you’re running a home server or already have a VPS, linkding saves you $28/year forever with no feature you’ll actually miss for personal use. If you’re on a $6/month Hetzner VPS that also runs other self-hosted tools, the incremental cost of adding linkding is essentially zero — it’s a single container on an existing machine.

Hidden benefit: When Mozilla shut down Pocket, anyone who hadn’t exported their data lost it. Self-hosted means the product can’t shut down on you.

---

Deployment reality check

The happy path: A single Podman or Docker compose setup with environment variables for initial credentials, accessible at localhost:9090 after deployment. The bootstrap script handles everything you’d normally do manually: creates required filesystem directories for favicons and previews, generates a unique SECRET_KEY if one doesn’t exist, runs Django database migrations, enables SQLite WAL mode, and creates the initial superuser.

What you actually need:

• A Linux machine with Docker or Podman (Raspberry Pi works fine)
• ~100MB RAM for a personal instance, more for multi-user
• A volume mount for persistent storage (SQLite database + assets)
• A reverse proxy (nginx, Caddy, Traefik) if you want HTTPS and custom domain
• Optional: Chromium-bundled “Plus” image if you want SingleFile-based HTML snapshots
• Optional: OIDC provider if you want SSO

What can go sideways:

• No content archiving for search. Linkding archives pages as HTML and can push to Internet Archive, but you can’t full-text search across archived content the way you can in Shiori.
• No native mobile apps. PWA only. One reviewer worked around this with the HTTP Shortcuts Android app to add bookmarks without logging into the web interface — workable, but not as smooth as Raindrop’s native apps.
• SQLite by default is the right choice for personal and small-team use, but you need to be thoughtful about backups. The built-in full_backup management command makes automation straightforward. Use a bash script + cron + rclone to push the backup off-machine every few hours.
• No nested collections. Tags are the only organization mechanism. This is a design choice, not a missing feature — but if you’re coming from Raindrop or Linkwarden and expecting folder trees, you’ll need to adapt.

Realistic time estimate: 15 minutes for a Docker-literate user on an existing VPS, 1–2 hours for a first-time self-hoster including reverse proxy and HTTPS.

---

Who should use this (and who shouldn’t)

Use linkding if:

• You were a Pocket user looking for a free replacement and you don’t need full-article archiving.
• You were a Pinboard user and you want the same experience but self-hosted and open source.
• You’re a Raindrop.io Pro user and the $28/year feels silly for tag-based bookmarks.
• You already self-host things and linkding slots into your existing Docker setup naturally.
• You want multi-user bookmark sharing inside a small team and SSO via OIDC.
• You want a bookmark manager you can automate via REST API.

Use Shiori instead if:

• You need full-article archiving and offline reading.
• You were heavily dependent on Pocket’s save-for-later + read-later functionality, not just bookmarks.

Use Linkwarden instead if:

• You need nested collections, link health monitoring, webhooks, collaboration.
• You’re setting this up for a team rather than a solo user.

---

Alternatives worth considering

• Shiori — open-source, Go-based, fast, content archiving focus, best Pocket replacement for read-later workflows.
• Linkwarden — open-source, Next.js-based, feature-rich, best for teams and nested collections.
• Raindrop.io — commercial SaaS, polished, native apps, cheap ($3/mo).
• Pinboard — closed-source SaaS, single-developer, minimal, $22/year.
• Wallabag — open-source, PHP-based, read-it-later focus with good content archiving.
• Hoarder — newer open-source bookmark manager with AI-assisted tagging, more features than linkding but younger project.

For someone migrating from Pocket and wanting self-hosted, the realistic shortlist is linkding vs Shiori vs Linkwarden. Linkding wins on minimalism and deployment simplicity. Shiori wins on content archiving. Linkwarden wins on features and team collaboration.

---

Bottom line

linkding is the self-hosted bookmark manager you install once, forget about, and never think about again except when you’re saving a new link. It’s not trying to be Raindrop. It’s not trying to replace your read-later app. It’s trying to be a reliable, fast, private place for your bookmarks, and it nails that job. The post-Pocket-shutdown landscape is full of tools competing on features; linkding competes on “works, stays out of your way, costs nothing” — and for a large chunk of the audience, that’s the winning combination.

If you’d rather not spend an afternoon on Docker + reverse proxy + backup automation just to replace a $3/month bookmark service, that’s exactly what unsubbed.co’s parent studio upready.dev deploys for clients. One-time fee, your data, done.

Sources

This review synthesizes 5 independent third-party articles along with primary sources from the project itself. Inline references throughout the review map to the numbered list below.

1. [1] akashrajpurohit.com (2024-01-16) — “Linkding: Self Hosted Bookmark Manager” (link)
2. [2] linuxlinks.com (2025-05-18) — “linkding: Self-Hosted Bookmark Manager” (link)
3. [3] tabmark.dev (2026-03-17) — “Best Self-Hosted Bookmark Managers in 2026: Shiori, Linkding & Linkwarden” (link)
4. [4] alexn.org (2025-02-14) — “Self-hosted Bookmarks Manager” (link)
5. [5] deepwiki.com (2026-03-19) — “Linkding Docker Deployment Architecture” — technical deep-dive / deployment architecture (link)
6. [6] GitHub repository — official source code, README, releases, and issue tracker (https://github.com/sissbruecker/linkding)
7. [7] Official website — linkding project homepage and docs (https://linkding.link)

References [1]–[7] above were used to cross-check claims about features, pricing, deployment, and limitations in this review.