<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Nick W</title>
    <description>The latest articles on DEV Community by Nick W (@nick97).</description>
    <link>https://dev.to/nick97</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4242925%2F6185993b-7b93-4459-9ec0-ed03a12fdf8e.jpg</url>
      <title>DEV Community: Nick W</title>
      <link>https://dev.to/nick97</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/nick97"/>
    <language>en</language>
    <item>
      <title>Why full page screenshots cut off on Gmail, Notion and dashboards (and how to capture them)</title>
      <dc:creator>Nick W</dc:creator>
      <pubDate>Fri, 13 Nov 2026 13:57:11 +0000</pubDate>
      <link>https://dev.to/nick97/why-full-page-screenshots-cut-off-on-gmail-notion-and-dashboards-and-how-to-capture-them-7g7</link>
      <guid>https://dev.to/nick97/why-full-page-screenshots-cut-off-on-gmail-notion-and-dashboards-and-how-to-capture-them-7g7</guid>
      <description>&lt;p&gt;If you have ever taken a "full page" screenshot of Gmail, a Notion doc or an analytics dashboard and got back one screen of content with a lot of empty space, this post explains why, and what to do about it.&lt;/p&gt;

&lt;p&gt;Disclosure up front: I build FullPage Capture, a Chrome extension for this. The first half of the post needs no extension at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  The built-in way, and where it stops
&lt;/h2&gt;

&lt;p&gt;Chrome can capture a whole page without installing anything:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open DevTools (F12, or Cmd+Option+I on Mac)&lt;/li&gt;
&lt;li&gt;Press Ctrl+Shift+P (Cmd+Shift+P on Mac)&lt;/li&gt;
&lt;li&gt;Type &lt;code&gt;screenshot&lt;/code&gt; and pick &lt;strong&gt;Capture full size screenshot&lt;/strong&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For articles, docs sites and landing pages this is all you need. It fails in four specific situations.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. The page does not scroll, a panel inside it does
&lt;/h3&gt;

&lt;p&gt;Gmail, Notion, Slack, most admin dashboards and many editors keep the window fixed and scroll a &lt;code&gt;div&lt;/code&gt; inside it. DevTools measures the document height, finds it equals the viewport, and saves one screen. The content you wanted is inside a container the capture never scrolled.&lt;/p&gt;

&lt;p&gt;You can check this yourself: if the browser scrollbar on the far right is missing but the content still scrolls, it is an inner scroller.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Sticky headers
&lt;/h3&gt;

&lt;p&gt;Tools that scroll and stitch take a picture per screen. A header with &lt;code&gt;position: sticky&lt;/code&gt; or &lt;code&gt;fixed&lt;/code&gt; is present in every one of those pictures (floating chat buttons and cookie bars behave the same way), so it shows up again every 800 pixels or so in the result. The fix is to capture the fixed elements once and hide them for the remaining frames.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Lazy-loaded content
&lt;/h3&gt;

&lt;p&gt;Images and list rows that load on scroll are not there until something scrolls past them. A capture that resizes the viewport instead of scrolling gets grey placeholders. You have to scroll, wait for the network, then shoot.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Very long pages
&lt;/h3&gt;

&lt;p&gt;Chrome limits how large a single canvas can be. Past that limit the image silently comes out blank or truncated. Long chat exports and infinite feeds hit this regularly.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I do about each one
&lt;/h2&gt;

&lt;p&gt;FullPage Capture handles these cases like this:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Inner scrollers and iframes&lt;/strong&gt;: it captures the window, then finds the scrolling panel and unrolls it too.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sticky headers&lt;/strong&gt;: captured once, at the top.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Lazy loading&lt;/strong&gt;: it scrolls the real page and waits before each frame.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Very long pages&lt;/strong&gt;: past 28,800 px per side the capture is split into numbered parts instead of failing.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What people tell me they use it for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Sending a complete page as documentation to an agency, a client or a government portal. Capture the whole page, upload one file.&lt;/li&gt;
&lt;li&gt;Grabbing website layouts and content for design reference.&lt;/li&gt;
&lt;li&gt;Saving a ChatGPT or Claude conversation, a Gmail thread or a Notion page as a PDF.&lt;/li&gt;
&lt;li&gt;Capturing a full Google Analytics or Search Console report.&lt;/li&gt;
&lt;li&gt;Attaching a complete page to a bug report with the URL and date stamped on it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A few lines from recent Chrome Web Store reviews, quoted as written:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"It's the best way to provide online documentation to agencies. Just click the whole page and upload it to their site."&lt;/p&gt;

&lt;p&gt;"My go to for grabbing website layouts and content."&lt;/p&gt;

&lt;p&gt;"A rare one that does long page screen capture easily."&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Not every review is glowing. One user reports that very long pages can come out blurry, and another that captures lag on heavily interactive sites. Both are on my list.&lt;/p&gt;

&lt;p&gt;Export is PNG, JPEG or PDF. The PDF can be one tall page or Letter, Legal and A4 with page breaks that do not cut through a line of text, and links stay clickable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where other tools are the better choice
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;You use Firefox.&lt;/strong&gt; FullPage Capture is Chromium only. Firefox has a good built-in full page screenshot, and GoFullPage now ships a Firefox version.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You want zero install permissions.&lt;/strong&gt; GoFullPage requests no site access at install. FullPage Capture asks for it, because reading iframes and PDFs open in Chrome requires it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You capture ordinary pages only.&lt;/strong&gt; On plain document-scrolling pages the DevTools command and every major extension give the same result. Use whichever is already installed.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Privacy and price
&lt;/h2&gt;

&lt;p&gt;Captures are processed and stored in the browser. There is no account and no analytics. One exception worth stating: extensions cannot scroll Chrome Web Store pages, so for those the public page address is sent to our server, which renders it and returns the image.&lt;/p&gt;

&lt;p&gt;Capturing, saving, copying and printing are free with no watermark. Saving a capture after you have annotated it, searchable PDF, batch capture and an evidence stamp with a SHA-256 checksum are in Pro at $19 a year.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Site and guides: &lt;a href="https://fullpagecapture.net" rel="noopener noreferrer"&gt;https://fullpagecapture.net&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Chrome Web Store: &lt;a href="https://chromewebstore.google.com/detail/fullpage-capture-full-pag/ggacghlcchiiejclfdajbpkbjfgjhfol" rel="noopener noreferrer"&gt;https://chromewebstore.google.com/detail/fullpage-capture-full-pag/ggacghlcchiiejclfdajbpkbjfgjhfol&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you have a page that still captures wrong, post the URL in the comments. Broken cases are how the capture logic gets better.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>productivity</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
