USE CASE · SCRAPING

Scrape pages that need a real browser surface.

For authorized data collection, Remote Browser can render JavaScript-heavy pages, preserve session state, handle downloads, and provide evidence when extraction breaks.

Create a scraping browser See automation API

extract.tsremote

await page.goto("https://example.com/dashboard", { waitUntil: "networkidle" });
const rows = await page.locator("[data-row]").evaluateAll((items) =>
  items.map((item) => item.textContent?.trim())
);
console.log(JSON.stringify(rows, null, 2));

JSrendered pages

proxyegress options

filesdownloads

Rendered extraction

Wait for client-side content before extracting text, links, table rows, or structured page state.

Session-aware workflows

Use profiles for authorized dashboards, owned accounts, and workflows where repeated login would be brittle.

Failure evidence

Capture screenshots or recordings when extraction fails so the team can see whether the page changed, blocked, or errored.

Workflow

From browser creation to evidence.

Authenticate responsibly

Use the browser only for sites and accounts where the workflow is authorized.

Extract after render

Use Playwright or Puppeteer locators after the page reaches a stable rendered state.

Throttle and terminate

Respect target limits, control runtime with idle timeout, and close sessions when collection finishes.

FAQ

Short answers for searchers and AI crawlers.

Does Remote Browser bypass rules automatically?

No. Remote Browser provides browser infrastructure. You are responsible for site terms, rate limits, robots guidance where applicable, and legal use.

Can it download files?

Yes. Browser workflows can interact with downloads, and session evidence can help debug file-related flows.

When is fetch better than browser scraping?

Use fetch when the data is available through stable APIs or static HTML. Use a browser when rendering or interaction is required.

Keep moving through the browser automation map.