- What is h4cc/wkhtmltopdf-i386 and does it work with Laravel?
- It is a Composer package that bundles a precompiled 32-bit Linux (i386) build of the wkhtmltopdf command-line tool, not a PHP library. It exposes the executable under vendor/bin so Laravel PDF wrappers such as barryvdh/laravel-snappy or knplabs/knp-snappy can shell out to it. There is no service provider, no config file, and no PHP API - you only get a binary path.
- How do I install and wire up h4cc/wkhtmltopdf-i386 with Laravel Snappy?
- Require the package with Composer, then point the pdf.binary value in config/snappy.php at vendor/h4cc/wkhtmltopdf-i386/bin/wkhtmltopdf-i386. Make sure the file is executable and that the host is i386 Linux with the required shared libraries present. After that you can call PDF::loadView(...)->download() as usual.
- Does h4cc/wkhtmltopdf-i386 run on 64-bit Linux, Docker containers, or Apple Silicon?
- Not by default. The bundled file is a 32-bit x86 ELF and fails on amd64 hosts with an error such as cannot execute binary file unless you add i386 multiarch support and the full 32-bit Qt/X11 dependency set. It cannot run at all on musl/Alpine or arm64 hosts, including Apple Silicon laptops, so use an amd64 or arm64 binary or install wkhtmltopdf directly in the image.
- Is h4cc/wkhtmltopdf-i386 compatible with PHP 8.x and modern Laravel versions?
- Compatibility is a non-issue because the package contains no PHP code, so PHP and Laravel versions do not affect it. That is also the trap: Composer will never flag it as stale, so it can sit in composer.lock for years unnoticed. Judge it by the binary's age and the OS it targets, not by the framework version.
- Is h4cc/wkhtmltopdf-i386 still maintained, and is it safe for production?
- There is no active maintenance: the last release was 2018-01-15, the repository is unlisted, and there is no issue tracker or upstream to patch. composer audit will report nothing because the risk lives in an opaque ELF binary rather than in PHP code. Treat it as a legacy artifact and only use it with trusted templates in a controlled environment.
- What are the security risks of rendering HTML with this bundled wkhtmltopdf binary?
- The bundled rendering engine is an end-of-life QtWebKit fork for which this build has no CVE feed or patch path. If any user-submitted or third-party HTML reaches the renderer, you are exposing an unpatched browser engine to arbitrary input. Restrict it to developer-authored templates or move to a maintained rendering engine.
- What are good alternatives to h4cc/wkhtmltopdf-i386?
- Use the matching h4cc/wkhtmltopdf-amd64 or arm64 binary, install wkhtmltopdf through your Dockerfile or OS package manager, or move to a maintained engine such as Chromium via Browsershot or a hosted PDF API. The cleanest approach is to provision the executable in the infrastructure layer and keep binaries out of the Composer dependency graph.
- Why do large PDFs run out of memory with this i386 binary?
- A 32-bit process has roughly a 3 GB address-space ceiling, and wkhtmltopdf is memory-hungry on long documents. Reports that would succeed on the amd64 build can OOM on i386. If you must stay on 32-bit, cap document size, set process timeouts, and monitor memory.
- Does the LGPL-3.0 license on the bundled wkhtmltopdf binary affect my commercial application?
- LGPL-3.0 on the binary is a distribution obligation, not a use obligation, so shelling out to a separate process is generally the safest posture. Bundling it into a shipped appliance or on-prem image can trigger notice, license-text, and source-availability or relinking duties. Confirm whether the Qt linkage in this build is dynamic and get legal sign-off before distributing.
- How should I test PDF generation in Laravel when using this binary?
- Keep golden-file regression tests that render representative templates and compare outputs, since fidelity changes when the engine or binary changes. In CI, run on an i386-capable image or stub the PDF driver so tests do not depend on the binary being executable. Also assert that the configured binary path exists and is executable at boot.