Ad and cookie blocking now default

AllScreenshots now enables ad blocking and cookie banner blocking by default. This gives new captures a cleaner output without requiring every request to include blockAds: true and blockCookieBanners: true.

What changed

• Single screenshot API calls block ads and cookie banners by default
• Async, bulk, and compose captures use the same clean defaults
• Workspace requests now start with both blocking toggles enabled
• Existing requests can still opt out by setting blockAds: false or blockCookieBanners: false

Why it matters

Most screenshot workflows need clean, shareable captures without ad slots, tracking pixels, and consent overlays. Making these protections the default reduces request boilerplate and makes the first capture more likely to match the result you want.

The request above now blocks ads and cookie banners automatically.