Slim Jim: A Lean Html to PDF Converter

Slim Jim is an ultra-fast, stateless compilation bridge tailored for high-load, simple-layout PDF generation. It translates a highly optimized, simplified HTML subset directly into native ReportLab canvas instructions, bypassing the massive resource overhead of headless browsers.

Detailed Benchmark and Source Code

TLDR: Conteineraised Slim Jim generates 1000 A4 pdf documents in about 1.6 seconds.

You can find detailed benchmark results and methodology here: Slim Jim Benchmark Gauntlet

Repository: Source Code

About Slim Jim

When we think about converting HTML to a PDF, we usually have a very simple expectation in our head: the generated document should mirror the source markup 1-to-1. In reality, the underlying process is incredibly complex and far less straightforward than it looks at first glance.

Over decades of open-source and commercial development, the engineering community has provided several powerful ways to bridge this gap. Generally, these solutions fall into two main camps:

1. Dedicated PDF Manipulation Libraries: Tools like iText or commercial equivalents largely support HTML-to-PDF pipelines natively. However, they carry distinct trade-offs. First, they come with licensing prices that most teams find surprisingly high for a standalone utility. Second, you introduce a heavy "black box" into your application layer, making your architecture entirely dependent on a third party for support, security updates, and bug fixes.
2. The Unvetted Open-Source Wrappers: The internet is full of obscure, community-maintained Python wrappers that promise easy HTML-to-PDF conversions. Under the hood, however, these packages almost always rely on outdated system binaries (like wkhtmltopdf, which was archived and deprecated years ago). Introducing these to an enterprise application means dragging a massive, unmaintained dependency tree into your codebase—often requiring custom Linux OS packages to be installed on your host container. For corporate security teams, these unvetted "black box" system binaries are an immediate red flag that will never pass a modern compliance audit.
3. Headless Browser Emulation: Tools like Puppeteer, Playwright, or Chromium load the entire DOM into a headless browser instance and render the visual snapshot out to a PDF. This approach is highly effective and easily handles complex HTML, grid layouts, and embedded media without structural limitations. But from an infrastructure standpoint, the process is as heavy as it gets. Running an entire web browser runtime to handle thousands of requests in a high-load system introduces massive resource overhead and leaves a staggering amount of work on the table for optimization.

This exact bottleneck sparked the original requirements for what became Slim Jim: a high-load, simple-layout PDF generation engine tailored for specific, high-velocity use cases. When your goal is to generate hundreds of thousands of "primitive" files—like barcodes, shipping labels, thermal tags, or picking receipts in a fast-paced warehouse—you don't need a heavy browser layout engine or an expensive enterprise suite just to draw text and vector shapes. Slim Jim is a lean, tailored solution for exactly these situations.

It acts as an ultra-fast, stateless compilation bridge that translates a highly optimized, simplified HTML subset directly into native ReportLab canvas instructions.

Core Architectural Features:

• Engineered for AWS Lambda & Serverless: By keeping its dependency tree razor-thin (FastAPI, BeautifulSoup, ReportLab), Slim Jim achieves an incredibly small CPU and memory footprint. You don't need a heavy, multi-gigabyte container image or a costly, always-on server instance. It is lightweight enough to boot instantly on AWS Lambda, effectively erasing cold-start penalties and eliminating infrastructure waste where costs quickly add up.
• Drop-in Codebase as Feature: Because the core engine logic is exceptionally compact and modular, you aren't forced to maintain Slim Jim as an isolated, standalone microservice network dependency. It is simple enough to be cleanly pasted straight into your existing Python backend codebase as an internal application utility or shared module without bloating your repository or muddying your architecture.
• Zero Network or Disk Delays: To maintain extreme processing speeds, Slim Jim operates entirely in an air-gapped, inline-only environment. All structural graphics, 1D logistics barcodes, and logos must be passed directly inside the request stream as inline attributes or Base64 data strings. The service never makes outbound network calls to fetch external assets and never writes temporary files to a disk.
• No Silent Layout Failures: Most document generators try to be overly resilient when encountering bad data—silently stripping out unparseable code blocks or writing a broken, half-empty layout. Slim Jim handles boundaries strictly. If an image stream is corrupt or a layout constraint is broken, it fails fast and triggers an immediate HTTP 500 panic. This guarantees that unreadable or corrupted barcodes never silently pollute your physical fulfillment pipeline.
• ReportLab Under the Hood: The low-level PDF building blocks, canvas coordinates, and flowable engines are fully abstracted behind a clean Strategy pattern. While this isolates the rest of your application code from layout quirks, it does mean the compiler engine is tightly coupled to ReportLab's native behavior. If you want to tweak or expand the visual components, you will need to spend a little quality time with the official ReportLab documentation.