How to Self-Host Shiori: Minimal Bookmark Manager 2026

TL;DR

Shiori (MIT, ~9K GitHub stars, Go) is a simple self-hosted bookmark manager and read-later tool. It's a lightweight alternative to Pocket or Pinboard: save URLs, archive the page content (offline readable copy), add tags, full-text search. The entire server is a single Go binary. Compare Shiori vs Linkwarden: Shiori is simpler (no PDF archiving, no collections/collaborative); Linkwarden has richer archiving and team features. Shiori is perfect for a solo, minimal setup.

Key Takeaways

• Shiori: MIT, ~9K stars, Go — single binary, SQLite, bookmark + offline archive
• Offline reading: Saves a clean readable copy of every page (no images by default)
• Browser extensions: Chrome and Firefox extensions for one-click save
• Full-text search: Search archived content, not just titles/tags
• REST API: Automate bookmarking from scripts or other tools
• Pocket import: Import your Pocket export directly

---

Shiori vs Linkwarden vs Wallabag

Feature	Shiori	Linkwarden	Wallabag
License	MIT	AGPL 3.0	MIT
GitHub Stars	~9K	~8K	~10K
Storage	SQLite/PostgreSQL	PostgreSQL	MySQL/SQLite
Archive: Readable	Yes	Yes	Yes
Archive: Screenshot	No	Yes	No
Archive: PDF	No	Yes	No
Collections	No (tags only)	Yes	Yes
Multi-user	Yes	Yes	Yes
Browser extension	Yes (Chrome/Firefox)	Yes	Yes
Highlights/annotations	No	No	Yes
RSS feed	No	No	Yes
Pocket import	Yes	No	Yes
Tech	Go	TypeScript/Next.js	PHP
RAM	~30MB	~200MB	~100MB

---

Part 1: Docker Setup

# docker-compose.yml
services:
  shiori:
    image: ghcr.io/go-shiori/shiori:latest
    container_name: shiori
    restart: unless-stopped
    ports:
      - "8080:8080"
    volumes:
      - shiori_data:/shiori
    environment:
      SHIORI_DIR: /shiori
      SHIORI_HTTP_PORT: 8080
      SHIORI_HTTP_ROOT_PATH: ""

volumes:
  shiori_data:

docker compose up -d

Visit http://your-server:8080 — first user to register becomes admin.

---

Part 2: HTTPS with Caddy

bookmarks.yourdomain.com {
    reverse_proxy localhost:8080
}

---

Part 3: First-Time Setup

1. Visit https://bookmarks.yourdomain.com
2. Register your account (first account = admin)
3. Immediately disable registration if this is a personal instance:

environment:
  SHIORI_HTTP_DISABLE_SIGNUP: "true"

Or set from CLI after first user:

docker exec shiori shiori account add -u bob --password secret

---

Part 4: Adding Bookmarks

Web UI

1. Click + New Bookmark
2. Paste URL
3. Shiori fetches the title, description, and optionally archives the page
4. Add tags (comma-separated)
5. Save

Browser Extension

Install the Shiori extension:

• Chrome Web Store
• Firefox Add-ons

Configure in extension settings:

• Server: https://bookmarks.yourdomain.com
• Username + password

Click the extension icon on any page → one-click save with optional tag.

CLI

# Add a bookmark:
docker exec -it shiori shiori add https://example.com -t "tech,reference"

# List bookmarks:
docker exec -it shiori shiori print

# Search:
docker exec -it shiori shiori print -s "docker"

REST API

# Get session token:
TOKEN=$(curl -s -X POST https://bookmarks.yourdomain.com/api/login \
  -H "Content-Type: application/json" \
  -d '{"username":"alice","password":"your-password"}' \
  | jq -r .session)

# Add bookmark:
curl -X POST https://bookmarks.yourdomain.com/api/bookmarks \
  -H "X-Session-Id: $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com","tags":[{"name":"tech"}],"createArchive":true}'

# Search bookmarks:
curl "https://bookmarks.yourdomain.com/api/bookmarks?keyword=docker&tags=ops" \
  -H "X-Session-Id: $TOKEN"

# Delete bookmark:
curl -X DELETE https://bookmarks.yourdomain.com/api/bookmarks \
  -H "X-Session-Id: $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"ids":[42]}'

---

Part 5: Archiving

Shiori can save an offline readable copy of every bookmark:

Archive on save:

1. Check Create archive when adding a bookmark
2. Or set auto-archive by default in settings

Archive existing bookmarks:

# Archive all bookmarks that don't have an archive:
docker exec -it shiori shiori update -i all --create-archive

The archive strips ads and navigation, keeping the main article content readable offline. Images are not stored by default (keeps storage small).

Enable image archiving (larger storage):

environment:
  SHIORI_HTTP_ARCHIVE_IMAGES: "true"

---

Part 6: Import from Pocket

Export your Pocket data and import into Shiori:

1. In Pocket: Settings → Export → HTML
2. Import:

docker cp pocket-export.html shiori:/tmp/
docker exec -it shiori shiori import /tmp/pocket-export.html

Import from Netscape Bookmarks (browser export)

# Export from Chrome/Firefox as HTML
docker cp bookmarks.html shiori:/tmp/
docker exec -it shiori shiori import /tmp/bookmarks.html

---

Part 7: PostgreSQL for Production

For larger libraries, switch from SQLite to PostgreSQL:

services:
  shiori:
    image: ghcr.io/go-shiori/shiori:latest
    environment:
      SHIORI_DIR: /shiori
      SHIORI_DATABASE_URL: "postgres://shiori:${POSTGRES_PASSWORD}@postgres:5432/shiori"
    depends_on:
      - postgres

  postgres:
    image: postgres:16-alpine
    environment:
      POSTGRES_DB: shiori
      POSTGRES_USER: shiori
      POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}"
    volumes:
      - postgres_data:/var/lib/postgresql/data

volumes:
  shiori_data:
  postgres_data:

---

Part 8: Tags and Search

Shiori uses tags for organization (no folders or collections):

# In the search box:
docker               ← full-text search across title, description, archived content
#docker              ← filter by tag "docker"
#docker #ops         ← bookmarks with both tags

Bulk tagging:

# Tag all bookmarks matching a search:
docker exec -it shiori shiori update -s "kubernetes" -t "k8s,ops,devops"

---

Maintenance

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

# Logs:
docker compose logs -f shiori

# Backup (SQLite):
docker exec shiori cp /shiori/shiori.db /shiori/shiori.db.backup
tar -czf shiori-backup-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect shiori_shiori_data --format '{{.Mountpoint}}')

# CLI account management:
docker exec -it shiori shiori account print     # list accounts
docker exec -it shiori shiori account add -u bob  # add user

Why Self-Host Shiori?

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

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

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 Shiori'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 shiori. 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 Shiori Updated

Shiori 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 Shiori 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 bookmark and read-later tools at OSSAlt.com/categories/productivity.