Scraping Browser

Run your Puppeteer or Playwright scripts against a remote, managed browser instead of one you provision and maintain yourself. Connect over a single WebSocket endpoint and keep the rest of your automation code unchanged.

01What it did

• Connected any Puppeteer or Playwright script to a remote browser over WebSocket, no local browser to install or update.
• Handled concurrency and browser availability, so scripts scaled without managing infrastructure.
• Rotated fingerprints across a residential network to reduce detection on protected sites.

02Original connection example

The original code samples from this page, preserved as-is. Both still connect correctly; see the Browser Sessions page for current examples and parameters.

// Puppeteer
const puppeteer = require('puppeteer-core');
const connectionURL = 'wss://browser.zenrows.com?apikey=<YOUR_ZENROWS_API_KEY>';

const browser = await puppeteer.connect({ browserWSEndpoint: connectionURL });
const page = await browser.newPage();
await page.goto('https://example.com');
console.log(await page.title());
await browser.close();

// Playwright
const { chromium } = require('playwright');
const connectionURL = 'wss://browser.zenrows.com?apikey=<YOUR_ZENROWS_API_KEY>';

const browser = await chromium.connectOverCDP(connectionURL);
const page = await browser.newPage();
await page.goto('https://example.com');
console.log(await page.title());
await browser.close();

03Frequently asked questions

Does the WebSocket endpoint still work?

Yes. wss://browser.zenrows.com is the same endpoint Browser Sessions uses today; nothing about the connection itself changed with the rename.

What's different under the new name?

Mainly positioning: Browser Sessions is documented and billed as one of the platform's core primitives alongside Fetch, Extract, and Batch, rather than a separate product.