Stirling-PDF: the PDF toolbox that lives on your NAS
Every household has a PDF workflow held together by sketchy free websites — upload a tax form here, a signed contract there, and hope. Stirling-PDF ends that: more than sixty PDF tools (merge, split, OCR, redact, sign, compress, convert) in one self-hosted container that processes everything locally. It is the #2 most-recommended app on r/selfhosted, ahead of Home Assistant itself — and it pairs with Paperless-ngx like they were designed together.
Published Nov 18, 2026
Deploy it
services:
stirling-pdf:
image: stirlingtools/stirling-pdf:latest
container_name: stirling-pdf
ports:
- "8080:8080"
volumes:
- ./stirling/configs:/configs
- ./stirling/customFiles:/customFiles
- ./stirling/logs:/logs
environment:
- LANGS=en-US # OCR + UI language
restart: unless-stopped
That is genuinely the whole install — one container, no database, no account. Open it at your NAS's port 8080 (remap the host side if qBittorrent or a friend already owns 8080 — the Compose generator flags exactly that collision). First run walks you through optional login setup; for a LAN-only family tool many households skip accounts entirely and let the reverse proxy or Tailscale be the gate.
The tools you will actually use
- OCR my PDF — turns a scanned image-PDF into searchable text. This is the Paperless front-end: scan → OCR here (or in Paperless) → archive.
- Redact — real redaction that removes the underlying text, not the black-box-over-text trick that has embarrassed institutions. Verify on a copy anyway; trust, but check.
- Merge / split / reorganize — the daily bread: combine the bank statements, split the 200-page closing packet.
- Sign & certify — draw or type signatures for the endless school/permission/consent forms of household life.
- Convert — PDF ↔ images, office docs → PDF, HTML → PDF for archiving web receipts before they vanish.
- Compress — shrink the 40 MB scan the multifunction printer produced into something emailable.
Pairing with Paperless-ngx
Paperless is the archive; Stirling is the workbench. The workflow that emerges: documents arrive (scanner, email, downloads), anything needing surgery — merging a two-part form, redacting an account number before sharing, OCR for a stubborn scan — goes through Stirling, and the finished document lands in Paperless's consume folder for tagging and permanent search. Our Paperless guide covers the archive side; keep both on the same NAS and the pair covers the entire paper life of a house. For tax season specifically, this duo is the whole system: gather in Paperless, prepare in Stirling, send with confidence.
Settings worth five minutes
- OCR languages: the LANGS setting and OCR language packs decide recognition quality for non-English documents — set them before the first big scan job, not after a bad result.
- Security: enable login if the instance is reachable beyond your LAN; better, keep it LAN/Tailscale-only like the rest of this site's stack.
- Pipelines: Stirling's automated pipeline feature watches folders and applies tool chains (e.g., everything dropped here gets OCR'd and compressed) — the power feature that turns it from website to appliance.
Official documentation and references
- Stirling-PDF documentation — installation, configuration and features
- Stirling-PDF — the official project site
- Stirling-PDF on GitHub — source code and releases
Frequently asked questions
Is Stirling-PDF really private? My PDFs are sensitive.
Yes — processing happens in the container on your NAS; documents are not uploaded anywhere. That is the entire point versus free web tools, and why it suits tax forms, contracts and medical paperwork.
How is this different from Paperless-ngx?
Paperless archives and searches documents you keep. Stirling edits and transforms PDFs themselves. They are complements: Stirling is the workbench, Paperless is the filing cabinet — most households end up running both.
Does it need much hardware?
Very little for everyday tools. OCR of large batches is the only CPU-hungry job; a modern NAS handles it fine, just let big batches run rather than expecting instant results.

