How to Save a Web Page as a PDF That Actually Looks Right

Everyone reaches for Ctrl+P → Save as PDF first. On a blog post it works. On a dashboard, a documentation site or anything with a sticky header, the file that comes out is not the page you were looking at.

That is not a bug in your browser. Printing is a separate rendering path with its own rules, and those rules are wrong for a page meant to be read on a screen. Here is what breaks, and what to do instead.

Four reasons Print to PDF gets it wrong

• Lazy-loaded images come out blankPrint rendering does not scroll the page, so anything that loads on scroll — most image grids, most feeds — has never been fetched and prints as empty space.
• Sticky headers repeat on every pageA fixed navbar is painted once per printed page, so a ten-page export carries ten copies of the header, each one covering the content underneath it.
• Print stylesheets rewrite the pageMany sites ship a @media print block that hides sidebars, strips backgrounds or drops entire sections. The PDF is a different document from the page you were reading.
• Dashboards and canvas elements drop outCharts drawn on a canvas, embedded maps and virtualised tables frequently render blank or truncated, because print never triggers the code that draws them.

Capture the page, then export it

The fix is to stop asking the print renderer for the document and take the screen's own rendering instead. Capture the full page as an image — scrolling it first, so everything loads — then write that image into a PDF sized to match.

• The full-page mode scrolls the real page first, so lazy content loads before anything is captured.
• You get one continuous image, so a sticky header appears exactly once — where it actually was.
• What you see is what you get: the screen's own rendering, not a print stylesheet's version of it.
• You can annotate before exporting — arrows, step numbers and redactions land in the PDF itself.

Doing it with Snipwise

1. 1Open the page you want to keep and click the Snipwise icon in the toolbar.
2. 2Choose Save as PDF. The page scrolls itself to the bottom so lazy content loads, then stitches one continuous capture.
3. 3Annotate first if you need to — arrows, numbered steps, or the blur tool over anything sensitive.
4. 4Export. The PDF is written on your machine and saved straight to your downloads folder.

Nothing is uploaded at any point — there is no server to upload to. If you would rather verify that than take our word for it, open DevTools, switch to the Network tab, and watch while you capture. The privacy policy spells out what the extension does and does not touch.

Common questions

How do I save a web page as a PDF without printing it?

Capture the page as an image first, then export that image to PDF. Snipwise does both in one step: choose Save as PDF, and it scrolls the page, stitches the full capture and writes a PDF sized to match. Because it works from a screenshot rather than the print renderer, the PDF looks like the page you were actually reading, including anything a print stylesheet would have hidden.

Why does Chrome's Print to PDF look broken on some pages?

Printing uses a separate rendering path. It does not scroll, so lazy-loaded images never load; it repaints fixed elements on every page, so sticky headers duplicate; and it applies the site's @media print rules, which often hide sidebars, backgrounds or whole sections. On dashboards, canvas-based charts and embedded maps commonly come out blank because the code that draws them is never triggered.

Does Snipwise upload my screenshots anywhere?

No. There is no server to upload to. Capture, annotation and PDF export all run inside your browser, and the extension requests no host permissions for any remote origin. You can confirm it yourself: open DevTools, switch to the Network tab, and capture a page — no outbound request is made.

Can I annotate a screenshot before saving it as a PDF?

Yes. Every capture opens in a full editor with ten tools — pen, arrow, line, circle, text, auto-numbered step markers, callout bubbles, blur and redact, crop, and emoji stamps. Annotations are drawn onto the image, so they are part of the exported PNG or PDF rather than a separate layer.

Can I redact sensitive information before sharing?

Yes, and it happens before the file exists. The blur and redact tool pixelates the area you drag over, and the export is written from the annotated canvas — so the original pixels are not carried into the saved file. Since nothing was uploaded at any point, the unredacted version never left your machine either.

Is Snipwise free, and is the source available?

It is free, MIT-licensed and open source. The full extension is a few plain HTML, CSS and JavaScript files with no build step, so you can read the code that handles your screenshots in an afternoon rather than trusting a minified bundle.