The Hidden Complexity of Client-Side PDF Generation

Generating a PDF is often viewed as a trivial task—a simple "print to PDF" or a call to a library. However, when the requirement shifts to generating these documents entirely on the client side while maintaining high-fidelity, text-selectable content, developers enter a world of surprising complexity. The journey of building SDocs highlights a fundamental tension in web development: the gap between how we render content for screens (HTML/CSS) and how we define documents for fixed-layout formats like PDF.

The Challenge of Text Selectability

One of the most common frustrations for users is the "dead" PDF—a document that looks correct but behaves like an image, where text cannot be selected, searched, or copied. Achieving true text selectability in a client-side generated PDF requires more than just placing characters on a page; it requires a precise mapping of glyphs to coordinates and the inclusion of a text layer that the PDF viewer can interpret.

As noted by developers in the community, this is one of the "pandora boxes" of web development, akin to the nightmare of creating cross-client email templates. The difficulty lies in the fact that PDFs are not responsive; they are fixed-layout documents. Translating the fluid nature of a web layout into a static coordinate system while preserving the relationship between the visual glyph and the underlying character code is a non-trivial engineering feat.

The "PDF Hell": Why it's so Difficult

Beyond the initial generation, the PDF format introduces several systemic issues that make it a fragile tool for modern data exchange:

1. The Copy-Paste Nightmare

Even when text is selectable, the experience is often broken. Because PDFs focus on visual positioning rather than semantic structure, copying text often results in fragmented sentences, missing spaces, or characters appearing in the wrong order.

"You show how much insane work is needed just to make text selectable with glyph mappings, layout, links, code blocks, rendered styles, etc. But once you copy from that PDF, most viewers still only expose raw text, and often broken raw text at that..."

2. Layout Rigidity

Software engineers often underestimate the complexity of GUI and layout engines. Rendering a table that spans multiple pages, for instance, requires complex logic to handle headers, footers, and row splitting—problems that the paged.js project attempts to solve by applying open web standards to paged media.

3. The Editing Gap

Editing an existing PDF is notoriously difficult. Simple tasks, such as filling in a checkbox, can fail silently or require complex scripts to manipulate the underlying PDF structure, as the visual representation often diverges from the actual data layer.

Alternative Approaches and Solutions

Given the complexities of native PDF generation, several alternative strategies have emerged:

• WASM-based Compilers: Some developers suggest using tools like Typst, which can be compiled into WebAssembly (WASM) to run locally in the browser, providing a more robust pipeline for generating high-quality, selectable PDFs.
• Intermediate Formats: Converting Markdown to a stable intermediate format like LaTeX or using Pandoc can provide a more dependable rendering pipeline, though these often introduce heavier dependencies.
• HTML-to-PDF Bridges: Libraries that render rich text into a 2D canvas context and then proxy that context to a PDF library can simplify the process of maintaining visual fidelity.
• The "Vibecoding" Approach: Some users have found success by bypassing PDFs entirely for internal tools, converting PDFs to HTML bundles and using scripts to inject variable data, effectively treating the PDF as a visual template rather than a document format.

Conclusion: Is the PDF the Right Tool?

The struggle to generate perfect PDFs often leads to a broader philosophical question: should we be using PDFs at all for digital-first content? While they are indispensable for printing and legal archiving, they are fundamentally ill-suited for the responsive, searchable, and accessible nature of the modern web. For books, scientific papers, and catalogs, standards like HTML and EPUB offer far superior flexibility and accessibility, provided that the ecosystem of readers continues to evolve.