Self-Host Linkding: Open Source Bookmark Manager 2026

TL;DR

Linkding (MIT, ~6K GitHub stars, Python/Django) is a minimal self-hosted bookmark manager — fast, lightweight, and focused. Save URLs with tags, search instantly, import from browser exports or Pocket/Pinboard, and access a clean REST API. Pinboard charges $22/year; Raindrop.io charges $3/month for Pro. Linkding runs on a $5 VPS with under 50MB RAM and has no subscription.

Key Takeaways

Linkding: MIT, ~6K stars, Python/Django — bookmark manager with tags, search, and sharing
Browser extensions: Chrome and Firefox — save the current page with one click
REST API: Full CRUD API with token auth — automate bookmark collection
Import/export: Netscape HTML format (all browsers), Pocket, Pinboard CSV
Shared bookmarks: Optional public bookmark pages per user
Minimal footprint: ~50MB RAM, SQLite by default — runs on the smallest VPS

Linkding vs Raindrop.io vs Hoarder

Feature	Linkding	Raindrop.io	Hoarder
Price	Free (self-host)	$3/mo Pro	Free (self-host)
AI tagging	No	Yes	Yes (Ollama)
Full-page archive	No	Yes (Pro)	Yes
Screenshot	No	Yes (Pro)	Yes
Collections/folders	Tags only	Yes	Lists
Mobile app	PWA	Native	Native
REST API	Yes	Yes	Yes
Speed	Very fast	Fast	Moderate

Part 1: Docker Setup

# docker-compose.yml
services:
  linkding:
    image: sissbruecker/linkding:latest
    container_name: linkding
    restart: unless-stopped
    ports:
      - "9090:9090"
    volumes:
      - linkding_data:/etc/linkding/data
    environment:
      # Create the first superuser automatically:
      LD_SUPERUSER_NAME: admin
      LD_SUPERUSER_PASSWORD: "${ADMIN_PASSWORD}"

      # Optional: disable public registration
      LD_DISABLE_BACKGROUND_TASKS: "False"

      # Optional: serve under a subpath (e.g. /bookmarks)
      # LD_CONTEXT_PATH: bookmarks/

      # Optional: enable CSRF trusted origins for reverse proxy:
      LD_CSRF_TRUSTED_ORIGINS: "https://links.yourdomain.com"

volumes:
  linkding_data:

docker compose up -d

Visit http://your-server:9090 → log in with your admin credentials.

Part 2: HTTPS with Caddy

links.yourdomain.com {
    reverse_proxy localhost:9090
}

Part 3: Browser Extensions

Chrome / Chromium

Install Linkding Extension
Extension → Options:
- Base URL: https://links.yourdomain.com
- API token: copy from Settings → Integrations → REST API
Click extension icon on any page → opens bookmark dialog
Add tags → Save

Firefox

Install from Mozilla Add-ons: search "Linkding"
Same configuration

Keyboard shortcut

Both extensions support a configurable keyboard shortcut for fast saving without taking your hands off the keyboard.

Part 4: REST API

Get your API token

Settings → Integrations → REST API → Generate token

API examples

TOKEN="your-api-token"
BASE="https://links.yourdomain.com"

# List bookmarks:
curl "$BASE/api/bookmarks/" \
  -H "Authorization: Token $TOKEN" | jq '.results[].url'

# Add a bookmark:
curl -X POST "$BASE/api/bookmarks/" \
  -H "Authorization: Token $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/article",
    "title": "Article Title",
    "description": "Notes about this link",
    "tag_names": ["tech", "read-later"],
    "is_archived": false
  }'

# Search bookmarks:
curl "$BASE/api/bookmarks/?q=kubernetes" \
  -H "Authorization: Token $TOKEN" | jq '.results[].title'

# Archive a bookmark (move to archive):
curl -X POST "$BASE/api/bookmarks/42/archive/" \
  -H "Authorization: Token $TOKEN"

# Delete a bookmark:
curl -X DELETE "$BASE/api/bookmarks/42/" \
  -H "Authorization: Token $TOKEN"

# List tags:
curl "$BASE/api/tags/" \
  -H "Authorization: Token $TOKEN" | jq '.results[].name'

Part 5: Import and Export

Import from browser

