Guide

Why Full-Page Screenshots Cut Off Emails (and the Fix)

Full-page screenshots cut off emails because the email usually sits inside an iframe with its own scroll bar. Screenshot tools scroll the browser page, not the frame inside it, so they record only the part of the email visible in that frame. To fix it, capture the frame's content directly, open the email on its own, or re-render it.

Short answer: The tool isn't broken, it's scrolling the wrong thing. Use DevTools to capture the email node, open the email's web view, or, for Klaviyo emails, export them with Previyo, which re-renders the email instead of screenshotting it.

Pages vs frames: what a full-page tool actually scrolls

A browser tab has one main document, the page. A full-page screenshot extension measures that document's height, scrolls the window from top to bottom, and stitches the pieces together. That works well for articles and landing pages.

An iframe is a separate document embedded in the page, in a box with a fixed height. If the content inside is taller than the box, the iframe gets its own scroll bar. From the page's point of view, the iframe is just a rectangle, say 700 px tall. Scrolling the window doesn't scroll what's inside it.

So the tool does its job correctly: it captures the whole page, including a 700 px window onto your email. The other 2,000 px of email never appear on screen, so they never appear in the screenshot.

The same thing happens with any scrollable element: chat panels, code editors, sidebars. If it scrolls separately from the page, a page screenshot won't capture its hidden content.

Why email previews live in iframes

Email apps, ESPs and preview tools have good reasons to put the email in a frame:

Klaviyo's campaign and template previews work this way. That's why the same question keeps coming up in its Community: how to take "a snapshot of a whole email, top to bottom" without stitching screenshots by hand.

DevTools "Capture node screenshot": the developer workaround

Both Chrome and Firefox can screenshot a single element, including content that's off-screen.

Chrome or Edge:

  1. Right-click the email and choose Inspect. DevTools opens with an element inside the email selected.
  2. In the Elements panel, select the email's <body> or outer <table> (inside the iframe, not the <iframe> tag itself).
  3. Right-click it and choose Capture node screenshot.

Firefox:

  1. Right-click the email and choose Inspect.
  2. Select the email's <body> or outer table in the Inspector.
  3. Right-click it and choose Screenshot Node.

Downsides: it's fiddly for non-developers, the result is captured at your screen's pixel density, and the email is captured at whatever width the frame happens to be. There's no simple way to get the mobile layout. It's a good one-off trick, not a workflow.

Open the email on its own and capture that

If the email has a "view in browser" link, open it. In Klaviyo that's the web view created by the {% web_view %} tag. There the email is the page, so a full-page extension can scroll and capture all of it.

Downsides: you need a sent email (or a test sent to yourself) that includes the link. The capture is at your browser window's width, so you'll often get a wide white canvas with the email centered. Fixed or lazy-loaded elements can repeat or go missing at the seams. To get mobile, you have to resize the window or use device emulation.

Re-render the email instead of screenshotting it (how Previyo does it)

The most reliable fix is to not screenshot at all. The email is HTML; you can lay it out again at the right width and draw it to an image in one pass.

That's what Previyo does for Klaviyo:

  1. It reads the email's HTML from the Klaviyo preview frame.
  2. It turns each image, stylesheet and font into an embedded copy, downloading images from Klaviyo's image CDN.
  3. It lays the email out in a hidden, script-free frame at exactly 600 px (desktop) or 375 px (mobile), with mobile styles applied at 375.
  4. It draws the result to a single canvas and saves PNG, JPG or PDF. It can also save the HTML.

Because nothing is scrolled, there are no seams, no repeated headers and no Klaviyo interface in the image. Scale is up to you: 1×, 2× or 3×, regardless of your screen. If the renderer can't draw an email, the Export Studio (opened from the toolbar icon) can fall back to scrolling the frame and stitching screenshots.

It runs locally in your browser, with no account or API key, and the email isn't uploaded. For the step-by-step version, see how to screenshot an entire Klaviyo email. If you need dozens of emails at once, bulk export saves a whole selection of campaigns to one ZIP.

Checklist: is your screenshot complete?

Before you send a full-length email image to a client or put it in a deck, check:

FAQ

Why is my full-page screenshot not working?

It probably is working, on the page. If the content you need sits inside an iframe or a scrollable panel, page screenshot tools capture only the visible part of it. Capture the element itself with DevTools, open the content on its own page, or use a tool that re-renders it.

How do I screenshot a scrollable element in Chrome?

Open DevTools, select the element's content in the Elements panel, right-click and choose Capture node screenshot. Chrome captures the whole element, usually including the part scrolled out of view. Inside frames the result can vary, so check the bottom of the image.

Does GoFullPage capture iframes?

General full-page tools such as GoFullPage capture the page, not the scrolled content inside a frame on that page. They work well once the email is the page itself, for example on a web view.

How does Previyo avoid cut-off emails?

It doesn't take screenshots. It rebuilds the Klaviyo email from its HTML at 600 or 375 px and draws it into one image or PDF, so the length of the preview window doesn't matter.

Is Previyo affiliated with Klaviyo or GoFullPage?

No. Previyo is an independent extension. It is not affiliated with or endorsed by Klaviyo or GoFullPage.

Add Previyo to Chrome — free · Firefox

Export your first full-length email

Free during the beta. No account, no API key.