How to Turn Screenshots Into a PDF for a Bug Report

Screenshots to PDF for a bug report is crop, convert, merge, compress, redact with your eyes. DevOkk will not OCR the shot and will not auto-censor the PII. It will wrap images in a PDF in the tab.

Single-format how-tos already exist: How to convert PNG screenshots to PDF, How to combine images into a single PDF. This is the workflow around a ticket.

Capture without capturing secrets

Crop before you convert. Session IDs in the URL bar, JWT in a query, customer names in a table - crop or fake the data. What not to paste into online developer tools applies to images too. A PDF merger is another paste.

OS tools: Snipping Tool, screenshot to clipboard, browser full page. Prefer the smallest rectangle that proves the bug.

PNG for UI, then PDF

Keep PNG. PNG to PDF or Image to PDF. Several files: convert each, then PDF Merge in order. PDF Sort if you merged wrong.

JPG screenshots of UIs look cheap and unreadable. JPG to PDF is for camera photos of a projector, not for Chrome.

Order and labels

Filename 01-empty-state.png, 02-after-click.png. Merge in that order. PDF Page Numbers. First page can be a PNG of the text repro steps if your audience will not open the ticket.

Size

4K × 5 pages is a 20 MB PDF. Crop. Then PDF Compressor. Check that error text is still selectable-looking (it may be pixels). If it becomes mush, split: send steps as text, PDF only the one shot that matters.

Email caps: Email attachment size limits.

Do not use a cloud “PDF from images” ad

Same rule as Are online PDF converters safe?. Staging data is still data.

A worked example: checkout 500

Three PNGs: cart, payment error toast, network panel (status 500, redact the Authorization header in the screenshot - crop it). Convert PNG to PDF ×3. Merge. Page numbers. Compress. Attach to Jira and email. Never ILovePDF.

If the network panel was a HAR, do not PDF the HAR; it is worse. Cropped PNG of the status line is enough.

After they say “can’t repro”

Add a fourth shot of the environment (browser, URL host). Merge again or send a second one-page PDF. Do not unlock a 40-page session recording as images.

The general combine article is the tool mechanics. This page is so the PDF is a bug report, not a data leak. PNG to PDF and PDF Merge are the two clicks after you cropped.

Red rectangles and arrows

Draw on the PNG in any editor before PDF if you need “this button.” Once it is a PDF, you are in PDF-annotation land (Acrobat). For bug reports, annotate the raster. Then wrap.

Light and dark mode

A bug that only happens in dark theme needs a shot in dark theme. Two PDFs or two pages. Do not rely on “it was dark on my machine.”

Mobile vs desktop

Two viewports, two pages. Merge. Say which is which in the filename and on page 1.

Accessibility of the report itself

If the only repro is a screenshot of text, paste the text in the ticket too. Screen-reader-using teammates cannot OCR your PDF reliably. The PDF is for layout bugs.

Video vs PDF

A 30-second Loom is better for timing bugs. PDF is better for “this pixel is wrong” and for email-only vendors. Do not Convertio a Loom into a 200-page PDF.

PNG to PDF and PDF Merge are the two clicks after you cropped. Crop is the security step.

Full-page captures

Full-page screenshot extensions produce tall PNGs. PDFs of those become unreadable on a phone. Slice into overlapping windows, or crop to the failing widget. Merge the slices with PDF Merge.

Annotations after PDF

If you must highlight after merge, you are in Acrobat territory. Prefer highlight on the PNG. If the vendor only accepts PDF comments, say so - that is a suite job, not DevOkk.

Repro matrix

Browser × OS shots as separate pages, labeled in the filename before convert so the PDF outline matches. PDF Page Numbers after.

PII in reflections and screens

A laptop in the background of a “webcam bug” shot can show Slack. Crop. The PDF merger will not do ethics for you.

Capture tools that fight you

Windows Snipping Tool and macOS screenshot to clipboard are enough. Browser full-page extensions produce a strip nobody can read on a phone. Prefer the smallest rectangle that proves the bug. If you must full-page, slice overlapping windows before PNG to PDF.

Retina captures are 2× pixels. They make sharp PDFs and huge email. Crop first, then wrap, then PDF Compressor. Do not JPEG a UI shot to “save size” if labels must stay readable.

iPhone screenshots can be HEIC. Convert before PDF or Windows PMs bounce: HEIC to PNG. Why iPhone photos won’t open on Windows.

Console, network, and HAR

A screenshot of the console is fine if you crop tokens. Pasting the error text in the ticket is better. A HAR in a PDF is a gift to whoever opens the ticket - cookies, Authorization, request bodies. Do not wrap a HAR. Crop the status line.

Redaction that is not a black rectangle in a PDF editor

Black boxes in a PDF can be removed. Crop the PNG so the secret pixels are gone, then convert. If you must redact a PDF you did not create, that is Acrobat-class work, not PDF Merge. What not to paste.

Jira, Linear, and email-only vendors

Jira wants images inline for many teams. Email-only vendors want one PDF. Follow the tracker. If you need both, keep the PNGs in the ticket and attach the merged PDF for the people who will not click Jira. Do not upload the same shots to ILovePDF “to make a nice PDF.”

Print to PDF from the browser vs image wrap

Print-to-PDF captures the page as vectors/text when you are lucky, and as a messy layout when you are not. For a pixel bug (“this button is 2px off”), an image wrap is the honest artifact. For a long log, paste text. PNG to PDF is for pictures of UI.

What belongs in the ticket body so the PDF is not the only repro

Steps, expected, actual, browser/OS, feature flag, and the error string as text. The PDF is the pictures. Screen-reader-using teammates and people on a phone cannot OCR your five-page screenshot stack reliably. Page numbers with PDF Page Numbers so “see page 3” means a page, not a guess.

If the vendor replies “can’t repro,” add environment as page 1 of a one-page follow-up PDF rather than a 40-page session dump.

Dark UI, light PDF, and inverted screenshots

Some people invert colors or use Windows High Contrast. Your PNG of a dark theme can look like a different product. Say the theme in the filename (03-checkout-dark.png) and on page 1. Merge with PDF Merge in the order of the repro, not the order the files landed in Downloads.

Video timestamps vs a still

If the bug is a 200ms flicker, a Loom with a timestamp in the ticket beats a 12-page PDF of almost-the-same frames. Use PDF for layout and copy bugs. Do not Convertio a screen recording into a PDF of keyframes.

Order of operations that keeps PII off converters

Crop → convert PNG to PDF → merge → page numbers → compress → attach. Skip any cloud “PDF from images” ad in that chain. If size still fails email, split the PDF, not the secret. Email attachment size limits.

Multiple monitors and “the toast was on the other screen”

A capture of monitor 2 while the bug is on monitor 1 wastes a page. Crop to the control. If the toast is off-canvas, scroll it into view before the snip, then PNG to PDF.

Crop is the security step. PNG to PDF is the wrap. PDF Merge is the stack. PDF Compressor is the email.