Self-Host Linkwarden: Social Bookmark Manager 2026

TL;DR

Linkwarden (AGPL 3.0, ~8K GitHub stars, TypeScript/Next.js) is a self-hosted bookmark manager with automatic page archiving. When you save a link, Linkwarden captures a screenshot, a readable text snapshot (Readability), and preserves the page as a PDF — so you always have the content even if the original page goes offline. Replace Pocket (now owned by Mozilla/going paid) or Instapaper with your own archiving system.

Key Takeaways

• Linkwarden: AGPL 3.0, ~8K stars, TypeScript — bookmarks + automatic archiving
• Archiving: Screenshots + readable text + PDF snapshots per bookmark
• Browser extension: Chrome and Firefox extensions for one-click saving
• Collections: Organize links into collections, shareable with others
• Tags: Flexible tagging system
• Search: Full-text search across bookmarks and archived content
• RSS feeds: Import links from RSS feeds automatically

---

Linkwarden vs Pocket vs Pinboard

Feature	Linkwarden (self-hosted)	Pocket	Pinboard
License	AGPL 3.0	Proprietary	Proprietary
Cost	Free (hosting)	Free / $5/mo	$11/year
Page archiving	Yes (auto)	Premium only	Yes (paid)
Screenshots	Yes	No	No
Full-text search	Yes	Yes (premium)	Yes
Tags	Yes	Yes	Yes
Collections	Yes	No	No
Sharing	Yes	No	Yes
Browser extension	Yes	Yes	Yes
Self-hosted	Yes	No	No

---

Part 1: Docker Setup

# docker-compose.yml
services:
  linkwarden:
    image: ghcr.io/linkwarden/linkwarden:latest
    container_name: linkwarden
    restart: unless-stopped
    ports:
      - "3000:3000"
    volumes:
      - linkwarden_data:/data/data
    environment:
      DATABASE_URL: "postgresql://postgres:${POSTGRES_PASSWORD}@db:5432/linkwarden"
      NEXTAUTH_SECRET: "${NEXTAUTH_SECRET}"
      NEXTAUTH_URL: "https://links.yourdomain.com"
      NEXT_PUBLIC_DISABLE_REGISTRATION: "false"    # Set true after creating account
    depends_on:
      db:
        condition: service_healthy

  db:
    image: postgres:16-alpine
    restart: unless-stopped
    environment:
      POSTGRES_DB: linkwarden
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}"
    volumes:
      - postgres_data:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      interval: 10s

volumes:
  linkwarden_data:
  postgres_data:

# Generate NEXTAUTH_SECRET:
openssl rand -hex 32

docker compose up -d

---

Part 2: HTTPS with Caddy

links.yourdomain.com {
    reverse_proxy localhost:3000
}

Visit https://links.yourdomain.com → register your account.

---

Part 3: Browser Extension

Install the Linkwarden browser extension to save links from any page:

• Chrome/Chromium: Chrome Web Store
• Firefox: Firefox Add-ons

Setup:

1. Install extension
2. Click extension icon → Settings
3. Instance URL: https://links.yourdomain.com
4. Enter your credentials
5. Click extension icon on any page → Save link

---

Part 4: Organize with Collections

Collections are the primary organization structure:

1. Sidebar → Collections → + New Collection
2. Name: "Dev Resources", "Recipes", "Articles to Read", "Research"
3. Color: pick a color for visual organization
4. Optional: share collection with other users (view or edit access)

Save links to collections:

• Via browser extension: select collection in the save dialog
• Via web UI: Add Link → select collection

---

Part 5: Tags

Add tags for cross-collection organization:

1. When saving a link → add tags: javascript, docker, tutorial
2. Tag view: Click any tag in the sidebar → see all links with that tag
3. Search by tag: Use the search bar with tag filter

---

Part 6: Archiving and Snapshots

When a link is saved, Linkwarden automatically:

1. Screenshots: Full-page screenshot of the page
2. Readable: Extracts the article text (Mozilla Readability)
3. PDF: Creates a PDF snapshot of the page

View archives:

• Click any saved link → Archive tab → view screenshot/readable/PDF

This means you keep the content even if:

• The original page is deleted
• The domain expires
• The article is paywalled later
• The site goes offline

Manual re-archive: Click the refresh icon on any link to re-capture.

---

Part 7: Import Existing Bookmarks

From Browser (HTML export)

1. Chrome/Firefox: Bookmarks Manager → Export to HTML file
2. Linkwarden → Settings → Import → Browser bookmarks → upload HTML

From Pocket

1. Pocket: Settings → Export (creates HTML)
2. Import the HTML file into Linkwarden

From Raindrop.io

1. Raindrop → Settings → Backups → Export CSV
2. Linkwarden → Settings → Import → CSV

---

Part 8: Share Collections

Collaborate on bookmark collections:

1. Collection → Settings → Sharing
2. Public: Anyone with the link can view
3. Invite by email: Specific users can view or edit

Share URL: https://links.yourdomain.com/public/collection/COLLECTION_ID

Team use case: Shared "Team Resources" collection → all team members add useful links.

---

Part 9: RSS Feed Import

Automatically import links from RSS feeds:

1. Settings → RSS Feeds → Add RSS Feed
2. URL: https://news.ycombinator.com/rss (or any RSS feed)
3. Collection: where to save imported items
4. Fetch interval: hourly, daily

All new items from the RSS feed appear in your chosen collection automatically.

---

Part 10: API Access

# Get API key from Settings → API Keys → Create New

# Get all links:
curl https://links.yourdomain.com/api/v1/links \
  -H "Authorization: Bearer YOUR_API_KEY"

# Create a link:
curl -X POST https://links.yourdomain.com/api/v1/links \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com","name":"Example Site","tags":["example"]}'

# Get collections:
curl https://links.yourdomain.com/api/v1/collections \
  -H "Authorization: Bearer YOUR_API_KEY"

Use the API with n8n or scripts to automatically save links from other sources.

---

Maintenance

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

# Backup:
# Database:
docker exec linkwarden-db-1 pg_dump -U postgres linkwarden | gzip \
  > linkwarden-db-$(date +%Y%m%d).sql.gz

# Archived content (screenshots, PDFs):
tar -czf linkwarden-data-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect linkwarden_linkwarden_data --format '{{.Mountpoint}}')

# Logs:
docker compose logs -f linkwarden

Why Self-Host Linkwarden?

The case for self-hosting Linkwarden 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 Linkwarden 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 Linkwarden, 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 Linkwarden 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 Linkwarden 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 Linkwarden 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 Linkwarden'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 Linkwarden 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 Linkwarden's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Linkwarden'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 Linkwarden'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 Linkwarden'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 linkwarden

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 Linkwarden's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

1. Confirm the container is running: docker compose ps
2. Test locally on the server: curl -I http://localhost:PORT
3. If local access works but external doesn't, check your firewall: ufw status
4. 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 linkwarden. 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 Linkwarden Updated

Linkwarden 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 Linkwarden 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 all open source productivity and bookmarking tools at OSSAlt.com/alternatives/pocket.