A common pattern in .NET shops: teams already use Playwright for end-to-end testing and discover its page.Pdf() method. The logic seems sound—we're already managing Playwright for tests, why add another dependency for PDF generation? One team ran this experiment: they measured first-render time (Playwright: 1.2s, IronPDF: 0.8s) and concluded Playwright was "close enough." Then they deployed to production. Under load, the testing-first architecture showed: full browser contexts per request consumed 3x memory, no renderer reuse optimization, and browser lifecycle management added complexity. The tool worked; the architecture didn't scale. Playwright is Microsoft's browser automation framework designed for comprehensive testing across Chromium, Firefox, and WebKit. The library manages browser processes, provides testing utilities (assertions, fixtures, reporters), and includes PDF generation as an ancillary feature through the browser's print-to-PDF functionality.…