Skip to content

Integrations

NextPDF extensions connect the core Portable Document Format (PDF) engine to application frameworks, browser renderers, edge services, build tooling, and legacy migrations. Each extension section follows the same manual structure: overview, install, quickstart, configuration, application programming interface (API), developer guide, production usage, security, and troubleshooting.

ExtensionPackageUse it whenMain section
Laravelnextpdf/laravelUse it when you build Laravel applications and need container bindings, a facade, responses, and queue jobs.Laravel
Symfonynextpdf/symfonyUse it when you build Symfony applications and need a bundle, dependency injection wiring, Messenger jobs, and Hypertext Transfer Protocol (HTTP) responses.Symfony
CodeIgniternextpdf/codeigniterUse it when you build CodeIgniter 4 applications and need services, a library wrapper, responses, and queue jobs.CodeIgniter
Artisannextpdf/artisanUse it when you need Chrome DevTools Protocol (CDP) Hypertext Markup Language (HTML) rendering, page import, or low-level PDF inspection utilities.Artisan
Cloudflarenextpdf/cloudflareUse it when you render through Cloudflare Browser Rendering, protect API access, or archive PDFs to R2.Cloudflare
Gotenbergnextpdf/gotenbergUse it when you convert office documents or HTML through a Gotenberg service.Gotenberg
TCPDF compatibilitynextpdf/compat-legacyUse it when you migrate TCPDF-shaped application code to NextPDF without a full rewrite.TCPDF compatibility
Backport Buildernextpdf/backport-builderUse it when you maintain release artifacts for older PHP: Hypertext Preprocessor (PHP) runtimes.Backport Builder
NeedStart hereOperational note
Framework response helpersLaravel, Symfony, or CodeIgniterThe framework package owns container and response integration; core owns document authoring.
Pixel-oriented HTML renderingArtisan or CloudflareChoose Artisan for host-local Chrome CDP. Choose Cloudflare when rendering belongs at the edge.
Office conversionGotenbergTreat Gotenberg as an external service boundary with timeout, size, and server-side request forgery (SSRF) controls.
Legacy TCPDF migrationTCPDF compatibilityCheck the method coverage table before you assume a legacy call is supported.
Older PHP distributionBackport BuilderBuild tooling only; do not install it as an application runtime dependency.

Each extension section contains these page types:

PagePurpose
overviewProduct boundary, target audience, supported workflows, and limitations.
installInstallation commands and required runtime dependencies.
quickstartMinimal working flow with a copyable first result.
configurationSupported config keys, environment variables, defaults, and effects.
apiPublic classes, methods, parameters, defaults, return values, and exceptions.
developer-guideExtension architecture, lifecycle, extension points, and code organization.
production-usageDeployment, reliability, performance, worker safety, and observability.
security-and-operationsTrust boundaries, safe defaults, secrets, file access, and operational controls.
troubleshootingSymptoms, diagnostics, likely causes, and corrective actions.

API tables use the same columns across the manual, so you can compare packages without learning a new layout.

ColumnMeaning
SymbolFully qualified class, method, endpoint, command-line interface (CLI) command, or config object.
ParametersName, type, required status, default, and accepted values.
Default behaviorWhat happens when you omit optional input.
ReturnsReturn type or output artifact.
Throws or fails withException type, HTTP status, validation failure, or operational failure mode.
NotesSecurity, worker-safety, compatibility, or performance detail.

The English source is written for later localization: short sections, stable headings, explicit nouns, no idioms, and tables for repeated structures. Keep method names, config keys, CLI flags, and exception names in code formatting on new API pages so translation tools preserve them.