Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

CaptureKit’s March 2026 guide shows remove_cookie_banners=true as a way to remove a cookie banner from a screenshot. However, the current CaptureKit API reference does not list that parameter, so verify that it works with your account before relying on it. The documentation also does not say whether it accepts or stores consent: a banner missing from an image is not proof that a consent choice was made.

Try CaptureKit’s cookie-banner setting, but verify it first

The CaptureKit guide demonstrates remove_cookie_banners=true in a screenshot request. Its current API reference omits that setting. Treat it as an option to test, not a confirmed current API feature. The two sources also differ on the HTTP method: the reference labels /v1/capture as GET, while the guide’s sample uses POST. Check the current documentation and your account before choosing a method or building this into a production workflow.

The guide’s example uses the endpoint https://api.capturekit.dev/v1/capture, an x-api-key header, and these query parameters:

  • format=png
  • full_page=true
  • full_page_scroll=true
  • full_page_scroll_duration=800
  • viewport_width=1440 and viewport_height=1200
  • remove_cookie_banners=true and remove_ads=true
  • wait_until=networkidle2 and delay=2

These are the guide’s sample values, not required settings for every page. Adapt viewport and timing to the page you are capturing. For the precise request syntax and current method, consult the CaptureKit API reference and the CaptureKit guide published March 10, 2026.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Choose waits and page coverage for the target site

CaptureKit’s reference documents several ways to control when capture begins. Use the condition that matches the page rather than adding waits indiscriminately:

  • wait_until supports networkidle2, load, domcontentloaded, and networkidle0.
  • wait_for_selector can wait for a known element to appear.
  • delay accepts zero to ten seconds when a page needs additional time after its load condition.

For a full-page image, enable full_page. The guide also enables full_page_scroll so lazy-loaded content can load as the page is scrolled, and sets full_page_scroll_duration=800. The reference lists a 400 ms default for scroll duration. If you compare screenshots over time, keep the viewport and timing settings consistent; that is a way to make comparisons more controlled, not a guarantee of identical rendering.

If the banner option is unavailable, hide a known element

The current reference documents remove_selectors for hiding specified page elements. If you know the banner’s CSS selector, this may produce a cleaner image when the cookie-banner parameter is unavailable. Verify the selector against the actual page and inspect the resulting screenshot: the documentation does not provide a cookie-specific selector or guarantee that a given selector will match.

Both approaches should be described as visual removal unless CaptureKit documents otherwise. Hiding an element—or receiving an image in which it is absent—does not show that the site accepted, rejected, or stored a consent choice. If your goal is to test a real consent flow, these sources do not establish that either option performs the interaction.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Or skip the browser setup

ScreenshotNeo offers a one-request screenshot API. Its clean-shot workflow accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. This is separate from CaptureKit’s documented behavior, and a clean image should not be treated as proof of recorded consent.

Use the request below with your ScreenshotNeo API key. See the ScreenshotNeo API documentation for request options.

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

ScreenshotNeo reports whether a response was a bot check or CAPTCHA, blank page, timeout, failed load, or cache hit; those outcomes cost nothing. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots.

Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month without a card.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Frequently Asked Questions

Does CaptureKit accept cookies when it removes a banner?

The reviewed CaptureKit documentation does not explain whether the setting clicks a consent choice or stores a consent signal. Do not infer acceptance from the screenshot alone.

What image formats does CaptureKit document?

The current API reference lists PNG as the default and also documents JPEG/JPG, WebP, and PDF.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.