Weave Code
Fpdi Tcpdf Laravel Package
setasign/fpdi-tcpdf
Lightweight bridge between FPDI and TCPDF that lets PHP developers import pages from existing PDF files directly into new TCPDF documents. Handy for merging files, adding stamps or watermarks, reordering pages, and assembling reports without rebuilding layouts from scratch.
ABANDONED! A kind of metadata package for Composer with fixed dependencies for the latest versions of FPDI and TCPDF.
Frequently asked questions about Fpdi Tcpdf
- What is setasign/fpdi-tcpdf used for?
- It is a Composer metapackage that pins setasign/fpdi and tecnickcom/tcpdf to a mutually compatible version pair. The real PDF functionality lives entirely in those two libraries, including the TCPDF bridge class setasign\Fpdi\Tcpdf\Fpdi. It lets developers import pages from existing PDFs into new TCPDF documents for merging, stamping, watermarking, or report assembly, but the metapackage itself ships no PHP code.
- Is setasign/fpdi-tcpdf abandoned?
- Yes. It is explicitly marked abandoned and archived, with the last release dated 2020-02-19. There is no active maintainer, no CVE response process, and no verified PHP 8.x fixes. You should not introduce it into a new Laravel project.
- How do I install setasign/fpdi-tcpdf in Laravel?
- Historically you would run composer require setasign/fpdi-tcpdf, and there is no service provider, facade, or config file to register. In a modern Laravel application you should instead require setasign/fpdi and tecnickcom/tcpdf directly. The resulting class names and namespaces are identical, so application code does not change.
- Does setasign/fpdi-tcpdf work with Laravel 10, 11, and PHP 8.2 or 8.3?
- The package has no Laravel coupling at all, so any compatibility issues come from its frozen FPDI and TCPDF constraints. PHP 8.x support is unverified for the metapackage, and its pinning can hold your project on outdated TCPDF builds with dynamic-property deprecations. Requiring current stable versions of setasign/fpdi and tecnickcom/tcpdf directly is the safer path.
- Should I replace setasign/fpdi-tcpdf with setasign/fpdi and tecnickcom/tcpdf?
- Yes. Remove setasign/fpdi-tcpdf from composer.json and add setasign/fpdi:^2.6 plus tecnickcom/tcpdf:^6.7 at current constraints. Then run composer update setasign/fpdi tecnickcom/tcpdf --with-dependencies and verify that no other package depended on the metapackage's exact pins. This is a dependency swap, not a code migration.
- Does removing setasign/fpdi-tcpdf require code changes?
- No, because FPDI 2.x already bundles the TCPDF bridge class setasign\Fpdi\Tcpdf\Fpdi. The metapackage contributes no source files, so class names, namespaces, and method calls remain the same after you declare the underlying libraries directly. Run your existing PDF import, stamping, and output tests to confirm behavior is unchanged.
- Can setasign/fpdi-tcpdf merge PDFs or add watermarks?
- Merging, watermarking, page reordering, and report assembly are capabilities of FPDI and TCPDF, not of the metapackage. FPDI imports pages from existing PDF files into a TCPDF document where you can overlay stamps or watermarks. Because the metapackage ships no code, you get exactly the same functionality by depending on the two libraries directly.
- What are the security risks of keeping setasign/fpdi-tcpdf?
- Its frozen constraints can pin your project to outdated TCPDF and FPDI releases, blocking security patches and creating unexplained lockfile drift. TCPDF parses untrusted PDFs and emits documents, so stale versions carry exposure to memory exhaustion and historically reported file-inclusion and XSS classes of issues. The package also creates a false sense of maintenance because the vendor explicitly disclaims support.
- Does setasign/fpdi-tcpdf support PDF/A or digital signatures?
- The metapackage adds no compliance features; TCPDF has only partial PDF/A and signing support, and importing pages with FPDI can break PDF/A conformance. If you need PDF/A or digital signatures in Laravel, evaluate TCPDF alone or a dedicated library before committing. Also confirm whether source templates are user-supplied or encrypted, since FPDI cannot import encrypted or some compressed-object PDFs.
- What are the alternatives to setasign/fpdi-tcpdf?
- The direct replacement is setasign/fpdi plus tecnickcom/tcpdf, which gives the same API with maintained versions. For HTML-to-PDF work in Laravel, developers often compare barryvdh/laravel-dompdf and laravel-snappy. Choose based on whether your requirement is page import and merging, template stamping, PDF/A, or digital signatures rather than on the metapackage.
Weaver
How can I help you explore Laravel packages today?