pdfcpu is an open-source CLI and Go library for merging, splitting, and securing PDFs locally, replacing desktop suites like Nitro PDF Pro in CI pipelines.
pdfcpu is a command-line processor and Go library for manipulating PDF documents without external C dependencies. It runs entirely as a self-contained binary on local infrastructure, giving teams complete control over document pipelines without transmitting files across the network.
Nitro PDF Pro is an enterprise desktop application that charges recurring seat licenses and relies on graphical interactions, operating system printing subsystems, and proprietary cloud services for collaboration. Teams that only need to automate document assembly, merge multi-page reports, stamp watermarks, or enforce file encryption often pay for Nitro PDF Pro licenses simply because standard office software bundles those functions. pdfcpu replaces that operational overhead with an embeddable CLI and Go API that runs headless in CI/CD runners, container clusters, or microservices with zero per-seat licensing fees.
Privacy and control represent the fundamental difference in architecture. Nitro PDF Pro routes electronic signatures, conversion workflows, and storage through proprietary desktop agents or cloud services, requiring corporate security reviews and compliance sign-offs for confidential files. pdfcpu executes strictly on local hardware, processing files in place without network egress, background telemetry, or third-party cloud infrastructure. What you trade away is Nitro's graphical user interface: pdfcpu cannot provide visual page previewing, interactive text editing, or optical character recognition. It assumes engineers interact through shell scripts, flags, or Go code rather than buttons and drag-and-drop windows.
Is pdfcpu free for commercial use? Yes. It is published under the Apache-2.0 license, permitting commercial distribution and internal deployment with no licensing fees.
pdfcpu vs Nitro PDF Pro — which should I choose? Choose Nitro PDF Pro if you need a visual desktop editor for reading, manual text revisions, and OCR; choose pdfcpu if you want to automate merging, watermarking, and document processing in terminal scripts or Go code.
Can pdfcpu extract plain text from a PDF? No. While pdfcpu can extract embedded fonts, images, and raw content streams, it does not layout glyphs or reconstruct plain text strings.
For teams needing headless, scriptable PDF manipulation that keeps documents strictly within private infrastructure, pdfcpu delivers reliable efficiency and zero external dependencies; it will not satisfy users who require visual document editing or OCR. Active maintenance and an Apache-2.0 license that allows bundling the tool into proprietary applications or backend microservices make it an ideal engine for automated document pipelines.
Commands from the official package registries. Each package is matched to pdfcpu through the registry's own link to its source code or website.
brew install pdfcpuwinget install --id pdfcpu.pdfcpu -ebrew install pdfcpuFree IDE for Java, Kotlin, Go, TypeScript and Python. Built on IntelliJ Community, fully open source, 300+ plugins.
Show that pdfcpu is listed as an open-source alternative. Paste into your README: