Managed PDF infrastructure for Laravel

BladePDF renders production-ready PDFs from your existing Blade views without making your Laravel deployment responsible for Chromium, Node.js, Docker, browser workers, or publicly reachable assets.

Why BladePDF exists

Most Laravel developers do not actually want to operate Chromium. They need reliable invoices, reports, labels, and exports. A browser that is easy to launch locally becomes a production system that needs installation, security updates, memory limits, crash recovery, queues, scaling, monitoring, and an asset path the renderer can reach.

BladePDF moves that rendering layer out of your application infrastructure. Your app keeps preparing data and rendering Blade; BladePDF manages the isolated browser work, transfers referenced local assets, records the result, and can store or deliver the finished PDF asynchronously.

What the managed service includes

BladePDF gives your application a fluent rendering API and a dashboard for managing templates, reusable assets, render history, stored PDFs, and signed webhook delivery.

Choose where the document content comes from, pass the data needed to render it, configure the PDF options, and decide how the result should be returned or stored.

Choose a source

One render contract

Once you choose a source, the rest of the API stays the same. You can set metadata, PDF options, request-scoped asset overrides, persistence, and then call render() or async().

 1BladePDF::fromView('pdf.invoice', ['invoice' => $invoice]);
 2
 3BladePDF::fromHtml($html);
 4
 5BladePDF::fromTemplate('invoice.standard', [
 6    'invoice' => $invoice->toArray(),
 7]);

All three can continue with the same document options:

 1return BladePDF::fromTemplate('invoice.standard', $context)
 2    ->reference($invoice->uuid)
 3    ->format('A4')
 4    ->margins(top: '16mm', right: '12mm', bottom: '18mm', left: '12mm')
 5    ->showBackground()
 6    ->storePdf()
 7    ->render()
 8    ->download("invoice-{$invoice->number}.pdf");

Basic example

The public Laravel API is intentionally small: pick the source, set metadata/options, then call render() and use the returned result.

 1use BladePDF\Laravel\Facades\BladePDF;
 2
 3Route::get('/invoices/{invoice}/pdf', function (Invoice $invoice) {
 4    return BladePDF::fromView('pdf.invoice', [
 5        'invoice' => $invoice,
 6    ])
 7        ->reference($invoice->uuid)
 8        ->format('A4')
 9        ->showBackground()
10        ->render()
11        ->download("invoice-{$invoice->number}.pdf");
12});

Cloud templates

Cloud templates let you update document markup from the dashboard without deploying your Laravel app. Your application sends the template id and a JSON object used as context.

 1return BladePDF::fromTemplate('invoice.standard', [
 2    'invoice' => $invoice->toArray(),
 3    'customer' => $invoice->customer->toArray(),
 4])
 5    ->reference($invoice->uuid)
 6    ->storePdf()
 7    ->render()
 8    ->response('invoice.pdf');

What happens after a request

Core concepts

Next steps