Why the Cookie Banner Is in Every Frame of Your Screenshot

A consent banner in a full-page screenshot is a worse problem than a repeated navigation bar, and it is worth separating the two, because the fix is different.

A sticky header repeats. A cookie banner repeats and covers something and sometimes stops the capture working at all.

Three separate things go wrong

1. It repeats, like any pinned element

Full-page capture works by scrolling a screen at a time and stitching the screens together. Anything pinned to the window is in every screen, so it lands in the image once per screen. This is the same mechanism that repeats a header, and it has its own page.

2. It covers content, so the capture has a hole in it

This is the part that makes banners worse than headers. A header sits above the content. A consent banner is usually an overlay dropped on top of it, often across the bottom third of the window and sometimes with a dimming layer over everything behind it.

Hide the banner at capture time and you still have the dimming. Capture around it and you have a strip of page you never got. Either way, a perfect stitch of a page you could not see is still a screenshot of a page you could not see.

3. On some sites it stops the page scrolling

Plenty of consent scripts lock scrolling until you answer, which is deliberate — it is how they make sure you answer. A capture tool that works by scrolling the page then has nothing to work with. What you get is the first screen, repeated, or a capture that finishes suspiciously quickly and is one screen tall.

If a full-page capture on a site you have never visited before comes out exactly the height of your window, this is almost always why.

The fix, and it is the boring one

Answer the banner first, then capture. Accept or decline — either works for this purpose, and the choice is yours to make on its own merits.

Two details that catch people out:

• Reload after you answer, then capture. Dismissing a banner changes the page height and can let content underneath finally load or move. Capturing the instant it disappears sometimes catches the page mid-shuffle, which produces a seam. A reload settles it.
• Answering does not always stick. Some sites re-prompt in a private window, or on a different subdomain, so the banner you dealt with yesterday is back today on the page you actually need.

If the banner genuinely cannot be dismissed — some regional variants offer no reject button without a paid subscription — the practical answer is to remove the element via right-click and Inspect, accepting that the content underneath it may still be unavailable.

What PageStill does, and what it will not do

PageStill hides elements that stay pinned while scrolling after the first screen, so a banner that is still on the page is not repeated down the image. It appears once, at the top, and the rest of the capture is clean.

What it will not do is answer the banner for you. Clicking Accept on a consent dialog is a decision about your own data, made on your behalf, and a screenshot tool has no business making it. It is also not something the extension could do quietly even if we wanted to: PageStill has no standing access to any website, and only touches the tab you clicked it on, from the moment you click.

So the sequence on a site you have not visited before is: answer the banner, reload, capture.