You are putting together an evidence packet, a research summary, or a trip report that pulls from three different kinds of source material: screenshots you grabbed off a website, the HTML of a help-desk article you want to preserve, and your own Markdown notes. The end product needs to be a single PDF, in a deliberate order, signed at the front so the recipient knows you certified it.

There is no single tool that converts all three formats and signs in one shot. But you can do the whole job in a single browser tab using five of Signegy’s free tools chained back to back. Nothing uploads, no account needed, the whole sequence works offline once the tools’ JavaScript has loaded.

Why this chain, in this order

You convert each source type to PDF separately first because each needs different conversion logic. Then you merge the resulting PDFs in the order you want the final packet to read. Then you sign the merged file once, at the front, certifying the assembled packet rather than the individual pieces. Signing each piece separately and then merging would produce a packet with five orphan signatures inside it, which is not what you want.

Pages also lets you reorder during the merge step, so you do not need to convert in the order you want the final read — convert in any order, then sequence at merge time.

Step 1: Convert your screenshots

Open the Image to PDF tool and drop in all the screenshots — PNG, JPG, or a mix. Drag the thumbnails into the order you want those screenshots to appear in the final packet. Pick page size (Letter or A4 typically), orientation (portrait works for most screenshots, landscape for wide dashboards), and whether you want one image per page or multiple. Save and download. You now have one PDF for the image section.

If your screenshots are very large or very high-resolution, the resulting PDF can be tens of megabytes. You can run it through the Compress tool at this stage if you want to keep the final packet small — or wait until step 4 and compress everything at once.

Step 2: Convert the HTML article

Open the HTML to PDF tool in a new tab. You have two options. If you have the page’s HTML saved as a file, drop it in. If you have the URL, save it as a complete page first (Ctrl/Cmd-S → “Webpage, complete” in most browsers) and drop the resulting .html file in. Or paste the raw HTML into the text input.

The tool renders the page as a print-style PDF, with hyperlinks preserved as live links in the output. Save and download. You now have one PDF for the article section.

For more complex pages with heavy JavaScript, consider taking a screenshot of the rendered page instead and adding it to step 1. The HTML to PDF converter handles static markup well; it does not run client-side JavaScript that mutates the DOM after page load.

Step 3: Convert your Markdown notes

Open the Markdown to PDF tool in a third tab and either paste your notes or drop in a .md file. The renderer supports GitHub Flavored Markdown — fenced code blocks, tables, task lists, strikethrough, autolinks. The output uses a clean typed style suitable for a packet appendix or an annotated commentary on the prior sections.

Save and download. You now have one PDF for the notes section.

Step 4: Merge in order

Open the Merge PDF tool in a fourth tab. Drop in all three PDFs (the screenshots PDF, the HTML PDF, and the notes PDF). Drag them into the order you want the final packet to read — typically: cover note (Markdown) on top, screenshots in the middle as evidence, the source article last as the appendix.

If you want the order at the page level rather than the file level, use Reorder Pages on the merged file afterwards to drag individual page thumbnails into a specific sequence.

Save and download the merged packet.

Step 5: Sign the front page

Open the Signing tool in a fifth tab and drop in the merged file. Add your signature on the cover page — drawn, typed, or uploaded from an image. If the packet is going out as evidence in a matter where authenticity matters, the signing tool also produces a free audit certificate recording a SHA-256 hash of the final packet, which lets a recipient verify later that the bytes have not been altered since you signed.

Download both the signed PDF and the audit certificate. Send the signed PDF to the recipient; keep the certificate in your file alongside the source materials.

What to watch out for

The HTML to PDF converter handles static markup well but does not run page JavaScript. If the source page renders its content via React, Vue, or similar after page load, what you’ll get is the empty shell. The workaround is to load the page in your browser, wait for it to finish, and either save it as a complete HTML page (which captures the rendered DOM in modern browsers) or grab a screenshot and route it through step 1 instead.

The other thing to budget for: this is a five-tool, multi-tab workflow, and each step downloads a new file. Use a single download folder for the session and keep the filenames descriptive (01-notes.pdf, 02-screenshots.pdf, 03-article.pdf, merged.pdf, merged-signed.pdf) so you do not lose track of which file is the final input to the next step.

Prepare a PDF for legal discovery — when the merged packet also needs Bates numbers and a confidentiality watermark.
Make a scanned PDF searchable, then sign it — for adding scanned documents to the packet alongside screenshots and notes.
Fill, sign, and lock a government tax form — for forms that need to ship as part of a larger packet.

Signegy provides general information, not legal advice. Confirm any specific evidentiary, filing, or chain-of-custody requirements with the relevant court rules, regulator, or supervising counsel.