Connection URL Patterns

Browserless supports various connection URL patterns for different use cases and library integrations. Understanding these patterns helps you choose the right connection method for your specific automation needs.

Pattern Examples

Pattern	Description	Example
Puppeteer/Playwright CDP	Standard WebSocket connection for Puppeteer and Playwright CDP mode	wss://production-sfo.browserless.io?token=TOKEN
Playwright Native	Playwright server mode connection with native protocol support	wss://production-sfo.browserless.io/chromium/playwright?token=TOKEN
Stealth Mode	Enhanced bot detection evasion with stealth capabilities	wss://production-sfo.browserless.io/chrome/stealth?token=TOKEN

Connection URL Builder

Use the interactive builder below to generate the appropriate connection URL for your use case:

BaaS Connection URL Builder

Library:

PuppeteerPlaywright

Browser:

ChromiumChrome

Stealth Mode:

DisabledEnabled

Region:

US WestEurope UKEurope Amsterdam

API Token:

Connection URL:

wss://production-sfo.browserless.io/?token=YOUR_TOKEN

Code Snippet:

const browser = await puppeteer.connect({
  browserWSEndpoint: 'wss://production-sfo.browserless.io/?token=YOUR_TOKEN',
});

Pattern Details

Puppeteer/Playwright CDP Pattern

The standard WebSocket connection pattern used by most Puppeteer and Playwright CDP implementations. This is the most common pattern for browser automation.

Use cases:

• Standard web scraping
• Form automation
• Screenshot generation
• PDF creation

Playwright Native Pattern

Playwright's native protocol connection that provides enhanced performance and additional features not available in CDP mode.

Use cases:

• High-performance automation
• Advanced Playwright features
• Network interception
• Mobile device emulation

Stealth Mode Pattern

Enhanced connection pattern with built-in bot detection evasion capabilities.

Use cases:

• Sites with sophisticated bot detection
• E-commerce automation
• Social media automation
• Data extraction from protected sites

Regional Endpoints

All patterns support the same regional endpoints for latency optimization:

Region	Endpoint	Location
US West	production-sfo.browserless.io	San Francisco, USA
Europe UK	production-lon.browserless.io	London, England
Europe Amsterdam	production-ams.browserless.io	Amsterdam, Netherlands