Fullbleed 2.4: six PDFs you can inspect and reproduce
Choosing a PDF library is easier when you can inspect its output before writing the integration. Fullbleed's rebuilt documentation now includes six downloadable PDFs, generated with the public 2.4.0 Python wheel, alongside runnable source and verification details.
Fullbleed is an MIT-licensed Python and Rust engine for invoices, reports, statements, and other print documents. Install it with python -m pip install fullbleed, then start with the first-PDF quickstart.
Pick a document that resembles yours
Styled invoice: an Acme invoice built from CSV with reusable components and decimal calculations in the application.
Invoice from JSON: one page with an embedded font, an item table, and checks for expected content.
Business report: five pages with headings and content-driven pagination.
Tagged service notice: one semantic page using the pdfua1 profile, with profile-marker and text checks.
Fixed variable-data output: 100 statement records on 100 pages, changing names, IDs, and balances.
Reflowing variable-data output: 20 records over 41 pages, allowing each record's content to change its page count.
The example gallery links the PDFs, previews, HTML/CSS where applicable, and their source projects. Sample data is fictional.
Inspect the output, then change the input
Start with the closest sample. Check its page breaks, table layout, text selection, fonts, and metadata against what your application needs. Then run the source and replace the sample data with a small synthetic record of your own.
The five compact workflow examples can be run together with python examples/agent_workflows/run_examples.py --out output/examples --json from a source checkout after installing Fullbleed. The Acme invoice project includes its own CSV data contract and build instructions.
For repeated records, the variable-data guide explains when to use fixed bindings and when content needs to reflow. The invoice guide covers the path from structured data to a document.
What the verification record tells you
The gallery verification record retains page counts, file hashes, and the scope of the checks. The five compact workflows passed their expected-content and internal inspection checks.
Standards conformance requires the applicable validation on the exact document you deliver. The accessibility workflow and 2.4.0 release evidence describe the checks and their limits.
Bring a real document problem
Try a sample, change one input, and see how it behaves. Share questions and document examples in GitHub Discussions. If something breaks, an issue with a small runnable reproduction gives us a useful starting point.
