explaingit

stirling-tools/stirling-pdf

🔥 Hot78,908TypeScriptAudience · developerComplexity · 3/5ActiveLicenseSetup · moderate

TLDR

Open-source platform to edit, sign, convert, and automate PDFs on your own machine or server without uploading to external services.

Mindmap

mindmap
  root((Stirling PDF))
    What it does
      Edit and sign PDFs
      Split and merge files
      Convert formats
      Redact sensitive content
    How to run it
      Desktop app
      Browser UI
      Docker container
      Self-hosted server
    Key features
      50+ PDF tools
      Workflow pipelines
      REST APIs
      OCR support
    Use cases
      Batch processing
      API integration
      Enterprise deployments
      Privacy-first workflows

Things people build with this

USE CASE 1

Batch split, merge, or convert hundreds of PDFs without uploading to third-party websites.

USE CASE 2

Integrate PDF signing, redaction, and OCR into your own application via REST APIs.

USE CASE 3

Set up a private, self-hosted PDF processing server for your organization with audit logs and single sign-on.

USE CASE 4

Create no-code workflows in the UI to chain PDF operations together and process files automatically.

Tech stack

TypeScriptDockerREST APIBrowser-based UI

Getting it running

Difficulty · moderate Time to first run · 30min

Requires Docker to run the platform locally; building from source or running without containerization may add complexity.

Open-core model with source code available; enterprise features available under commercial licensing.

In plain English

Stirling PDF is an open-source platform for editing and working with PDF documents. The README describes it as a way to edit, sign, redact, convert, and automate PDFs without sending the documents to external services, which is the main appeal: you keep your files on your own machine or your own server. You can run Stirling PDF in three different shapes. There is a personal desktop app, a browser-based UI you point at a local instance, and a self-hosted server deployment that exposes a private API. Quick-start instructions show running it as a Docker container that exposes its UI on port 8080. The project advertises more than 50 PDF tools covering common needs, editing, merging, splitting, signing, redacting, converting between formats, running OCR (reading text out of scanned PDFs), and compressing files. On top of these tools sit no-code workflow pipelines so you can chain operations together in the UI and process many files at once, plus REST APIs for nearly all tools so the same operations can be wired into other software. The README also lists enterprise features such as single sign-on, auditing, and flexible on-premise deployments, and notes the interface is translated into 40+ languages. Someone would use Stirling PDF when they need to manipulate PDFs frequently, splitting them, filling them, redacting sensitive content, or batch-converting, and either prefer not to upload documents to a third-party website or want to integrate PDF processing into their own systems. The project is described as open-core. According to the repository metadata, it is primarily written in TypeScript.

Copy-paste prompts

Prompt 1
How do I set up Stirling PDF as a Docker container and access it from my browser on localhost:8080?
Prompt 2
Show me how to use the REST API to programmatically split a PDF and convert it to images in my Node.js app.
Prompt 3
How do I create a workflow pipeline in Stirling PDF to batch redact sensitive text from 100 PDFs at once?
Prompt 4
What are the steps to deploy Stirling PDF on my own server with single sign-on and audit logging enabled?
Prompt 5
How can I use Stirling PDF's OCR tool to extract text from scanned PDFs and save the results as searchable PDFs?
Open on GitHub → Explain another repo

Generated 2026-05-18 · Model: sonnet-4-6 · Verify against the repo before relying on details.