BladePDF for Laravel

Production-ready Laravel PDF generation from the Blade views you already use.
Generate beautiful PDFs without installing Chromium, maintaining browser workers, or exposing local assets.

Browsershot and Puppeteer give you browser-level control. Spatie's Laravel PDF package gives you a choice of rendering drivers. **BladePDF is for Laravel teams that want the familiar Blade workflow while the browser lifecycle, asset uploads, concurrency, storage, and async delivery are managed for them.** ## Installation Install the package: Add an [API key](https://app.bladepdf.com) to your environment: Configuration is auto-discovered. Publish it only when you need to change timeouts, retries, SSL verification, or asset resolution: ## Verify webhooks Store the signing secret shown when you create a BladePDF webhook endpoint: Then verify the request before decoding or processing its payload: The validator checks the signature against the exact raw request body and rejects timestamps outside a five-minute tolerance by default. Pass a secret as the second argument for a per-request webhook, or publish the configuration to customize `webhook_tolerance`. ## Using Spatie Laravel PDF? Install the dedicated driver to keep the `Spatie\LaravelPdf\Facades\Pdf` API while BladePDF provides the managed Chromium backend: See the [Spatie Laravel PDF integration guide](https://docs.bladepdf.com/integrations/spatie-laravel-pdf) for default-driver configuration, supported options, queues, and compatibility notes. ## 30-second example That is the complete synchronous flow: BladePDF renders the local view, resolves referenced assets, generates the PDF, and returns a Laravel download response. ## Features - ✅ Local Laravel Blade views and raw HTML - ✅ Tailwind CSS, plain CSS, and print styles - ✅ Local images, SVG, stylesheets, and custom fonts - ✅ Automatic asset discovery and request-scoped uploads - ✅ Headers, footers, backgrounds, and custom page sizes - ✅ JavaScript rendering and external assets on supported plans - ✅ Cloud Blade templates and hosted assets - ✅ Stored PDFs with signed retrieval URLs - ✅ Asynchronous rendering with signed webhooks - ✅ Fluent Laravel API with typed result objects ## Why BladePDF? Running Chromium is straightforward in development. Production adds browser installs, process crashes, memory pressure, security updates, queue capacity, and asset URLs that the renderer can actually reach. | Operational concern | Self-hosted Chromium | BladePDF | | --- | --- | --- | | Chrome and Node installation | You install and pin them | Managed | | Browser crashes | Your workers absorb them | Isolated from your app | | Memory and process tuning | Your responsibility | Managed render capacity | | Local CSS, images, and fonts | Expose or rewrite them | Discovered and uploaded automatically | | Queue workers | Build and operate them | Async API with signed webhooks | | Scaling | Add workers and replicas | Increase managed concurrency | | Browser and security updates | Your maintenance window | Managed | | Template operations | Build your own workflow | Local views plus cloud templates | > Focus on generating PDFs instead of maintaining browser infrastructure. BladePDF is a hosted API, so it requires network access and an API key. Choose a self-hosted driver when offline rendering, data locality, or low-level browser control is more important than operational simplicity. ## Example PDFs Each example includes a production-quality Blade template, realistic sample data, a rendered preview, and a focused README. | [Invoice](examples/invoice) | [Event ticket](examples/ticket) | | --- | --- | | [](examples/ticket) | | [Certificate](examples/certificate) | [Business report](examples/report) | | [](examples/report) | ## Documentation

Read the full documentation →

Start with the [quickstart](https://docs.bladepdf.com/quickstart), then explore the [asset pipeline](https://docs.bladepdf.com/asset-pipeline), [Blade templates](https://docs.bladepdf.com/blade-templates), [async renders](https://docs.bladepdf.com/api/async-renders), and [webhooks](https://docs.bladepdf.com/api/webhooks). ## Supported features | Feature | Supported | Notes | | --- | :---: | --- | | Local Blade templates | Yes | Render existing Laravel views with `fromView()` | | Raw HTML | Yes | Send prepared markup with `fromHtml()` | | Tailwind and plain CSS | Yes | Local stylesheets are resolved automatically | | Images and SVG | Yes | Local files are uploaded per render; remote URLs are preserved | | Custom fonts | Yes | WOFF2, OTF, TTF, and CSS `@font-face` references | | Headers and footers | Yes | Blade views or raw HTML for local HTML renders | | Backgrounds | Yes | Use `showBackground()` or `transparentBackground()` | | Landscape and custom paper | Yes | A3/A4 and any width/height supported by Chromium | | Page ranges and margins | Yes | Fluent helpers plus raw PDF options | | JavaScript rendering | Yes | Available on supported plans | | Async rendering | Yes | Stored PDFs plus a `202 Accepted` submission | | Signed webhooks | Yes | `pdf.rendered` and `pdf.failed` delivery events | | Cloud Blade templates | Yes | Publish templates in the dashboard and render by id | | Stored PDFs | Yes | Retrieve the signed URL from the result or webhook | | Laravel versions | 11-13 | PHP 8.2 or newer | ## Upgrading from 1.x Version 2 delegates all framework-independent rendering, HTTP transport, asset resolution, results, and exceptions to [`bladepdf/php`](https://github.com/bladepdf/bladepdf-php). Normal facade calls such as `BladePDF::fromView()` and `BladePDF::fromHtml()` remain unchanged. Update both the package and exception imports: The old `BladePDF\Laravel\BladePdfClient`, `BladePDF\Laravel\Support\*`, `BladePDF\Laravel\Exceptions\*`, and Laravel `RenderSubmission` classes were removed. Local automatic asset access is now constrained to `public_path()` and `storage_path('app')`; add intentional directories to the published `asset_roots` configuration. `base_path()` is deliberately not allowed by default. Spatie driver 1.x is paired with this package's 1.x line. Use `bladepdf/spatie-laravel-pdf-driver:^2.0` with Laravel adapter 2.x. ## License BladePDF for Laravel is open-source software licensed under the [MIT License](LICENSE).