Layer 5 · self-hosting reality check
What it actually takes to self-host Stirling PDF
The docs say 4 GB, the vendor's smallest sizing tier (1–10 users: 2 cores, 4 GB, 10 GB disk, 4G container limit). There is an ultra-lite image for smaller machines, with core features only.. In practice you want 4 GB for light use, 8 GB if people OCR scans or convert Office files. The docs say a 50 MB PDF can grow to 200–500 MB in memory, and LibreOffice and Tesseract run outside the Java heap, so set the container limit to at least 1.5× -Xmx.. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.
Usually reached from Adobe Acrobat Pro alternatives, where Stirling PDF is one of the picks.
Wondering whether you need to at all? Is Adobe Acrobat free? — what the free tier actually allows, and where the wall is.
| RAM — documented minimum | 4 GB, the vendor's smallest sizing tier (1–10 users: 2 cores, 4 GB, 10 GB disk, 4G container limit). There is an ultra-lite image for smaller machines, with core features only. |
|---|---|
| RAM — what it really needs | 4 GB for light use, 8 GB if people OCR scans or convert Office files. The docs say a 50 MB PDF can grow to 200–500 MB in memory, and LibreOffice and Tesseract run outside the Java heap, so set the container limit to at least 1.5× -Xmx. |
| CPU | 2 cores (4+ recommended) for 1–10 users. OCR and file conversion are the heaviest jobs. |
| Disk | 10 GB free for a small team, 50 GB of SSD for 10–50 users. Files over 50 MB are processed on disk. |
| Monthly cost | $7–24/mo on a 4 GB VPS. Since v3, API and automation use above 1,000 PDFs a month is metered unless you buy a licence or credits. |
| Setup time | 15 minutes with one docker run |
| How you install it | `docker run` with the stirlingtools/stirling-pdf:latest image and a /configs volume. Use `latest-fat` for the best conversions and `latest-ultra-lite` for small boxes. Log in as admin / stirling and change it. |
| Ongoing maintenance | Pull the new image and recreate the container. Releases come fast (v3.0.0 on 24 Sep 2026, v3.0.1 two days later, and the vendor expects near-weekly releases), so pin a tag and read release notes before you upgrade. |
| Where it stops scaling | Vendor sizing goes up to 100+ users on 8+ cores and 16–32 GB, with 4 LibreOffice and 2 Tesseract sessions running in parallel. Beyond one box there is a Kubernetes guide. |
The thing that catches people out
Stirling PDF 3.0 (24 Sep 2026) started metering automation. Manual work in the web editor stays free and unlimited. API calls, the new Processor and the AI tools draw on a processing allowance of 1,000 PDFs a month, and the vendor's own pull request says those calls can be blocked once it runs out, unless the server holds a paid Server licence. Anyone running `:latest` behind an n8n or Paperless pipeline got this change automatically. Pin an image version, count your monthly API volume before upgrading, and budget for a licence if it is over 1,000.
When not to self-host Stirling PDF
You only merge or sign an occasional PDF on one machine: the Stirling desktop app runs the tools locally with no server. Skip it too if your pipeline pushes thousands of PDFs a month through the API and you won't pay for a licence. Call OCRmyPDF or qpdf directly instead.
Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.
Other Layer 5 self-hosting guides
- Self-hosting LibreOffice2 GB with a large spreadsheet open
- Self-hosting ONLYOFFICE6 GB for the Document Server with a handful of concurrent editors
- Self-hosting Collabora Online4 GB, and roughly 1 GB per 20 concurrent documents
- Self-hosting CryptPad2 GB for a small instance
- Self-hosting Mattermost4 GB for a team of 50 with PostgreSQL on the same box
- Self-hosting Rocket.Chat6 GB with MongoDB on the same machine
Common questions
- How much RAM does Stirling PDF actually need?
- 4 GB for light use, 8 GB if people OCR scans or convert Office files. The docs say a 50 MB PDF can grow to 200–500 MB in memory, and LibreOffice and Tesseract run outside the Java heap, so set the container limit to at least 1.5× -Xmx. in practice. The documented minimum is 4 GB, the vendor's smallest sizing tier (1–10 users: 2 cores, 4 GB, 10 GB disk, 4G container limit). There is an ultra-lite image for smaller machines, with core features only., which is the figure at which the process starts rather than the figure at which it works under real use. 2 cores (4+ recommended) for 1–10 users. OCR and file conversion are the heaviest jobs. alongside it.
- What does self-hosting Stirling PDF cost per month?
- $7–24/mo on a 4 GB VPS. Since v3, API and automation use above 1,000 PDFs a month is metered unless you buy a licence or credits. This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for pull the new image and recreate the container. Releases come fast (v3.0.0 on 24 Sep 2026, v3.0.1 two days later, and the vendor expects near-weekly releases), so pin a tag and read release notes before you upgrade.
- How long does it take to set up Stirling PDF?
- 15 minutes with one docker run, via `docker run` with the stirlingtools/stirling-pdf:latest image and a /configs volume. Use `latest-fat` for the best conversions and `latest-ultra-lite` for small boxes. Log in as admin / stirling and change it..
- When should I NOT self-host Stirling PDF?
- You only merge or sign an occasional PDF on one machine: the Stirling desktop app runs the tools locally with no server. Skip it too if your pipeline pushes thousands of PDFs a month through the API and you won't pay for a licence. Call OCRmyPDF or qpdf directly instead.
- What is the most common mistake when self-hosting Stirling PDF?
- Stirling PDF 3.0 (24 Sep 2026) started metering automation. Manual work in the web editor stays free and unlimited. API calls, the new Processor and the AI tools draw on a processing allowance of 1,000 PDFs a month, and the vendor's own pull request says those calls can be blocked once it runs out, unless the server holds a paid Server licence. Anyone running `:latest` behind an n8n or Paperless pipeline got this change automatically. Pin an image version, count your monthly API volume before upgrading, and budget for a licence if it is over 1,000.