How to Capture a Web Page in Nimbus Screenshot When a Cookie Banner Covers the Content
Try Nimbus’s Hide fixed elements setting, then inspect the capture. If the banner remains, use an appropriate page control or another capture method.
If a cookie banner covers the page in Nimbus Screenshot, try enabling Hide fixed elements in the capture settings and capture again. Nimbus documents this as a general setting for fixed page elements, not as a cookie-banner detector, so check the result: it may also hide a sticky header, navigation, or other fixed content.
Choose the capture mode that fits your goal. Use Entire page for a full-page capture; use a visible-area or selected-area capture when you only need what is currently on screen. Nimbus documents whole-page and selected-area capture options in its screenshot guide and product page.
Steps to try in Nimbus Screenshot
- Open the page and decide whether you need the entire page or only the visible content. Select the matching Nimbus capture mode.
- Open Nimbus’s capture settings and select Hide fixed elements. Nimbus’s guide recommends trying this option when fixed elements interfere with a capture. Read the Nimbus guide.
- Capture the page again. Inspect the image for the banner and for other fixed elements you intended to keep, such as a sticky menu or header.
- If the banner remains, look for a page-provided close or reject control. If it is appropriate for your task, use that control and take a fresh capture.
Hiding a banner, rejecting consent, and accepting consent are different actions. Do not accept consent solely to make an image look cleaner: acceptance may save a site preference. If there is no suitable close or reject route, keeping the banner visible may be the most faithful capture.
Why Hide fixed elements may not remove the banner
The Nimbus documentation describes a setting for fixed elements generally; it does not document a dedicated cookie-banner toggle or promise that every consent banner will be recognized. A banner may not be fixed, or the site may show it again during a full-page capture. Behavior can vary by page. A practical screenshot guide also recommends dismissing an overlay manually where possible and notes that overlays may return during a long-page scroll. See the practical guide.
| What you see | What to try | What to check |
|---|---|---|
| The banner covers the viewport | Try Hide fixed elements, then recapture. | Whether the banner disappeared and whether a fixed header disappeared too. |
| The banner remains after hiding fixed elements | Use a page-provided close or reject control, if available and suitable, then recapture. | Whether the page changed and whether the capture reflects the intended state. |
| The banner disappears at first but appears lower down | Review the full-page capture and consider whether the page re-displays the overlay while scrolling. | Long pages can expose behavior not visible in a viewport capture. |
| There is no suitable dismissal control | Capture with the banner visible, or try the fixed-elements setting and document the visual change. | Whether removing the banner would misrepresent the page state. |
Common problems and fixes
The banner is still in the screenshot
Possible cause: The banner is not treated as a fixed element, or the site presents it in a way the setting does not affect. Fix: Try the page’s own close or reject control if available, then capture again. The setting is a general fixed-element option, not a guarantee for every consent implementation.
The sticky navigation or header is missing too
Possible cause: Hide fixed elements applies beyond cookie banners. Fix: Inspect the result and decide whether that trade-off is acceptable. If the navigation matters, use an appropriate page control to dismiss the banner instead, or keep the banner in the capture.
The banner returns during a full-page capture
Possible cause: The page may show the overlay again as the capture moves through the page. Fix: Check the entire output, not just its first screen. If a page-level dismissal is appropriate, dismiss it before starting a new capture; otherwise, choose a capture that faithfully shows the page state.
The screenshot shows a different consent state than expected
Possible cause: A page control may save a preference, or the banner may be removed only for the capture. Fix: Distinguish a visual change from a consent choice. Prefer a close or reject route over accepting solely for appearance, and inspect the page after interacting with it.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. Its capture flow accepts cookie and consent banners, removes more than 60 known consent platforms along with newsletter popups and chat widgets, and lets you turn each step off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing; responses indicate the page verdict and billing status in headers. An MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs.
Here is a one-call request using cURL. Replace YOUR_API_KEY with your key and the URL with the page you want to capture. See the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpFor scripts, the same request is available in Python and Node.js:
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)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', bytes));The Free plan includes 1,000 screenshots a month with no card. Paid plans start at $5 for 3,000 screenshots; every feature is available on every plan. Sign up for 1,000 free screenshots a month, with no card.
Reliability and cost considerations
For Nimbus, inspect each capture because a general fixed-elements setting may remove content you need or leave a banner untouched. For repeatable captures across many pages, an API can make the request part of a script or workflow. With ScreenshotNeo, only clean shots are billed; bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed. Check the response’s X-Page-Verdict and X-Billed headers to see the outcome. See the documentation for API options and setup.
FAQ
Does Nimbus have a cookie-banner removal switch?
The reviewed Nimbus help material documents Hide fixed elements, not a dedicated cookie-banner switch.
Will Hide fixed elements preserve my sticky header?
Do not assume so. The setting applies to fixed elements generally, so inspect the capture for other content that may have been hidden.
Should I accept cookies to get a clean screenshot?
Not solely for appearance. Acceptance can save a site preference. Use a suitable close or reject control if one is available, or keep the banner visible.
Can I automate captures without using the Nimbus extension?
Yes. ScreenshotNeo offers a screenshot API and an MCP server for AI agents. Its free plan includes 1,000 screenshots per month without a card; see the call above and the API docs.
