You can screenshot a page without a cookie banner by placing Hide Element before Take a Screenshot. Pick the banner once, run the graph, and Tab Automation hides that match before Chrome captures the visible viewport as a PNG.
This is a cosmetic change to the current page. It does not accept or reject cookies, save consent, or change the source website.
Hide a cookie banner before the screenshot
- Open the page you want to capture, then open Tab Automation from its toolbar action.
- Click New Automation and choose the open tab under Select a Tab.
- Click Add Step, choose Hide Element, then click Pick element to hide.
- Click the cookie banner or overlay on the page. The picker writes its CSS selector.
- If the selector matches several elements, use Which match to use to choose the intended one.
- Add another Hide Element step when the dim backdrop, chat button, or sticky header is a separate page element.
- Add Take a Screenshot after every Hide Element step.
- Turn Repeat off for one PNG, or leave it on when the same cleanup and capture should run again after each cycle wait.
- Use Test to run the sequence once, then choose Save & Run.
The order matters. A screenshot placed before Hide Element still contains the banner. A screenshot placed after it photographs the page with that selected node set to display: none.
Chrome can only capture the tab that is showing, so Take a Screenshot brings the assigned tab and window to the front. The PNG is the visible viewport, not a full-page image or a crop of one element.
Wait for a late cookie banner
Hide Element waits up to about six seconds for its selector to appear. That is enough for many overlays that arrive shortly after the rest of the page.
When the banner arrives later, or when the sequence should explicitly wait for it, place Wait / Delay first and configure Until → Appears for the banner. The sequence becomes:
- Wait Until Appears
- Hide Element
- Take a Screenshot
The Until step polls only while that automation is running. It is not a permanent page watcher. If the wait times out, it records a warning and the graph continues, so Hide Element can still fail when the banner never arrives.
For a region below the fold, place Scroll Page after the hide and before the screenshot. Scroll changes which visible frame Chrome photographs; it does not turn the result into a stitched full-page capture.
Hiding is not dismissing or giving consent
Hide Element changes the presentation of one node in the current document. It does not click Accept, Reject, or Close, and it does not store a cookie preference.
That distinction matters when an overlay also locks the page. Some sites put the banner, backdrop, and scroll lock on different elements. Hiding the visible banner may leave the backdrop or the page’s disabled scrolling in place. Add a Hide Element step for another visible node when appropriate, but use the website’s own controls when a real consent choice or page-state change is required.
This is not an ad blocker or a cookie-banner detector. Tab Automation does not guess which element is a notice, keep a shared filter list, or automatically adapt when the website changes its selector. You choose the element for this automation.
Hide an element with Chrome DevTools instead
For a one-off manual capture, Chrome DevTools can temporarily hide a node:
- Right-click the banner and choose Inspect.
- In the Elements panel, select the banner’s node.
- Press
H, or right-click the node and choose Hide element. - Take the screenshot manually.
Chrome documents this in its guide to viewing and changing the DOM. Reloading the page restores the element, so repeat the manual edit for another fresh load.
Tab Automation is useful when the same hide-then-capture sequence should be tested, saved, or repeated without reopening DevTools each time.
A page banner is not a Chrome pop-up
Chrome’s pop-up blocker handles separate browser pop-up windows and redirects. Google’s pop-up settings guide explains those browser permissions.
A cookie banner, newsletter modal, or chat widget is usually an element inside the web page. Changing Chrome’s pop-up setting does not necessarily remove it from a screenshot. Hide Element targets that in-page node instead.
Limits to know before you start
- One picked match per step. Add more Hide Element steps for separate banners, backdrops, headers, or widgets.
- The selector can change. If the site replaces its markup, the step waits about six seconds, then records a failure in Activity.
- The change is temporary. Refreshing or navigating replaces the document and shows the element again. A repeating graph runs Hide Element again before each capture.
- Visible viewport only. Take a Screenshot does not stitch a whole page, crop one element, or capture a hidden background tab.
- Chrome must stay open. The sequence does not run in the cloud or continue after you quit Chrome.
- Web pages only. Chrome UI pages, extension pages, and the Chrome Web Store cannot be targeted or captured.
- Files stay local. PNGs are saved beneath Chrome Downloads, using the Settings folder or a step override.
For the timer, file naming, link-walking, and screenshot failure behavior, read the broader guide to automatically screenshot a Chrome tab.