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

Microlink’s adblock is documented as enabled by default and blocks matching third-party ads, trackers, and consent-service requests before a page renders. It will not necessarily remove a cookie banner or pop-up built into the website itself. For those, use Microlink’s page controls: inject CSS to hide a known element, click its dismiss control, or run a script for custom behavior. If the page is dynamic, wait for a selector that confirms the intended state before capture.

Does Microlink automatically remove cookie banners?

Not all of them. Microlink says its adblock blocks ads, trackers, and third-party consent requests before rendering. That can prevent some third-party consent interfaces from appearing, but a banner implemented by the website itself may remain. Microlink distinguishes automatic request blocking from dismissing first-party banners in its Screenshot API use-case documentation.

Choose the method based on what you need the screenshot to show: blocking stops matching requests from loading; CSS changes an element’s visibility; clicking a control changes the page’s state. Hiding a banner with CSS is not the same as accepting consent, and these capture options do not establish anything about a site’s legal compliance.

Choose the right option for the page

Situation Microlink option Effect and caveat
A third-party ad, tracker, or consent service is cluttering the capture adblock Blocks matching requests before rendering; a site’s own first-party banner may still appear. It is documented as on by default.
A known first-party banner should be invisible styles Inject CSS such as display: none !important. This affects appearance only; verify the selector on the target page.
The page has a close, dismiss, or accept control click Clicks a selector before capture and may change page state. Use it only when that resulting state matches your screenshot goal.
A custom page action is needed scripts Runs JavaScript in the page context before capture. Use when styles or a declarative click do not express the required action.
The page or post-dismissal content loads asynchronously waitUntil and waitForSelector Wait for navigation readiness, then a specific element or state. Prefer a stable selector over an arbitrary delay when available.

Microlink documents these page controls in its API parameter reference. Check the current parameter syntax there before deploying a request.

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

Hide a first-party banner with CSS

Use this when the banner is a known element and you want it omitted visually, without clicking the site’s consent controls. Replace .cookie-banner with a selector that matches the actual page.

curl -G "https://api.microlink.io" 
  --data-urlencode "url=https://example.com" 
  --data-urlencode 'styles=.cookie-banner { display: none !important; }' 
  -o screenshot.png

Microlink’s screenshot API returns website captures through a REST request; its screenshot documentation covers output and page configuration. See the parameter reference for the current accepted options and output settings.

Dismiss a banner by clicking it

If the page exposes a close button or a consent control and the resulting page state is what you intend to capture, use click with its selector. Confirm that the selector is unique and that the action works on the page; changing consent state can affect what the site displays afterward.

curl -G "https://api.microlink.io" 
  --data-urlencode "url=https://example.com" 
  --data-urlencode 'click=button.cookie-dismiss' 
  -o screenshot.png

Use the selector syntax and parameter format in Microlink’s API documentation. Do not treat an automated click as proof that consent was properly obtained for any purpose outside the screenshot.

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

Use a script only for custom interactions

For a page that requires custom logic beyond a simple click or style, Microlink documents the scripts option for running JavaScript in the page context before capture. The exact script should be specific to the target page and tested against its current markup. Avoid broad scripts that hide every dialog: they can remove content unrelated to the nuisance you are trying to suppress.

See Microlink’s parameter reference for the current script option syntax. If a selector-based click or injected CSS expresses the needed behavior, prefer that simpler configuration.

Rank #2
Free Fling File Transfer Software for Windows [PC Download]
  • Intuitive interface of a conventional FTP client
  • Easy and Reliable FTP Site Maintenance.
  • FTP Automation and Synchronization

Wait for the intended state on dynamic pages

Single-page applications and other asynchronously rendered pages can capture before the banner disappears or before the content you want is present. Treat interaction and timing as separate steps: use a click or style to prepare the page, then wait for a selector that signals the desired state. Microlink documents navigation lifecycle waits, selector waits, and fixed delays in its Screenshot API use-case guidance.

Where there is a stable selector for the visible content or post-dismissal state, use waitForSelector rather than guessing a fixed delay. Set waitUntil to an appropriate navigation readiness condition as well. A selector should indicate the state you actually want captured—for example, a main content element—not merely that the page shell has loaded.

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

When not to suppress the banner

Do not hide or dismiss the interface if the screenshot is meant to document or audit the consent experience. In that case, capture the banner as displayed and avoid CSS, clicks, or scripts that alter it. For ordinary page captures, decide whether you need to block third-party requests, hide a first-party element, or reproduce a user interaction; those are different outcomes.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. Its one-request capture handles consent banners, newsletter pop-ups, and chat widgets before the shot, with each cleanup step switchable. Only clean shots are billed; bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and responses identify the page verdict and billing status.

Here is a cURL capture of a page:

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

See the ScreenshotNeo API documentation for request options. The MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents and 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 free for 1,000 screenshots a month, with no card required.

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

Microlink plan context

Microlink’s API overview listed a free tier of 25 requests per day when reviewed on October 3, 2026. That is a vendor-stated plan limit, not an independent usage measurement, and plans can change; verify the current quota on Microlink’s API overview before relying on it. No independent performance result is established here.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Frequently Asked Questions

Can CSS hiding accept a visitor’s cookie consent?

No. CSS only changes what is visible in the capture; it does not itself accept consent.

Should I use a fixed delay or wait for a selector?

Use a stable selector tied to the desired page state when one is available; fixed delays are less specific.

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.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

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