Adding a header or footer to an HTML to PDF request seems like it should be easy. You enable the option, generate a PDF, and then nothing shows up. Or the page number works, but the footer overlaps the document. Or the logo disappears because the header uses an external <img src="...">. Or you reuse CSS classes from the main page, but the header and footer cannot see those styles.

This guide gives you working HTML to PDF header and footer examples for the cases developers ask about most often: page numbers, document titles, logos, dates, invoice footers, legal headers, margins, and Base64 templates. The examples use PDFBolt's Chromium-based API, so they also feel familiar if you have used Puppeteer or Playwright.

Payment processors generate their own invoices, but those come with generic layouts and zero branding. If you need an invoice PDF generator that matches your product's look, you have to build it yourself. With n8n and PDFBolt, you can set up a workflow that listens for payments, generates a branded PDF invoice from a template, emails it to the customer, and archives it in Google Drive. No custom code to deploy, no PDF rendering infrastructure to manage.

This guide walks through building that workflow from scratch using the PDFBolt community node. We cover two e-commerce triggers (Stripe and Shopify), data mapping with the Code node, email delivery, and cloud storage. Everything runs inside n8n's visual workflow builder.

PDF files have a tendency to grow far beyond what you'd expect. A report with a handful of images can easily hit 20 or 30 MB, making it impractical to email, upload, or store at scale. If you're working with Java and already using Apache PDFBox, you can compress and optimize these files programmatically using only open-source tools.

This post covers how to use PDFBox to compress PDF files in Java – from image recompression and downsampling to stream compression and resource cleanup.

Every SaaS product and e-commerce store eventually needs to generate invoice PDFs. Most teams start with a Word template, Canva, or a drag-and-drop builder, and that works fine for five invoices a month. Once you hit hundreds or thousands, you need something that runs without human input.

This guide covers three ways to generate invoice PDFs with an HTML to PDF API: raw HTML templates, Handlebars-based templates with dynamic data, and AI-generated templates. Complete with working code in Node.js and Python that you can run.

PDFs generated from HTML or web pages with images can get large. A product catalog with high‑resolution photos might produce a 15 MB file. An annual report with charts and screenshots could hit 8 MB. These sizes cause real problems: slow downloads, email attachment limits, expensive storage, and poor user experience. Manual compression through Acrobat or online tools doesn't work when you're generating hundreds of PDFs programmatically. You need compression that runs as part of your generation pipeline – and with a PDF compression API, you can apply it in the same request that creates the PDF.

For a one-off existing PDF, use the free PDF compressor. This guide covers compression during automated PDF generation.

PDF generation has always been a developer task. You write HTML, style it with CSS, configure page settings, and connect it to a rendering engine. The template alone can take days, especially for complex documents like financial reports with charts, multi-page contracts with conditional sections, or product catalogs with varied layouts. PDFBolt's AI PDF generator changes this workflow. Instead of writing code, you describe the document you want. The AI builds the PDF template, you connect your data, and the API produces PDFs.

Sending a regular PDF to a commercial printer is a gamble. Colors shift because RGB doesn't translate cleanly to ink on paper. Fonts render differently or go missing. Transparent elements break at the RIP stage, leaving white boxes where gradients should be. Print shops deal with these problems daily. The fix is a set of ISO standards called PDF/X that enforce strict rules about color spaces, fonts, and transparency. This article covers what PDF/X-1a and PDF/X‑4 are, when to use each, and how to generate compliant files programmatically through an API.

Most n8n workflows eventually need to produce documents – invoices after purchases, scheduled reports, certificates for course completions. Setting up PDF generation inside n8n usually means dealing with HTML rendering quirks or managing headless browser instances. PDFBolt's API plugs directly into n8n's HTTP Request node, so you send template data and get back a finished PDF. No browser setup, no rendering config – just an API call.

PDFBolt Templates is a new feature that separates design from data in PDF generation. Instead of rebuilding HTML for every document, create reusable layouts once and populate them with dynamic data. Invoices, certificates, reports – Templates make your workflow faster and easier to maintain.

PHP remains the language behind most of the web, and PDF generation is a common task in PHP applications – invoices, reports, certificates, shipping labels. The library you pick affects performance, maintenance cost, and how much CSS/HTML you can reuse. The PHP ecosystem has several approaches: pure PHP HTML to PDF conversion, programmatic document construction, and browser-based rendering. This guide compares the most popular PHP PDF libraries with Packagist download numbers, working code examples, and a side-by-side feature table so you can choose the right fit for your project.