Answers for building with NextPDF

NextPDF Core is the Apache License 2.0 edition for PDF creation and HTML-to-PDF. NextPDF Pro adds charts, templates, redaction, and timestamped signing. NextPDF Enterprise adds long-term signing, HSM and PKCS#11 hardware signing, archival output, e-invoicing, and document forensics. All three editions use the same in-process engine and API. See the edition comparison.

NextPDF Connect is the access surface for your installed edition. It exposes the engine over MCP, REST, and gRPC, then loads the NextPDF Pro or NextPDF Enterprise capabilities present in your application. NextPDF Connect uses the Apache License 2.0. See NextPDF Connect.

NextPDF Core generates PDF 2.0 documents from HTML and CSS, emits tagged structure targeting PDF/UA-2, applies PAdES B-B signatures, and exposes the engine through NextPDF Connect. It runs in your PHP process under the Apache License 2.0. Install NextPDF Core, or review the commercial editions on pricing.

Each NextPDF output target names the standard and structures it covers: PDF 2.0, PDF/UA-2, PDF/A-4, PAdES, or EN 16931. An external validator determines formal conformance for your document and data. Use the commands in the conformance matrix to inspect the result.

The PAdES baseline levels add requirements in sequence. PAdES B-B in NextPDF Core embeds the digital signature and signer certificate. PAdES B-T in NextPDF Pro adds an RFC 3161 timestamp token for the signature. PAdES B-LT in NextPDF Enterprise adds validation material in the DSS. PAdES B-LTA adds document timestamps for archival validation. See signed agreements.

Use qpdf --check for PDF structure, veraPDF for PDF/UA or PDF/A, OpenSSL for the digital signature, and pdfdetach for embedded e-invoice XML. The showcase publishes downloadable engine output, generating source, and SHA-256 provenance for independent checks.

PDF/A-3 permits embedded files. ZUGFeRD and Factur-X use it as a carrier for structured EN 16931 XML and a human-readable PDF. PDF/A-4 is a separate, PDF 2.0-based profile for long-term preservation. NextPDF Enterprise targets both output paths.

PDF/UA-2 is the accessibility profile for PDF 2.0. It covers logical structure, document language, reading order, and figure alternative text. NextPDF targets PDF/UA-2 with those document structures. You supply meaningful alternative text, reading order, and content.

The native packages target PHP 8.4 or newer on the 8.x line and install with Composer. NextPDF Core renders in your PHP process. Its published runtime targets include Octane, FrankenPHP, and RoadRunner. CI is configured to run PHPStan at Level 10.

The native HTML-to-PDF path runs in your PHP process. The Artisan extension uses Chrome over the DevTools Protocol for its named CSS features. The Cloudflare extension provides a separate edge-rendering path. Compare them on integrations.

Use nextpdf/backport for PHP 8.1–8.3, or for NextPDF Core on PHP 7.4–8.0. The native packages target PHP 8.4 or newer on the 8.x line. Review the exact package ranges on the backport page.

The native engine generates, signs, tags, and archives inside your PHP process. Those operations share one engine and document model. See why NextPDF for the architecture.