Self-Host Paperless-ngx: Document Management 2026

TL;DR

Paperless-ngx (GPL 3.0, ~20K GitHub stars, Python/TypeScript) eliminates physical filing cabinets. Scan documents, drop PDFs into a watched folder, and Paperless automatically OCRs them, suggests tags and correspondents, and makes them full-text searchable. Adobe Acrobat charges $12.99/month for OCR and PDF management. Paperless-ngx is free and stores everything locally. After setup: every receipt, tax document, medical form, and letter is searchable in under 2 seconds.

Key Takeaways

Paperless-ngx: GPL 3.0, ~20K stars — OCR + full-text search + tag-based document organization
Auto-tagging: ML-based classifier learns from your manual tags and auto-suggests on new documents
Consumed folder: Drop files in a folder → Paperless automatically imports and OCRs them
Full-text search: OCR makes every word in every PDF searchable
Correspondents: Track who documents are from (IRS, Bank of America, doctor's office, etc.)
Document types: Categorize by type (Invoice, Receipt, Medical, Tax, Contract, etc.)

Part 1: Docker Setup

# docker-compose.yml
services:
  broker:
    image: redis:7-alpine
    restart: unless-stopped

  db:
    image: postgres:15-alpine
    restart: unless-stopped
    environment:
      POSTGRES_DB: paperless
      POSTGRES_USER: paperless
      POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}"
    volumes:
      - db_data:/var/lib/postgresql/data

  webserver:
    image: ghcr.io/paperless-ngx/paperless-ngx:latest
    container_name: paperless
    restart: unless-stopped
    ports:
      - "8000:8000"
    volumes:
      - paperless_data:/usr/src/paperless/data
      - paperless_media:/usr/src/paperless/media
      - /path/to/consume:/usr/src/paperless/consume  # Watch this folder
      - /path/to/export:/usr/src/paperless/export    # Export goes here
    environment:
      PAPERLESS_REDIS: redis://broker:6379
      PAPERLESS_DBHOST: db
      PAPERLESS_DBUSER: paperless
      PAPERLESS_DBPASS: "${POSTGRES_PASSWORD}"
      PAPERLESS_DBNAME: paperless
      PAPERLESS_SECRET_KEY: "${SECRET_KEY}"
      PAPERLESS_URL: "https://docs.yourdomain.com"
      PAPERLESS_ADMIN_USER: admin
      PAPERLESS_ADMIN_PASSWORD: "${ADMIN_PASSWORD}"
      PAPERLESS_ADMIN_MAIL: admin@yourdomain.com
      PAPERLESS_TIME_ZONE: America/Los_Angeles
      PAPERLESS_OCR_LANGUAGE: eng
      PAPERLESS_TIKA_ENABLED: 1  # Enable for Office docs (DOCX, XLSX, etc.)
      PAPERLESS_TIKA_GOTENBERG_ENDPOINT: http://gotenberg:3000
      PAPERLESS_TIKA_ENDPOINT: http://tika:9998
    depends_on:
      - broker
      - db

  # Required for Office document conversion:
  gotenberg:
    image: docker.io/gotenberg/gotenberg:7.10
    restart: unless-stopped
    command:
      - "gotenberg"
      - "--chromium-disable-javascript=true"
      - "--chromium-allow-list=file:///tmp/.*"

  tika:
    image: ghcr.io/paperless-ngx/tika:latest
    restart: unless-stopped

volumes:
  db_data:
  paperless_data:
  paperless_media:

# .env
POSTGRES_PASSWORD=your-db-password
SECRET_KEY=your-50-char-secret-key
ADMIN_PASSWORD=your-admin-password

# Create consume folder:
mkdir -p ~/paperless/consume ~/paperless/export

docker compose up -d

Part 2: HTTPS with Caddy

docs.yourdomain.com {
    reverse_proxy localhost:8000
}

Part 3: Import Documents

Method 1: Consume folder (automated)

Drop any file into the consume folder:

# Any of these formats work:
cp ~/Downloads/tax-return-2025.pdf ~/paperless/consume/
cp ~/Downloads/bank-statement.pdf ~/paperless/consume/
cp ~/Desktop/receipt.jpg ~/paperless/consume/

# Paperless watches the folder and automatically:
# 1. Moves file to media storage
# 2. Runs OCR (Tesseract)
# 3. Extracts text
# 4. Suggests tags/correspondent/document type via ML classifier
# 5. Makes it searchable

Method 2: Upload via web UI

Documents → Upload → drag and drop files
Multiple files at once

Method 3: Email ingestion

# Add to docker-compose.yml environment:
PAPERLESS_EMAIL_TASK_CRON: "*/10 * * * *"

# In Paperless web UI:
# Settings → Mail → Add mail account:
PAPERLESS_EMAIL_IMAP_SERVER: mail.yourdomain.com
PAPERLESS_EMAIL_USERNAME: paperless@yourdomain.com
PAPERLESS_EMAIL_PASSWORD: your-email-password

Emails matching rules are automatically imported as documents.

Part 4: Organization System

Correspondents

Track who documents are from:

