It is a fork of pdfcpu.
pdfcpu is a PDF processing library written in Go supporting encryption. It provides both an API and a CLI. Supported are all versions up to PDF 1.7 (ISO-32000).
Support for PDF 2.0 is basic and ongoing work.
This is an effort to build a comprehensive PDF processing library from the ground up written in Go. Over time pdfcpu aims to support the standard range of PDF processing features and also any interesting use cases that may present themselves along the way.
The primary emphasis is on providing robust assistance for batch processing and scripting through a comprehensive command-line interface. Simultaneously, pdfcpu aims to simplify the integration of PDF processing into your Go-based backend system by offering a versatile set of commands.
- annotations
- attachments
- booklet
- bookmarks
- boxes
- change owner password
- change user password
- collect
- create
- crop
- cut
- decrypt
- encrypt
- extract
- fonts
- form
- grid
- images
- import
- info
- keywords
- merge
- ndown
- nup
- optimize
- pagelayout
- pagemode
- pages
- permissions
- portfolio
- poster
- properties
- resize
- rotate
- split
- stamp
- trim
- validate 👉 now including rudimentory support for PDF 2.0
- viewerpref
- watermark
- zoom
- The main entry point is core.io.
- For CLI examples also go to core.io. There you will find explanations of all the commands and their parameters.
- For API examples of all pdfcpu operations please refer to GoDoc.
- Always make sure your work is based on the latest commit!
- pdfcpu is still Alpha - bugfixes are committed on the fly and will be mentioned in the next release notes.
- Follow pdfcpu for news and release announcements.
- For quick questions or discussions get in touch on the Gopher Slack in the #pdfcpu channel.
- Please create an issue if you find a bug or want to propose a change.
- Feature requests - always welcome!
- Bug fixes - always welcome!
- PRs - let's discuss first or create an issue.
- pdfcpu is stable but still Alpha and occasionally undergoing heavy changes.
- The pdfcpu discussion board is open! Please engage in any form helpful for the community.
- If you want to report a bug please attach the very verbose (
pdfcpu cmd -vv ...) output and ideally a test PDF that you can share. - Always make sure your contribution is based on the latest commit.
- Please sign your commits.
Unfortunately crashes do happen :( For the majority of the cases this is due to a diverse pool of PDF Writers out there and millions of PDF files using different versions waiting to be processed by core. Sometimes these PDFs were written more than 20(!) years ago. Often there is an issue with validation - sometimes a bug in the parser. Many times even using relaxed validation with pdfcpu does not work. In these cases we need to extend relaxed validation and for this we are relying on your help. By reporting crashes you are helping to improve the stability of core. If you happen to crash on any pdfcpu operation be it on the command line or in your Go backend these are the steps to report this:
Regardless of the pdfcpu operation, please start using the pdfcpu command line to validate your file:
$ pdfcpu validate -v &> crash.logor to produce very verbose output
$ pdfcpu validate -vv &> crash.logwill produce what's needed to investigate a crash. Then open an issue and post crash.log or its contents. Ideally post a test PDF you can share to reproduce this. You can also email to hhrutter@gmail.com or if you prefer Slack you can get in touch on the Gopher slack #pdfcpu channel.
If processing your PDF with pdfcpu crashes during validation and can be opened by Adobe Reader and Mac Preview chances are we can extend relaxed validation and provide a fix. If the file in question cannot be opened by both Adobe Reader and Mac Preview we cannot help you!
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.