Snapopa
Back to blog
ChangelogReleaseBlocking

What's new: anti-bot mode and finer-grained blocking

A stealth option for sites that challenge headless browsers, plus separate switches for ads, trackers, cookie banners, popups and media.

Ruby Le
Ruby Le
Project Manager
· Apr 8, 2026· 1 min read

This release is about getting a clean capture from pages that fight back.

Anti-bot mode

Some sites show a challenge page to anything that looks like a headless browser. Set antiBot: true and the capture is routed to a stealth-capable browser provider:

{ "url": "https://example.com", "antiBot": true }

It is off by default because most sites do not need it and standard rendering is faster.

Blocking, split into switches

The block option now has five independent settings:

  • ads (on by default) - Blocks ad network requests
  • trackers (on by default) - Blocks analytics and tracking scripts
  • cookies (on by default) - Hides consent and GDPR banners (CSS-only)
  • popups (off by default) - Hides newsletter and promo overlays (CSS-only)
  • media (off by default) - Blocks images, video and fonts

We wrote up how the blocking works, and when to turn it off, in a separate post.

Also in this release

  • Clearer validation errors that name the exact field that failed.
Try Snapopa

Reading about screenshots? Try the API.

100 free tokens on signup. No credit card. One request is all it takes.

Start free Read the docs
$ curl https://api.snapopa.com/capture \
    -H "Authorization: Bearer sk_•••" \
    -d '{"url":"https://stripe.com"}'

✓ 200 OK
{ "data": { "fileUrl": "https://cdn.snapopa.com/…" } }