Export bookmarks from Chrome/Firefox (Bookmarks Manager → Export) → bookmarks.html
Linkding → Settings → Import
Select file → Import

All bookmark folders become tags.

Import from Pocket

Pocket → Export → ril_export.html
Linkding → Settings → Import → select Pocket file
Pocket tags are preserved

Import from Pinboard

# Download Pinboard JSON export, convert to Netscape HTML format:
# Linkding accepts Netscape HTML format directly

# Or use the CLI tool:
pip install linkding-cli
linkding import --token $TOKEN --file pinboard_export.html

Export

# Export all bookmarks as Netscape HTML (importable to any browser):
curl "$BASE/api/bookmarks/?limit=9999&format=html" \
  -H "Authorization: Token $TOKEN" \
  -o bookmarks-export.html

Part 6: Tagging and Search

Search syntax

Linkding supports full-text search across URL, title, description, and tags:

# Search by keyword:
kubernetes

# Search by tag:
#docker

# Search by URL domain:
github.com

# Combined:
kubernetes #docker github.com

# Untagged bookmarks:
!untagged

# Archived bookmarks:
Go to the Archive tab

Tag strategy

Good tagging makes bookmarks actually useful:

Content type:  #article #video #tool #paper #repo #doc
Topic:         #docker #kubernetes #rust #python #sre
Status:        #read-later #reading #reference #done
Project:       #ossalt #work #personal

Public bookmarks

Users can mark individual bookmarks as public — visible at:

https://links.yourdomain.com/public?user=admin

Enable public sharing per user: Settings → General → Enable public bookmarks

Multiple users

Add additional users via the admin panel:

# Create a new user via Django CLI:
docker exec -it linkding python manage.py createsuperuser

# Or create a regular user:
docker exec -it linkding python manage.py shell -c "
from django.contrib.auth.models import User
User.objects.create_user('alice', 'alice@example.com', 'password123')
"

Part 8: Automation

Save bookmarks from command line

# Quick save function (add to ~/.bashrc or ~/.zshrc):
bm() {
  curl -s -X POST "https://links.yourdomain.com/api/bookmarks/" \
    -H "Authorization: Token $TOKEN" \
    -H "Content-Type: application/json" \
    -d "{\"url\": \"$1\", \"tag_names\": [\"cli\"]}"
  echo "Saved: $1"
}

# Usage:
bm "https://example.com/article"

Save from iOS Shortcuts

Shortcuts → New Shortcut → Get contents of URL
URL: https://links.yourdomain.com/api/bookmarks/
Method: POST
Headers: Authorization: Token $TOKEN
Body: {"url": "Shortcut Input", "tag_names": ["ios"]}
Add to Share Sheet → save any URL from Safari

ntfy notification on save

# Webhook approach: Linkding doesn't have webhooks natively,
# but you can poll the API and notify on new bookmarks:

# Run daily to check for unread bookmarks:
COUNT=$(curl -s "$BASE/api/bookmarks/?is_archived=false" \
  -H "Authorization: Token $TOKEN" | jq '.count')

curl -d "You have $COUNT unread bookmarks" \
  https://ntfy.yourdomain.com/bookmarks

Maintenance

# Update Linkding:
docker compose pull
docker compose up -d

# Backup (SQLite):
docker cp linkding:/etc/linkding/data/db.sqlite3 \
  ./linkding-backup-$(date +%Y%m%d).db

# Or backup the full data directory:
tar -czf linkding-data-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect linkding_linkding_data --format '{{.Mountpoint}}')

# Check health:
curl https://links.yourdomain.com/health

# Logs:
docker compose logs -f linkding

Why Self-Host Linkding?

The case for self-hosting Linkding comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Linkding means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Linkding, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Linkding headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Linkding data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Linkding without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Linkding's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Linkding backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Linkding's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Linkding's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Linkding's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Linkding's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f linkding

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Linkding's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

Confirm the container is running: docker compose ps
Test locally on the server: curl -I http://localhost:PORT
If local access works but external doesn't, check your firewall: ufw status
If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats linkding. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Linkding Updated

Linkding follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Linkding is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

See also: Hoarder — AI-powered alternative with automatic tagging and full-page archiving

See all open source productivity tools at OSSAlt.com/categories/productivity.

The SaaS-to-Self-Hosted Migration Guide (Free PDF)