简体中文
English
Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is linkding?
linkding is a self-hosted bookmark manager built to be minimal, fast and easy to set up. It runs as a single Docker container with SQLite as its database, which keeps maintenance low: migrations are automated and the project describes zero breaking changes. It is aimed at people who want their own bookmark collection rather than a hosted service, and who value a focused, readable interface over a feature-heavy one.
What it does
- Bookmark capture with metadata: it fetches titles, descriptions, icons and preview images from bookmarked sites automatically.
- Archiving: it can save snapshots of bookmarked pages, either as local HTML files or via the Internet Archive.
- Organization and bulk work: metadata and settings aside, you can apply operations to a selection of bookmarks or the entire collection at once.
- Import and export: bookmarks move in and out in the Netscape HTML format, the common bookmark-file standard.
- Multi-user access: several users can be supported, with the option to share bookmarks with other users or guests.
- Browser and script access: Firefox and Chrome extensions let you add and search bookmarks from the browser, and a REST API supports scripts or third-party apps.
Who it suits
A practical case is someone with a few thousand saved links who wants fast search, clean reading, and control over the data. The single-container, SQLite setup means a small home server or VPS is enough, and the import/export path makes it easy to try without committing. The trade-off is that you host and back up the instance yourself, and the deliberately minimal interface may feel thin if you want annotation, collaboration or reading-list workflows built in. For a broader look at self-hosted options, GitHub hosts linkding's source and demo links, and Internet Archive is the service behind its optional snapshot archiving.
As a next step, check whether your existing bookmarks export cleanly to Netscape HTML, then run the demo or a test container and import that file to judge search speed and metadata quality on your own collection before migrating fully.
How do I install and run linkding with Docker?
Run linkding as a single Docker container with a persistent volume for its SQLite database, then open the web UI to create your admin account. The page describes it as “a single Docker container, using SQLite as database,” with automated migrations—so upgrades are mostly a matter of pulling a new image and restarting.
Typical install shape
services:
linkding:
image: sissbruecker/linkding:latest
ports:
- "9090:9090"
volumes:
- ./data:/etc/linkding/data
restart: unless-stopped
Start it with docker compose up -d, then visit http://localhost:9090 (or your server's address on port 9090). Confirm the exact image name, port, and volume path against the project's own documentation before deploying, since those are the details most likely to change.
Practical decisions
- Where data lives: Keep the volume on storage you back up. The database, and any locally archived snapshots, live there.
- Reverse proxy and HTTPS: If you'll reach it from outside your home network, put it behind a proxy with TLS and don't expose the raw port publicly. Multi-user support and guest sharing make this more relevant than for a single-person setup.
- Archiving: The page notes snapshots can be saved as local HTML files or to the Internet Archive. Local archiving grows your volume over time; the Internet Archive option shifts storage elsewhere but depends on an external service.
- Upgrades: Because migrations are automated, a routine pull-and-restart is usually enough—but take a volume backup first, as you would with any SQLite-backed service.
Who this suits
Someone comfortable running a container who wants a focused bookmark manager rather than a full "read-it-later" platform. The feature set is deliberately narrow: metadata fetching, bulk editing, Netscape HTML import/export, browser extensions for Firefox and Chrome, and a REST API for scripts. If you need rich annotation or team collaboration features, that's a different class of tool.
For a concrete next step, compare the setup effort against a hosted alternative if you'd rather not maintain a server—for example linkding for the project itself, or a managed bookmark service. If you already run Docker for other services, adding linkding is a small increment; if this would be your first container, start with the compose file above on a machine you can back up.
How does linkding compare to other self-hosted bookmark managers?
linkding is a deliberately minimal, self-hosted bookmark manager that runs as a single Docker container on SQLite, so it suits people who want a fast personal bookmark tool with little server upkeep rather than a full content-archiving platform. Its main differentiators are simplicity and low maintenance: automated migrations, no breaking changes, and features you can toggle on or off.
Where it fits among self-hosted options
| Need | linkding's approach | Typical alternative |
|---|---|---|
| Quick capture and retrieval | Focused, readable UI; Firefox and Chrome extensions for adding and searching from the browser | Heavier apps with dashboards, tags plus folders, and richer views |
| Keeping page copies | Snapshots as local HTML files or via the Internet Archive | Dedicated read-later or archiving tools with full-text search over saved pages |
| Sharing with others | Multi-user support with bookmark sharing to users or guests | Some single-user tools; others have more granular team permissions |
| Scripting and integrations | REST API for scripts and third-party apps | Varies; API coverage and plugin ecosystems differ widely |
| Setup and upkeep | One Docker container, SQLite, automated migrations | Often Postgres plus multiple services, more configuration |
| Moving data in and out | Netscape HTML import/export | Many tools support this format, so migration is usually straightforward |
The metadata fetching (titles, descriptions, icons, preview images) and bulk editing over selections or the whole collection make it practical for cleaning up a large existing bookmark collection after an import.
Choosing between them
Pick linkding if your priority is a small, dependable instance you can run on modest hardware and rarely touch, and you mainly need fast bookmarking with tags, sharing and an API. Look elsewhere if you need full-text search inside archived pages, collaborative editing with fine-grained roles, or a polished reading experience for saved articles.
A concrete test: import your current bookmarks via Netscape HTML into a trial container, enable archiving, and see whether retrieval and the local snapshot format meet your needs before committing. If you want to compare the project directly, start at linkding and its linked demo and GitHub pages.
Can I import my existing browser bookmarks into linkding?
Yes. linkding imports bookmarks in the Netscape HTML format, which is the standard bookmark export format used by most browsers, so you can move an existing collection in rather than rebuilding it by hand.
How to do it
- In your browser, open the bookmark manager and choose "Export bookmarks" — Chrome, Firefox and Edge all produce an HTML file in Netscape format.
- In linkding, use the import option and select that file.
- Review the result: imported entries bring their URLs and titles, but expect to tidy tags and folders afterward, since browser folder structures don't map cleanly onto linkding's tagging.
What to expect
The same format works in reverse — linkding exports in Netscape HTML, so you can move bookmarks back out or into another tool later. Once imported, linkding's metadata feature fetches titles, descriptions, icons and preview images automatically, which fills in gaps that browser exports often leave blank.
Practical notes
- Duplicates: if you import the same file twice, check for repeated entries rather than assuming linkding deduplicates for you. Cleaning up first in the browser is easier.
- Large collections: importing a few thousand bookmarks is fine, but bulk editing is the tool to lean on afterward — it applies operations to a selection or the whole collection, useful for adding or removing tags en masse.
- Whose setup this suits: someone running their own instance via Docker who wants a fast, distraction-free archive they control. The trade-off is that you handle hosting and backups yourself; the payoff is no third-party service holding your bookmarks.
For setup details and the exact import steps for your version, see linkding.
How does linkding handle multiple users and bookmark sharing?
linkding supports multiple user accounts on a single instance. Each person gets their own bookmarks, and the sharing feature lets users make bookmarks visible to other users or to guests, so a household, team, or small group can run one instance without everyone mixing their private collections. Because it runs as a single Docker container with SQLite, you set up accounts within your own deployment rather than through a hosted service.
How sharing fits real use
- Household or small team: one person runs the instance; others get accounts and share only the links meant for the group (references, internal docs, reading lists), keeping personal bookmarks private.
- Guest access: shared bookmarks can be exposed to guests, which suits a public or semi-public link list without giving full accounts.
- Shared collections: because sharing is per bookmark, curating a group reading list is a matter of sharing those items rather than maintaining a separate account.
Trade-offs to weigh
- Shared SQLite instance: simple to run, but all users depend on the same container and database; there is no per-user isolation at the infrastructure level.
- Sharing granularity: sharing is at the bookmark level, so large, fast-changing group libraries may call for consistent tagging conventions among users.
- Self-hosting duty: you handle backups, updates, and access, though automated migrations and a low-maintenance setup reduce that burden.
Next step
Decide who needs full accounts versus guest visibility, then agree on a shared tagging scheme (for example a team tag) so shared bookmarks stay easy to find. If you want to compare approaches, wallabag and Raindrop.io handle multi-user and sharing differently and are worth a look before committing.
What can I do with the linkding REST API?
The linkding REST API lets you work with your bookmarks programmatically rather than through the web interface. Since linkding is a self-hosted bookmark manager, the API is aimed at people running their own instance who want to script, automate or integrate bookmark handling.
Practical uses
- Automating bookmark creation. You can add bookmarks from scripts, command-line tools or other apps, which is useful for capturing links from a workflow without opening a browser.
- Building your own tools. Because the API is intended for scripts and third-party apps, you can build a custom front end, a mobile client or a dashboard that reads and writes your bookmark collection.
- Bulk operations. linkding already supports bulk editing in its interface; an API lets you script similar large-scale changes, such as tagging or reorganizing many bookmarks at once.
- Integration with other services. You could wire bookmark creation into a read-later pipeline, a note-taking tool or an RSS-style workflow, so links you collect elsewhere land in linkding.
Who benefits most
The API is most valuable to individuals or small teams who already self-host linkding and are comfortable writing small scripts. If you only add bookmarks occasionally through the browser extension, the API adds little. If you want linkding to be one component in a larger personal system, it becomes genuinely useful.
A concrete next step
Decide what you want to automate first—for example, "save every link I post in a chat channel" or "export my bookmarks to another tool on a schedule." Then check the API documentation on the project's GitHub repository to confirm which endpoints cover that operation before writing code. The official project pages are linkding and its GitHub repository, which the site links to for setup and API details.
NS1
Netlify
User reviews (0)