Linkding

One-click saving with automatic metadata Browser extensions for Firefox and Chrome, a universal bookmarklet, an installable PWA, and mobile OS sharing capture links anywhere, while titles, descriptions, favicons, and preview images are fetched automatically so saved items keep their context.[1][2]

Tags with namespaces and bulk editing Search-as-you-type tagging, tag clouds, namespaces that group related tags, and bulk editing keep large collections organized without manual per-bookmark housekeeping, while most-used tags and admin duplicate detection surface cleanup work.[1][2]

Full-text search over titles, URLs, and notes An instant full-text search covers bookmark titles, URLs, descriptions, and attached notes, so a half-remembered phrase finds the link.[1]

Markdown notes on bookmarks Private or shared Markdown notes attach context, quotes, or to-dos to any bookmark, with per-tag and per-feed views over annotated items.[1][2]

Read-later list with unread and shared filters A dedicated read-later flag plus unread and shared filters separate the reading queue from the permanent collection and from links shared with other users.[1][2]

Archiving against link rot One-click snapshots store a local HTML copy or push the page to the Internet Archive, the plus-image variant with bundled Chromium captures full website screenshots for readers who need visual copies, and scheduled snapshots keep versioned asset copies over time.[1][2][3]

Import, export, and feeds Netscape HTML import and export moves browser bookmark libraries in and out in a portable format, while per-tag and per-feed RSS views publish saved links to feed readers and aggregators, and read-only feeds let aggregators consume a collection without an account.[1][2]

Multi-user sharing, SSO, API, and notifications Shared bookmarks and multiple user accounts cover families and small teams, OIDC and auth-proxy single sign-on plus an admin panel cover access control, a read-only REST API covers integrations, and notification services announce newly saved bookmarks.[1][2]

Self-hosters wanting the smallest dependable shelf People running a home server or VPS get a single Docker container with an embedded SQLite database, ARM and Raspberry Pi support, and portable single-file backups instead of a multi-service stack.[1][2]

Read-it-later readers who file with tags Readers who save articles for later get a read-later queue, unread filters, Markdown notes, and RSS views, with archiving that keeps the text even when the original page changes.[1][2]

Small teams and families sharing links Households or teams that collect references together get shared bookmarks, multiple accounts, and single sign-on instead of scattered chat messages and docs.[1][2]

Readers who want zero maintenance Anyone unwilling to run Docker, apply updates, and keep backups should use a managed bookmark service, since a self-hosted shelf is only as reliable as its operator.[1]

Collectors wanting full-page preservation or AI organization Readers who expect PDF and screenshot archives of every page or automatic AI tagging will find only HTML snapshots and manual tags here, and should compare Linkwarden or Karakeep instead.[1][2]

Smartphone-first savers expecting a first-party native app The reviewed sources document browser extensions, a bookmarklet, and an installable web app rather than a first-party native mobile app, so users who save mainly from native apps should check the available clients first.[1][2]