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:

composer require bladepdf/laravel

Add an API key to your environment:

BLADEPDF_API_KEY=your_api_key

Configuration is auto-discovered. Publish it only when you need to change timeouts, retries, SSL verification, or asset resolution:

php artisan vendor:publish --tag=bladepdf-config

#Verify webhooks

Store the signing secret shown when you create a BladePDF webhook endpoint:

BLADEPDF_WEBHOOK_SECRET=whsec_...

Then verify the request before decoding or processing its payload:

use BladePDF\Laravel\Webhooks\SignatureValidator;
use Illuminate\Http\Request;

public function handle(Request $request)
{
    abort_unless(SignatureValidator::isValid($request), 401);

    $event = $request->json()->all();

    // Handle the verified event...
}

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:

composer require bladepdf/spatie-laravel-pdf-driver

See the Spatie Laravel PDF integration guide for default-driver configuration, supported options, queues, and compatibility notes.

#30-second example

use BladePDF\Laravel\Facades\BladePDF;

return BladePDF::fromView('pdf.invoice', ['invoice' => $invoice])
    ->render()
    ->download("invoice-{$invoice->number}.pdf");

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.

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.

#Documentation

Read the full documentation →

Start with the quickstart, then explore the asset pipeline, Blade templates, async renders, and webhooks.

#Supported features

#Upgrading from 1.x

Version 2 delegates all framework-independent rendering, HTTP transport, asset resolution, results, and exceptions to bladepdf/php. Normal facade calls such as BladePDF::fromView() and BladePDF::fromHtml() remain unchanged.

Update both the package and exception imports:

composer require bladepdf/laravel:^2.0 --with-all-dependencies

use BladePDF\Exceptions\BladePdfException;
use BladePDF\Laravel\Webhooks\SignatureValidator;

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.