Skip to content

Browser Automation

Shape the page first. Set the device, wait for the right state, click, and run scripts — declarative options on the same request, applied before capture.

Overview

Declarative steps, then the capture.

Pass automation options on any product call — device, waitUntil, waitForSelector, click, scripts. The page is shaped into the right state before the screenshot, PDF, or data is taken.
  • One product call — the page is prepared, then captured
  • device emulates viewport, DPR and user-agent presets
  • waitUntil / waitForSelector settle dynamic, client-rendered pages
  • click, scroll and scripts drive the UI before extraction
  • Escalate to a function only when the flow is truly custom
Parameters

Options that shape the page.

Examples

Shape the page, then capture.

device presets the viewport before the screenshot is taken.
Emulate a phone
import createClient from 'microlink.io'

const microlink = createClient({
  apiKey: process.env.MICROLINK_API_KEY
})

const { url } = await microlink.screenshot(
  'https://example.com',
  { device: 'iPhone 11', fullPage: true }
)
Related features

Pair automation with these.

Browser Functions

Run JavaScript with Puppeteer and npm packages. No infrastructure, no servers.

Web Scraping

Extract structured JSON from any webpage using CSS selectors. URL → JSON in one request.

Proxy Resolution

PRO
Automatically bypass Cloudflare, DataDome, Akamai and more. We handle the hard part.

Antibot Detection

PRO
Know exactly who blocked your request and why — 30+ antibot and CAPTCHA providers.

Adblock & Cookie Banners

Ads and trackers blocked, cookie banners dismissed automatically — on by default, on every plan.

FAQ

How is automation different from a function?

Automation is declarative: device, waitUntil, click, scroll and scripts are options on a normal product call, so the page is shaped and then captured. A function is imperative code you author when a flow is too custom for those options.

Do automation options work on the free plan?

Yes. device, waitUntil, waitForSelector, click, scroll and scripts all work on the free tier. Pro raises the time budget and lets you combine them with proxy, custom headers and configurable TTL.

When should I use waitUntil vs waitForSelector?

Use waitUntil to gate on a navigation event like networkidle0 for whole-page settling. Use waitForSelector when you know the exact element that signals the page is ready, which is more precise for single-page apps.

Can I run my own JavaScript before capture?

Yes. Pass scripts to inject and execute JavaScript in the page context before the product reads it — useful for dismissing banners or expanding sections. For return values and npm packages, use the function parameter instead.

Does automation compose with other products?

Yes. The same options apply to screenshot, pdf, markdown and extract, and they stack with proxy, headers and ttl on Pro so one call can emulate a device, unblock the target, and cache the result.