2026.10.12
linkding: A focused self-hosted bookmark manager
linkding brings bookmark organization, sharing, website archiving, and an API into a service you can host yourself. Before adoption, verify its authentication, browser integrations, and external website access against your environment.
What it is for
linkding is a bookmark manager that can be hosted by its users. The project describes itself as minimal, fast, and easy to set up using Docker. Its scope is centered on links and bookmarks, making it relevant to individuals, households, or small collaborative settings that want to store, organize, and find links in a service they operate.
The project is not presented as a general-purpose documentation collaboration or project-management product. Its focused scope is worth considering when the primary need is bookmark collection, migration, and sharing rather than a broad content-production workflow. Repository metadata identifies linkding as MIT-licensed and not archived.
Known capabilities
Bookmarks can be organized with tags, and the project lists bulk editing, Markdown notes, and read-later functionality. Users can share bookmarks with other users or guests. linkding can also automatically provide titles, descriptions, and icons for bookmarked websites, reducing manual metadata entry.
Archiving is an explicitly listed capability: websites can be archived as local HTML files or on Internet Archive. For migration, linkding supports bookmark import and export in Netscape HTML format. Its interface is installable as a Progressive Web App (PWA), and the project lists Firefox and Chrome extensions alongside a bookmarklet.
For centralized identity, linkding supports SSO through OIDC or authentication proxies. It also provides a REST API for third-party application development, while its admin panel includes user self-service and raw data access. The v1.47.0 release notes list CORS support for the REST API, SSRF protection for server-side requests, scheduling snapshot tasks when pending snapshots exist, and bundling JavaScript and CSS with esbuild.
Limits before adoption
The supplied material does not state minimum hardware requirements, performance benchmarks, collection-size limits, concurrency limits, or a complete production compatibility matrix. It is therefore not possible to assess performance with very large bookmark collections or under high concurrency from these sources alone.
Automatic website metadata retrieval and website archiving involve access to target websites. Local archiving and the Internet Archive path should each be checked in the intended network environment. Although the release notes mention SSRF protection, the supplied material is insufficient to draw a conclusion about the security of an overall deployment. The README mentions community mobile apps, extensions, and libraries, but does not confirm their individual capabilities or compatibility in the provided sources.
Deployment considerations
The official README presents Docker as an accessible setup route and points to self-hosting installation documentation and managed-hosting options. Before adoption, confirm that the required import/export, archiving, PWA, extension, and API workflows fit the intended use.
When using OIDC or an authentication proxy, review the integration against the organization’s own identity system. Development documentation says the application is built with Django and lists Python 3.13, uv, and Node.js as development prerequisites. Those details describe development setup and should not be treated as minimum production deployment requirements.
Sources
Sources checked: 2026-10-12