Settings → Correspondents → Add:
- IRS, Bank of America, Blue Cross, Employer, Landlord

Paperless auto-assigns based on patterns you define, or learns from your corrections.

Document types

Categorize by type:

Invoice, Receipt, Tax Return, Medical Record, Insurance, Contract, Letter

Date extraction

Paperless extracts dates from document content automatically. For receipts or letters, it finds the date in the text.

Part 5: Full-Text Search

# Search examples in the web UI:
"electric bill"           → finds all utility bills
correspondent:IRS         → all IRS documents
tag:2025-taxes            → all 2025 tax documents
type:Invoice              → all invoices
created:[2025-01-01 TO 2025-12-31]  → documents from 2025
content:"account number"  → documents containing that phrase

Combine filters:

correspondent:IRS tag:2025-taxes type:"Tax Return"

Part 6: Scanner Integration

Network scanners (SANE)

# Scan directly to consume folder via command line:
scanimage --device="brother5:net1;dev0" \
  --format=pdf \
  --resolution=300 \
  --mode=Color \
  > ~/paperless/consume/scan-$(date +%Y%m%d-%H%M%S).pdf

iOS/Android scanning

Use a scanning app that saves directly to your consume folder:

iOS: Scanner Pro, Microsoft Lens → save to Nextcloud → watched by Paperless
Android: Adobe Scan, Microsoft Lens → save to synced folder

Automatic scan workflow

Scanner app (iOS/Android)
  → Saves to Nextcloud folder (auto-sync)
  → Nextcloud folder is also your Paperless consume path
  → Paperless auto-imports and OCRs
  → Document searchable within 60 seconds

Part 7: ML Auto-Classifier

Paperless learns from your tagging behavior:

# Train the classifier manually:
docker exec paperless python manage.py document_create_classifier

# After training, Paperless suggests:
# - Correspondent (who it's from)
# - Document type
# - Tags
# - Storage path

# The more you correct suggestions, the better it gets.

Custom matching rules

# Settings → Tags → Edit tag → Add matching rule:
Tag: "medical"
Algorithm: "Any word"
Pattern: "physician diagnosis prescription copay deductible"
Case insensitive: Yes

Part 8: Export and Backup

# Export all documents (preserves metadata):
docker exec paperless document_exporter /usr/src/paperless/export

# This creates:
# export/
# ├── document_001.pdf          ← original file
# ├── document_001.json         ← metadata (tags, date, correspondent)
# ├── document_002.jpg
# └── ...

# The JSON metadata lets you re-import to a fresh Paperless instance.

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

# Media backup:
tar -czf paperless-media-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect paperless_paperless_media --format '{{.Mountpoint}}')

Maintenance

# Update:
docker compose pull
docker compose up -d

# Check Paperless status:
docker exec paperless python manage.py status

# Reprocess a document (e.g., if OCR failed):
docker exec paperless python manage.py document_retagger --id=42

# Re-run classifier on all documents:
docker exec paperless python manage.py document_create_classifier

# Logs:
docker compose logs -f webserver

Why Self-Host Paperless-ngx?

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

Always use a reverse proxy: Never expose Paperless-ngx'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 Paperless-ngx'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 Paperless-ngx'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 paperless-ngx

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 Paperless-ngx'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 paperless-ngx. 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 Paperless-ngx Updated

Paperless-ngx 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 Paperless-ngx 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.

Frequently Asked Questions

How much does it cost to self-host Paperless-ngx?

The primary cost is your server. A Hetzner CAX11 (2 vCPU ARM, 4GB RAM) runs about $5/month — enough for Paperless-ngx plus a few companion services. Add a domain ($12/year) and you're under $75/year for a complete self-hosted deployment. Compare that to SaaS pricing that typically starts at $5-15/user/month.

Can I run Paperless-ngx on a VPS with other services?

Yes. The docker-compose.yml above isolates Paperless-ngx on its own named Docker network. As long as your server has sufficient RAM and disk — 4GB RAM and 20GB disk handles most combinations — running multiple self-hosted services on one VPS is both practical and common. Tools like Dozzle and Portainer make monitoring multi-container setups manageable.

How do I migrate data if I switch servers?

Stop the Paperless-ngx container, export the Docker volumes (using docker run --rm -v VOLUME:/data -v $(pwd):/backup alpine tar czf /backup/backup.tar.gz /data), transfer to the new server, restore the volumes, and update your DNS. Most migrations complete in under an hour. Test the restoration on the new server before decommissioning the old one.

What happens if Paperless-ngx releases a breaking update?

Pin your docker-compose.yml to a specific image tag (e.g., image: paperless-ngx:1.2.3 instead of latest). Subscribe to the GitHub releases page for advance notice. When you're ready to upgrade, read the release notes, back up first, test on a staging instance, then update production.

Is Paperless-ngx suitable for production use?

Yes, with the hardening described above: reverse proxy for HTTPS, firewall rules, regular backups, and a pinned image tag. Many teams run Paperless-ngx in production successfully. The main requirement is treating your self-hosted instance with the same operational discipline you'd apply to any business-critical service.

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

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