Linkding replaces your pinned tabs with an actual bookmark manager

July 2009 — Pinboard launches at $22/year with a promise: no ads, no trackers, no bullshit. December 2020 — Linkding ships v1.0, a single Docker container running SQLite. January 2026 — Linkding reaches v1.45 with 11,000 GitHub stars, six third-party mobile apps, a REST API, and a community that has built tools the solo developer never planned for. Bookmarks have never been easier to self-host. Time to close those 47 tabs you’ve been hoarding “for later” and give them an actual home.

What Linkding does, and what it doesn’t

Linkding is a bookmark manager built to be minimal, fast, and fit inside a single Docker container. It’s not a research tool, an RSS reader, or a read-it-later app with rich parsing like the now-defunct Omnivore. It does one thing: store your links, let you find them fast, and make sure you never lose them.

Under the hood, it’s a Django application backed by SQLite by default — PostgreSQL is supported but entirely optional. The base Docker image weighs under 100 MB, and the official docker-compose.yml fits in 25 lines. No Redis, no message queues: a single process, a single database, and automatic migrations that never break backward compatibility. The maintainer has kept that contract since v1.0 in December 2020.

The release cadence is the most reliable signal of project health. Four releases in 2025 (1.42 in August, 1.43 in September, 1.44 in October, 1.45 in January 2026), each with a detailed changelog. The security vulnerability GHSA-3pf9-5cjv-2w7q patched in December 2025 shipped in v1.44.2 within a week — standard turnaround for a solo-maintained project, and a positive signal.

The feature lineup

Linkding doesn’t try to do everything, but what it does is solid.

• Tags with autocomplete, batch management, and tag cloud since v1.43 (September 2025). A bookmark can carry multiple tags; tags can be renamed or merged in a few clicks.
• Full-text search with logical operators (and, or, not) since v1.44 (October 2025). Type docker and selfhosted and you get exactly those results — not half your library.
• Automatic archiving on the Internet Archive in the background, zero configuration required — just don’t disable LD_DISABLE_BACKGROUND_TASKS. The latest-plus Docker variant adds local HTML snapshots via Chromium, at the cost of a container twice as heavy and higher memory usage per snapshot.
• Keyboard shortcuts for the full navigation flow: n for new bookmark, s to focus search, ? for the full list. You can run your entire session without touching a mouse.
• Dark mode, native, detected automatically from your browser preferences.
• PWA installable on mobile and desktop, with a clean layout and smooth touch navigation.
• Multi-user with bookmark sharing between users or via token-protected public links. v1.45 (January 2026) adds API token management and the option to disable the login form for deployments behind an authentication proxy.
• SSO via OIDC (Authentik, Authelia, Keycloak) or authentication proxy, with automatic account creation on first login.
• Import/export in the Netscape HTML format, the de facto bookmark standard for twenty-five years. You can import a Pinboard, Pocket, Firefox, or Chrome export without any intermediate steps.

The REST API is the real force multiplier. It exposes every endpoint you need — CRUD on bookmarks, search, tag management — and powers a community ecosystem that far exceeds what any solo project could maintain alone.

The community ecosystem

This is the killer argument for Linkding over any closed alternative. A documented REST API has spawned projects covering every imaginable use case.

Mobile apps. Linkdy (Flutter, Android and iOS, on Google Play and the App Store) is the most complete mobile client. LinkBuddy (React Native, both platforms) covers the same ground. Pinkt and Linklater exist as native Android clients, LinkThing on iOS.

Browser integrations. The official extension for Firefox and Chrome adds a toolbar button. For power users, linkding-injector injects Linkding search results into the sidebar of Google and DuckDuckGo — your bookmarks surface alongside web results.

Automation. DingDrop and linkdinger are Telegram bots that save links straight into Linkding. linkding-cli is a command-line interface, aiolinkding an async Python library, linkding-rs a Rust client, go-linkding a Go client. Pocket2Linkding migrates an entire Pocket library without losing dates or tags.

Quality of life. linkding-healthcheck scans your bookmarks and flags dead URLs, linkding-reminder sends email reminders for bookmarks tagged a certain way, linkding-archiver pairs SingleFile with Tube Archivist to archive everything.

