Bulk Captures
Windows 10 & 11 Buy license · $39.95
Troubleshooting

Scrolling Screenshot Shows a Repeated Header? Why and How to Fix It

Scrolling screenshot shows the header, chat widget or cookie bar repeated down the page? Learn why sticky elements do this and how to get a clean capture.

Updated 5 minute read The Bulk Captures team

If your scrolling screenshot shows the header, a chat button or a cookie bar repeated all the way down the page, the cause is a sticky or fixed element. These stay pinned to the screen while the page scrolls, so a tool that captures the page one screen at a time and stitches the pieces together photographs them again in every piece. The fix is either to capture the page in a way that renders its full height in one go, such as a browser's full-page command or a capture from the URL, or to stop the element from sticking before you capture.

This guide explains which elements cause the problem, five ways to get a clean capture, and how to deal with the elements that keep coming back.

Why sticky elements repeat

Most scrolling capture tools work like this: capture the visible part of the window, scroll down, capture again, and repeat until they reach the bottom. Then they join the pieces, matching up overlapping rows of pixels.

Normal page content moves up as you scroll, so each piece shows new content. But web designers often pin certain elements to the window using CSS (position: fixed or position: sticky). Those elements stay in the same spot on screen no matter how far you scroll, so they appear in every captured piece. The stitched result shows a copy of the header every screen-height down the page, often overlapping the content beneath it.

The usual suspects:

ElementWhere it repeatsQuickest fix
Sticky header or navigation barTop of every sectionFull-height render, or unstick it with DevTools
Cookie or consent bannerBottom of every sectionAccept or dismiss it before capturing
Chat or help buttonBottom corner of every sectionMinimize or close the widget
"Back to top" buttonBottom corner, appears after scrollingHide it with DevTools
Sticky sidebar or table of contentsSide of every sectionFull-height render
Sticky "add to cart" or promo barTop or bottomDismiss it, or full-height render

Fix 1: Use a capture that renders the full page at once

Browser full-page commands do not scroll and stitch. They resize the page's rendering area to its full height and capture it in one image, so a fixed header normally appears once, at the top, where it belongs.

  • Chrome and Edge: open developer tools with F12, press Ctrl+Shift+P, type full size and choose Capture full size screenshot.
  • Edge: press Ctrl+Shift+S for Web capture and choose Capture full page.
  • Firefox: right-click the page, choose Take Screenshot, then Save full page.

Our guide to full page screenshots in Chrome without an extension covers the DevTools commands step by step.

A few sites set their layout to fill exactly one window height and scroll an inner panel instead of the page. A full-size capture of those may come out as one screen tall. For those pages, scroll-and-stitch with the fixes below is the better route.

Fix 2: Dismiss what you can

Banners and widgets you can close, close. Accept or reject the cookie banner, minimize the chat widget, close promotional bars and newsletter pop-ups. Then reload the page if needed and capture again. Most sites remember your choice, so the elements stay away on later visits.

Fix 3: Unstick the header with developer tools

For elements that cannot be dismissed, change how they behave for this one capture. Nothing you change here affects the real website, and it all resets when you reload.

  1. Right-click the sticky header and choose Inspect.
  2. In the Elements panel, find the element highlighted on the page. You may need to move up a level or two to reach the one that is sticky.
  3. In the Styles panel on the right, find position: fixed or position: sticky.
  4. Click the value and change it to static. The header now scrolls away with the page.
  5. To remove an element completely, such as a floating button, right-click it in the Elements panel and choose Hide element, or press H.
  6. Take your scrolling capture.

Fix 4: Zoom out so fewer pieces are needed

If you must scroll and stitch, fewer pieces means fewer repeats. Pressing Ctrl+minus to zoom the browser to 67 or 50 percent fits more of the page on each screen. This does not remove the problem, and text gets smaller, but on a medium-length page it can reduce a dozen repeats to two or three. Note that zooming can also trigger a different responsive layout.

Fix 5: Capture from the URL instead of the window

When you need full pages regularly, or for many pages at once, capturing directly from the address is more reliable than scrolling a live browser window. You are not fighting your own browser's scroll position, extensions or open pop-ups.

Bulk Captures captures an entire web page from top to bottom as one tall image, either for the window you are looking at or for a whole list of URLs. In URL mode you set a viewport width and a load delay, and it saves a full-page capture of every address, named and filed automatically, with no manual stitching. Sticky elements are still part of the page design, so check the first few results; if a site's header or consent bar gets in the way, the dismiss and DevTools fixes above are the way to handle that particular page.

Elements that keep coming back

  • Cookie banners in batch captures. A batch visits each page as a first-time visitor, so consent banners will appear. For an honest record of what visitors see, that is usually correct. If you need clean marketing images, capture those pages individually after accepting the banner.
  • Headers that change on scroll. Some headers shrink or change color after you scroll. A full-height capture shows the initial version; a stitched one may show both. Pick the method that shows what you need.
  • Animated elements. Content that fades in as it scrolls into view can appear blank in full-height captures. That is a separate problem with its own fixes: see full page screenshots with missing images.

Which approach to use

SituationBest approach
One public web pageBrowser full-size capture (Fix 1)
Page behind a loginDismiss and unstick in DevTools, then browser capture (Fixes 2 and 3)
Document or app, not a web pageScroll-and-stitch, with the window maximized and zoomed out (Fix 4)
Many pages, or the same pages every monthFull-page capture from a URL list (Fix 5)

For an overview of every way to take long captures on Windows, see our guide on how to take a scrolling screenshot on Windows.

Frequently asked questions

Why does the header repeat in my scrolling screenshot?

Sticky or fixed headers stay on screen as the page scrolls, so a tool that stitches screen-sized pieces captures the header again in every piece.

How do I stop a chat widget appearing in screenshots?

Close or minimize the widget before capturing. If it reopens, a full-page capture from the URL is often cleaner than scrolling a live browser window.

Do browser full-page captures have the same problem?

Less often. Browser tools such as the Chrome DevTools full size screenshot render the page at its full height in one go, which avoids most repeats.

Get three guides like this every month, plus software update notices.Subscribe →