Screenshot to PDF

Combining screenshots into a single PDF is one of those small office tasks that comes up surprisingly often. Sales people want to package a conversation thread for their CRM. Designers want to deliver a series of mockups as one shareable file. Customer-support agents need to attach a sequence of error messages to a ticket. Auditors and compliance teams need to preserve evidence in a non-editable, single-document format. Students bundle screenshots of equations from a textbook into a study guide. The common thread is the same: many images, one delivery format, ideally PDF (because PDF is the universal "looks the same everywhere" container).

What makes a screenshot PDF "good"

A well-built screenshot PDF has three properties: consistent page size (so scrolling feels uniform), preserved readability (text in screenshots stays crisp), and reasonable file size (small enough to email). Most people optimise for one of these and accidentally sacrifice the other two. The default settings here aim for all three: A4 portrait, Contain fit with 20pt margin, JPEG embed at quality 92. The result is PDFs typically 30-60% smaller than what most online "image to PDF" services produce because they default to PNG embedding (which never compresses photographic detail).

A 10-screenshot iPhone capture (1290×2796 each) compressed with the default JPEG embed comes out to about 4-7 MB as PDF — small enough for any email or chat attachment.

When to use JPEG vs PNG embed

Use JPEG embed (default) for screenshots of photos, design mockups, and general-purpose content. The 30-50% file-size saving over PNG is almost always worth the slight quality cost. Use PNG embed for screenshots dominated by text (terminal output, code), high-contrast line art (architectural diagrams), or anything where you want exact pixel preservation. A PNG-embedded multi-page PDF of code screenshots is much larger but the text stays perfectly sharp at any zoom level — important for things like development documentation.

The APAC document-delivery landscape

Screenshot-to-PDF is a daily operation in APAC business environments. Singapore, Hong Kong, Malaysia, Australia see it heavily in financial-services compliance — chat logs from WhatsApp, WeChat, or Telegram captured as screenshot bundles, packaged as PDF, archived for regulatory retention. India's booming BPO sector turns customer-interaction screenshots into PDF case files at massive scale. Japan, South Korea, Taiwan have strong evidence-archival cultures where everything from Slack conversations to system error dialogs gets PDFed for paper trails. China has its own twist: WeChat conversations are often the entire customer relationship, so screenshot-to-PDF tools are part of standard sales workflows; the format also matters because PDF can be passed cleanly through Tencent's enterprise document systems. Indonesia, Vietnam, Philippines, Thailand see massive use among gig-economy workers documenting deliveries, ride-hailing trips, and freelance task completions — screenshot timestamp, location, customer message, package photo all bundled as one PDF for dispute resolution. Across the region, the most-asked question is the same: "how do I do this without uploading my customer's data to an unknown server?" Self-hosted browser tools are the only honest answer.

What this tool doesn't do (yet)

It doesn't add captions or annotations to pages (use a PDF editor for that). It doesn't OCR screenshot text into selectable form (the embedded image stays an image). It doesn't generate a table of contents or bookmarks. It doesn't password-protect the output (pdf-lib supports it but the UX of password input is best left to a dedicated tool). It doesn't crop or rotate images before embedding — pre-process those in our Image Format Converter or other tools first. For all of those, the current workflow is: get your screenshots PDF-ready here, then run the output through a dedicated PDF editor.