Blocking

Ads, trackers, chat widgets and cookie banners.

{
  "url": "https://example.com",
  "block_ads": true,
  "block_trackers": true,
  "block_chats": true,
  "block_cookie_banners": true,
  "format": "png"
}

Cookie banners work in two layers. The first uses known rules for the major consent platforms — OneTrust, Cookiebot, Quantcast, Usercentrics, Didomi and others — hiding the container and clicking a reject button where one exists.

The second, block_banners_by_heuristics=true, is opt-in. It looks for large fixed overlays whose text matches consent vocabulary and only clicks inside a restricted set of candidates. It is opt-in because a wrong click on a checkout page is far worse than a banner in a screenshot.

Both layers also release the scroll lock that consent platforms apply to <body> — otherwise a full-page capture would come back as just the first fold.

For anything else, block_requests accepts domains or glob patterns, and block_resources blocks by type (image, font, script, xhr, …).