Validate your PDF output yourself
Published PDF standards samples pair downloadable output with local validator commands. The workflow uses veraPDF and qpdf.
NextPDF journal
From the team
Engineering notes, standards deep-dives, and product updates from the team building NextPDF.
Why we built a PDF 2.0 engine for modern PHP
PHP has had PDF libraries for twenty years. NextPDF combines PDF 2.0 output, tagged accessibility, and PAdES signatures in one in-process, strictly typed engine. It produces the requested result or returns a typed failure.
Typed failures for precise PDF output
NextPDF uses typed failures and fail-closed defaults to define clear boundaries for unsupported operations.
The company behind NextPDF
NextPDF is the open core of a commercial product built by a Taipei security company whose ISMS is certified to ISO/IEC 27001:2022.
Welcome to the NextPDF blog
An introduction to how the NextPDF journal covers engine internals, digital signatures, accessibility, and testing discipline.
Why PDF 2.0, and why now
NextPDF builds on the PDF 2.0 (ISO 32000-2) object model, with tagged structure, PAdES signatures, and PDF/A-4 archival profiles in scope.