No closed service offers this diversity of tools, and none ever will — that’s the definition of the open API advantage.

One Docker command, and you’re done

The official docker-compose.yml is the shortest I’ve seen for an application of this maturity.

version: "3.8"

services:
  linkding:
    container_name: linkding
    image: sissbruecker/linkding:latest
    ports:
      - "9090:9090"
    volumes:
      - ./data:/etc/linkding/data
    environment:
      LD_SUPERUSER_NAME: admin
      LD_SUPERUSER_PASSWORD: ${LD_SUPERUSER_PASSWORD}
    restart: unless-stopped

Create a .env file with LD_SUPERUSER_PASSWORD=<your-password>, run docker compose up -d, then create your first user:

docker compose exec linkding python manage.py createsuperuser \
  --username=joe [email protected]

Three precautions that save hours of troubleshooting. First, never expose port 9090 directly to the internet without a reverse proxy and HTTPS: the admin interface is accessible on first boot, and the login form is the only barrier. Second, the latest-plus image bundles Chromium for local HTML archiving — expect a 400 MB image instead of 100 MB, and an extra 200 MB of RAM at runtime per snapshot. Third, if you’re migrating from Pinboard or Pocket, export to Netscape HTML format first, then import through the admin panel: the Pocket2Linkding tool is more reliable for Pocket, since it preserves original timestamps.

Pinboard vs Linkding: the matchup

The comparison is asymmetric by design — a commercial service maintained by one person for fifteen years against an open-source project maintained by one person for five.

Pinboard costs $22/year for basic access, $39/year with full archiving (page copies, full-text search, dead link detection). Your data lives on Pinboard’s infrastructure, accessible only through Pinboard’s API. The service works, it’s fast, and it’s had no major public security incident since 2009. But you own nothing: if Pinboard shuts down tomorrow, you get a Netscape export and a week to find an alternative.

Linkding costs zero dollars per year in licensing, roughly $10–15/year in electricity for a Raspberry Pi or mini PC. Your data lives on your disk, in an SQLite file you can back up with rsync or rclone. You can read the database directly with any SQLite client. Internet Archive archiving is free and automatic. But you’re responsible for security, updates, and backups.

The real difference isn’t price. It’s control. With Linkding, you can write a script that pulls every bookmark tagged to-read and sends them to your Kindle every Sunday. With Pinboard, you wait for the developer to add the feature — which he probably never will, and that’s his right.

The verdict

If you already have a running server or a Raspberry Pi collecting dust, install Linkding today. The docker compose up -d takes under a minute, importing a Pinboard or Pocket library takes under five, and you’ll have a bookmark manager that beats the pinned-tab graveyard for zero dollars.

If you don’t have self-hosting infrastructure set up and you just want to save links without thinking about maintenance, Pinboard at $22/year remains an excellent option — the service is stable, the developer is responsive, and you never touch a YAML file.

If you’re on the fence, run Linkding alongside Pinboard for a month. Export your existing bookmarks, test the daily workflow (adding, searching, tagging), and decide after thirty days. The worst option is to keep going with 47 tabs “for later” — that’s not a bookmark manager, a reading strategy, or a browsing hygiene practice. It’s just digital hoarding with a browser window.

References

• Linkding — GitHub, sissbruecker, 11,000 stars, MIT license.
• Linkding v1.45.0, GitHub Releases, January 6, 2026.
• Linkding v1.44.0 — New search engine, GitHub Releases, October 5, 2025.
• Linkding v1.43.0 — Tag management, GitHub Releases, September 28, 2025.
• GHSA-3pf9-5cjv-2w7q — Sandbox CSP for viewing assets, GitHub Advisory Database, December 2025.
• Linkding — Installation, official documentation.
• Linkding — Options, official documentation.
• Linkding — Community, community projects.
• Pinboard — Tour, pinboard.in.
• This Week in Self-Hosted (29 December 2023), selfh.st.
• Self-Hosting Guide to Alternatives: Pocket, Omnivore, selfh.st.