Links checked 2026-10-14
Self-hosting Stirling PDF
The self-hosted route instead of Adobe Acrobat, online PDF converters.
The documented install is one container with a volume. The care it needs is authentication and choosing the right image variant, not the deployment itself.
What it is
A PDF toolkit you host yourself: merge, split, sign, redact, compress, convert and run OCR, through a browser interface or its own API. It exists so that documents do not have to be uploaded to somebody else's converter.
What you actually need
This is the reader's own hardware and configuration, not a price. We describe what a job needs; we do not put a figure on what self-hosting costs, because that depends on the provider, the term and the disk you choose.
- The server
- The project's documentation attaches memory guidance to each image variant — the standard image, a larger one that bundles the AI engine, and a lightweight one with the core tools only. Pick the variant that matches the work you actually do.
- How it installs
- A single container, run directly or with Docker Compose. Desktop builds exist for personal use.
- Data store
- No external database. The container keeps its settings and its own small database in a mounted volume.
- What grows
- The mounted configuration and log volumes, plus whatever you process. Large batches want scratch space on the same box.
Before it is safe to expose
- Login and administrator credentials before it is reachable from a network you do not control
- A reverse proxy and TLS if it is exposed beyond your own machine
- A note of your chosen image tag, so an upgrade is a decision rather than a surprise
The trade-offs, specifically for Stirling PDF
- An unauthenticated document editor on a public URL is the obvious risk. Set credentials before you expose it, not after.
- The image variants exist for a reason: OCR, Office conversion and ebook tooling are heavy, and the documentation says so next to each tag.
- OCR and format conversion are processor-bound; a large batch will keep the machine busy for a while.
- It is a utility, not an archive. There is no versioned document store behind it, so keep your originals somewhere that does have one.
And the six things you own from now on
These are true of every tool in this section, including Stirling PDF. They are also the reason to decide against self-hosting, which is a legitimate decision.
- You own the updates. Security releases have to be applied by you, on your schedule, and a project that stops publishing releases becomes your problem to notice.
- You own the backups, and a backup is not a backup until you have restored from it once.
- You own the uptime. There is no status page to watch and no support line to call when it stops answering.
- You own the security patches, the TLS certificate, the reverse proxy and the firewall in front of it.
- You are the on-call rota. The failure mode nobody plans for is being the only person who knows how the thing was set up.
- The hardware has a running cost and a lifetime. Disks fail, and the replacement is on you.
What you give up
- A commercial editor's desktop features and its support contract
- The conveniences of a managed service that updates itself
What you gain
- Documents are processed on your own machine rather than uploaded to a third party
- An API you can call from scripts and automated pipelines
Elsewhere in the index
The box it runs on
The project's documentation attaches memory guidance to each image variant — the standard image, a larger one that bundles the AI engine, and a lightweight one with the core tools only. Pick the variant that matches the work you actually do. That machine is the purchase this page is really about, and it is the one number we will not invent for you: the right size depends on the provider, the term and the disk, so check it on the provider's own page.
Hostinger
Hostinger's VPS product is the closest fit to a self-hosted application: its own page advertises root access, Docker and NVMe storage, with data centres in several regions.
See Hostinger's plansRead Hostinger's published pricing ↗DigitalOcean
Virtual machines billed as you use them, with separate volumes, snapshots and object storage for the parts you want to keep outside the server.
See DigitalOcean's plansRead DigitalOcean's published pricing ↗Hetzner
Cloud instances and dedicated servers with rates published per instance size, so the cost of a bigger box is visible before you move.
See Hetzner's plansRead Hetzner's published pricing ↗What to check before you buy
- A virtual machine you have root on, not a website plan with a control panel bolted on top.
- Snapshots or automated backups, and where those backups are stored.
- Block storage or object storage for the data that will outgrow the server's own disk.
- What the monthly rate renews at, rather than the first-term rate on the signup page.
- Where the data centre is, if the data has a jurisdiction attached to it.
The “See plans” links go through our own /go/ redirect and some are affiliate links, which pay us if you sign up. The descriptions and trade-offs on this page are written from the project's own documentation and are unaffected. The plain pricing link under each provider is not an affiliate link. See our disclosure.
Frequently asked questions about self-hosting Stirling PDF
Answers restate the notes on this page or point at the project's own documentation. Self-hosting moves work to you rather than removing it, and these answers say so.
What is Stirling PDF?
A PDF toolkit you host yourself: merge, split, sign, redact, compress, convert and run OCR, through a browser interface or its own API. We cover it as a replacement for Adobe Acrobat, online PDF converters.
What do you need to run Stirling PDF yourself?
A single container, run directly or with Docker Compose. Desktop builds exist for personal use. The requirements table on this page lists the server, the data store, what grows and what else to arrange first. Setup steps are at Stirling PDF's Docker install guide.
How hard is Stirling PDF to run yourself?
We rate it Straightforward. The documented install is one container with a volume. The care it needs is authentication and choosing the right image variant, not the deployment itself.
What are the trade-offs of self-hosting Stirling PDF?
Our notes list these costs. An unauthenticated document editor on a public URL is the obvious risk. Set credentials before you expose it, not after. The image variants exist for a reason: OCR, Office conversion and ebook tooling are heavy, and the documentation says so next to each tag.
What do you give up by running Stirling PDF yourself?
You take on what Adobe Acrobat, online PDF converters used to do for you. A commercial editor's desktop features and its support contract. The conveniences of a managed service that updates itself. Self-hosting moves that work to you rather than removing it.
What do you gain by running Stirling PDF yourself?
Our notes list these. Documents are processed on your own machine rather than uploaded to a third party. An API you can call from scripts and automated pipelines.