Improve screenshot API speed and reliability with better wait conditions, batching, formats, caching, retries, and monitoring.
Learn how screenshots support financial audits, compliance reviews, and evidence collection by preserving what auditors saw, when they saw it, and where it came from.
Build website thumbnail previews for dashboards, directories, link cards, CRM records, and internal tools with a screenshot API.
Developers, marketers, and founders use Allscreenshots to automate website captures. No credit card required to get started.
Automated screenshots are only useful when they show the page you meant to capture. Cookie consent banners, ads, newsletter popups, chat widgets, survey prompts, and sticky promos can cover the exact content you need to inspect.
The problem is worse at scale. A single manual screenshot can be cleaned up by closing the banner. A scheduled capture, visual regression run, audit archive, or thumbnail pipeline needs a repeatable rule.
This guide shows how to reduce screenshot noise without hiding meaningful page changes.
Modern websites often render several layers on top of the page:
| Overlay | Why it appears | Screenshot problem |
|---|---|---|
| Cookie banner | Consent and privacy compliance | Covers footer, CTAs, pricing, or forms |
| Ad slot | Monetization | Creates layout shifts and inconsistent captures |
| Newsletter modal | Lead capture | Blocks the page after a delay |
| Chat widget | Support or sales | Floats over buttons and content |
| Promo bar | Campaigns and discounts | Changes frequently and triggers false diffs |
| Survey prompt | Feedback collection | Appears unpredictably |
None of these layers are necessarily bugs. They are part of the live page. But if your goal is to document the underlying product page, compare a visual baseline, or generate clean thumbnails, they get in the way.
AllScreenshots supports ad blocking and cookie banner blocking as capture settings:
curl -X POST 'https://api.allscreenshots.com/v1/screenshots' \
-H 'X-API-Key: YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"url": "https://example.com",
"fullPage": true,
"blockAds": true,
"blockCookieBanners": true,
"viewport": {
"width": 1440,
"height": 900
},
"responseType": "url"
}'Use these before reaching for custom workarounds. They handle the common cases while keeping your capture request simple.
Keep ad and cookie-banner blocking consistent across a workflow. Mixing blocked and unblocked captures makes visual diffs harder to interpret.
Before hiding anything, be clear about the purpose of the screenshot.
| Goal | Recommended approach |
|---|---|
| Marketing review | Block cookie banners and ads |
| Visual regression testing | Block noise, keep product UI visible |
| Compliance evidence | Capture the page as the user sees it, or archive both versions |
| Thumbnail generation | Block overlays and use a fixed viewport |
| Competitor monitoring | Usually block ads, but think carefully before hiding promos |
| Cookie banner QA | Do not block the cookie banner |
There is no universal "clean" screenshot. A consent banner is noise in a product thumbnail, but it is the subject of the test when your legal team asks whether consent appears correctly.
Some popups appear after a delay. Others appear only after the main content renders. If you capture too early, you may miss a banner that a real user sees. If you capture too late, a newsletter modal may cover the page.
Start with a meaningful selector:
{
"url": "https://example.com/pricing",
"blockAds": true,
"blockCookieBanners": true,
"waitForSelector": "main",
"fullPage": true,
"responseType": "url"
}For pages with charts, tables, or client-rendered content, wait for the specific content:
{
"url": "https://example.com/reports",
"blockAds": true,
"blockCookieBanners": true,
"waitForSelector": "[data-testid='report-ready']",
"delay": 500,
"responseType": "url"
}The goal is to capture after the real page is ready, not after every third-party script has finished doing work.
Full-page screenshots are more likely to expose overlays because they include areas a user would normally scroll to. Sticky cookie banners and chat widgets can repeat visually or cover content across the captured page.
For full-page captures:
blockCookieBanners for consent overlays.blockAds when ad slots are not part of the review.{
"url": "https://example.com/blog/launch-post",
"fullPage": true,
"blockAds": true,
"blockCookieBanners": true,
"viewport": {
"width": 1280,
"height": 800
},
"responseType": "url"
}If you only need the hero section or first viewport, avoid full-page mode. It is faster and produces fewer surprises.
Cookie banners and ads are a common cause of false positives in visual regression testing. They change independently from your code, so they can fail a pull request even when the product UI is fine.
For visual regression, aim for deterministic captures:
| Source of noise | Mitigation |
|---|---|
| Cookie banner | Enable cookie-banner blocking |
| Ads | Enable ad blocking |
| Chat widget | Disable it in test environments when possible |
| Animations | Prefer reduced motion or wait for a stable selector |
| Dates and timers | Hide or freeze them in the app under test |
| Personalized content | Use a seeded test account or static fixture data |
The cleanest setup is an environment built for testing: same data, same viewport, same theme, same page state. Blocking helps, but it is not a substitute for deterministic test data.
Do not hide overlays when they are part of the user experience you are reviewing.
Examples:
In those cases, capture the page as-is. If you also need a clean version for design review, archive both:
pricing-user-view.png
pricing-clean-review.pngThat small naming distinction prevents confusion later.
If the same pages need regular review, use a schedule rather than running captures manually. Scheduled screenshots are useful for:
For scheduled monitoring, start with blocking enabled and change detection at a moderate sensitivity. Then inspect the first few runs. If important page changes are hidden, loosen the blocking. If harmless third-party movement triggers alerts, tighten the setup.
The competitor pricing alert guide walks through a no-code schedule with email delivery and change-only notifications.
Before you automate a page, take one test screenshot and check:
One manual review at the start saves noisy alerts and broken baselines later.
Removing banners and ads is not just a technical setting. It changes what the screenshot represents.
For QA and visual regression, clean captures usually produce better signal. For compliance and customer evidence, the raw user view may be more accurate. For monitoring, the right answer depends on whether the overlay is part of what you care about.
Pick the capture policy once, document it, and use it consistently across the workflow.