How to Capture a Website Screenshot and Hide Cookie Banners with Screenshot.rocks

Screenshot.rocks can capture the visible part of your active browser tab and open it in its editor, where you can style and export the image. Its reviewed documentation does not confirm a built-in control that automatically hides cookie banners. For a one-off image, crop or cover the banner after capture; for repeatable screenshots, use a browser automation tool with a site-specific CSS rule or selector. If you need to test consent behavior, use the page’s actual accept or reject controls: hiding a banner is not the same as making or recording a consent choice.

1. Capture the page with Screenshot.rocks

1. Install the Screenshot.rocks extension from a supported browser store and pin it.
2. Open the page you want to capture and put the relevant content in the visible tab area.
3. Click the extension button. It captures the visible part of the tab and opens the image in the Screenshot.rocks editor.
4. Choose a style or background, make any edits, and export the image.

The extension captures the viewport, not the entire page. For a full-page screenshot, use your browser’s built-in full-page capture, then import that image into the editor. The extension documentation says the screenshot is sent to Screenshot.rocks to open in the editor and is not stored; the product overview describes editor processing in the browser and says editor images are not stored on its servers. See the Screenshot.rocks overview and its extension instructions.

2. Remove a banner from a one-off image

If the banner is already in the captured image, use an image editor to crop it out or cover it with an opaque shape. Cropping is simplest when the banner is at the edge and the remaining page still tells the story. An opaque cover works when you need to preserve the canvas dimensions, but make sure it does not conceal page content the reader needs to see.

Do not treat visual cleanup as consent management. If you are documenting or testing consent, interact with the real controls and note whether you accepted, rejected, or customized preferences. A screenshot without a banner cannot establish what choice was made or whether the site recorded it.

3. Hide a site-specific banner in repeatable captures

For automated screenshots, the separate capture-website project documents CSS injection and selector-based element hiding. This is not a Screenshot.rocks feature. Use a selector that matches the banner on the target site, and verify the result whenever the site changes its markup or styles. Selector rules can break after redesigns, and setting an element to display: none may change the page layout.

const captureWebsite = require('capture-website');

(async () => {
  await captureWebsite.file('https://example.com', 'page.png', {
    styles: ['.cookie-banner { display: none !important; }']
  });
})();

Replace .cookie-banner with the selector for the specific site. The selector above is an example, not a universal cookie-banner selector. Check the project’s documentation for installation and current options: 4. Choose the right workflow

Need	Approach	Watch for
One clean image quickly	Capture, then crop or cover the banner	Do not imply a consent action occurred
Repeated captures of one site	Inject CSS or hide a site-specific selector in automation	Selector changes and layout shifts
Consent behavior testing	Use the real accept/reject controls and verify the result	A hidden banner alone proves nothing about consent state
Entire page	Use browser full-page capture, then import for editing	The Screenshot.rocks extension itself captures the visible area

5. Protect sensitive information before sharing

Inspect the whole exported image for account details, email addresses, tokens, and other private data. Prefer replacing sensitive values before capture, or crop them away or cover them with an opaque shape. Screenshot.rocks says its blur effect is flattened on export, but its guide cautions that light blur or small pixelation may sometimes be reversible, so do not rely on subtle blur to protect secrets. See the Screenshot.rocks guide.

6. Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. A GET request takes a URL and returns an image or PDF. Its capture flow accepts cookie and consent banners like a visitor, then removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and the response identifies the page verdict and billing status. AI agents can capture with its MCP tools, including take_screenshot, get_page_info, and capture_pdf.

See the ScreenshotNeo API documentation for parameters and options. This cURL example saves a WebP screenshot:

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://stripe.com \
  -o shot.webp

Python:

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

Node.js:

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://stripe.com'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));

One thousand screenshots per month are free with no card; paid plans start at $5 for 3,000. Create a free ScreenshotNeo account and get 1,000 screenshots a month with no card.

7. Troubleshooting

Problem	Likely cause	Fix
The banner remains in the image	The extension captures what is visible; no documented automatic removal control is established	Crop or cover it for a one-off image, or use a verified site-specific automation selector
The screenshot cuts off the page	The extension captures the visible tab area	Use the browser’s full-page screenshot feature and import the resulting image
The CSS rule has no effect	The selector does not match, the banner is inside an iframe or shadow root, or the page changed	Inspect the live DOM, update the selector, and account for iframe or shadow DOM handling in your automation setup
Removing the banner shifts or overlaps content	The banner affects layout, or another page element depends on its space	Inspect the resulting layout; consider covering the banner in the final image when preserving the original geometry matters
The cleaned screenshot is being used as consent evidence	Visual removal was mistaken for a real preference action	Repeat the test with the page’s actual controls and record the chosen action and observed result
Private data is still readable	Blur or pixelation was too light	Replace the data before capture, crop it out, or use a fully opaque cover

8. FAQ

Does Screenshot.rocks automatically accept cookie consent?

The reviewed official documentation does not establish that it does. In any case, accepting consent is a real user action; hiding the visual banner does not mean consent was accepted.

Can I capture a full page with the extension?

The extension documentation describes visible-tab capture. Use the browser’s full-page screenshot capability for a full document, then import that image into the editor.

Will one CSS selector work on every website?

No. Banner markup varies by site and can change. Use and maintain a selector for each target, and inspect the rendered result.

Does Screenshot.rocks store the extension screenshot?

The extension instructions say the screenshot is sent to open in the editor and is not stored. The product overview also describes in-browser editor processing and says editor images are not stored on its servers.