> For the complete documentation index, see [llms.txt](/llms.txt)

# Connection URLs and Endpoints

# Connection URLs and Endpoints

Browserless uses HTTPS for [BrowserQL](/browserql/start) and [REST APIs](/rest-apis/intro), and WebSocket connections for [BaaS](/baas/start) sessions. Pick the host that matches your fleet, then choose the path that matches your browser or API.

- A Browserless API token from your [account dashboard](https://browserless.io/account/)

## Shared Fleet vs. Private Fleet URLs

Browserless operates two types of fleets. Use the URLs that match your account type.

### Shared fleet

The shared fleet uses regional URLs shared across all customers on that plan.

| Region | URL |
|---|---|
| US West | `https://production-sfo.browserless.io` |
| Europe UK | `https://production-lon.browserless.io` |
| Europe Amsterdam | `https://production-ams.browserless.io` |

For WebSocket connections, replace `https://` with `wss://`.

### Private fleet (Enterprise private deployments)

Enterprise customers with a dedicated fleet connect through `chrome.browserless.io`, which routes to your assigned region. Regional variants are available for lower latency.

| Region | URL |
|---|---|
| Default (auto-routed) | `https://chrome.browserless.io` |
| US West (SFO) | `https://chrome-us-west.browserless.io` |
| US East (NYC) | `https://chrome-us-east.browserless.io` |
| Europe UK (LON) | `https://chrome-eu-uk.browserless.io` |
| Europe Amsterdam (AMS) | `https://chrome-eu-ams.browserless.io` |

For WebSocket connections, replace `https://` with `wss://`.

> **Warning**
> Using a private fleet token against a shared fleet URL returns HTTP 401 Unauthorized. Always use your dedicated fleet URL with your private fleet token.

See [Load Balancing](/enterprise/private-deployment/load-balancing) for more on private fleet regional endpoints.

## BrowserQL Endpoints

BrowserQL uses HTTPS POST requests. Choose the endpoint that matches the browser you want.

| Purpose | Shared fleet URL | Notes |
|---|---|---|
| Chromium | `https://production-sfo.browserless.io/chromium/bql?token=YOUR_TOKEN` | Standard BrowserQL queries |
| Chrome | `https://production-sfo.browserless.io/chrome/bql?token=YOUR_TOKEN` | Chrome-based BrowserQL sessions |
| Stealth | `https://production-sfo.browserless.io/stealth/bql?token=YOUR_TOKEN` | Stealth-enabled BrowserQL sessions |

The same path patterns apply on dedicated fleets. Replace the shared-fleet host with `chrome.browserless.io` or your regional dedicated URL.

If you use the BQL IDE, Browserless handles the endpoint for you. If you reconnect to an existing BQL session, use the `browserQLEndpoint` returned by the `reconnect` mutation rather than building the reconnect URL by hand.

## BaaS v2 Endpoints

To connect Puppeteer or Playwright to Browserless, use a WebSocket URL. These endpoints launch a browser and hand control back to your library.

| Library | Example URL |
|---|---|
| Puppeteer / Chromium | `wss://production-sfo.browserless.io?token=YOUR_TOKEN` |
| Playwright Chromium over CDP | `wss://production-sfo.browserless.io?token=YOUR_TOKEN` |
| Playwright native Chromium | `wss://production-sfo.browserless.io/chromium/playwright?token=YOUR_TOKEN` |
| Playwright Chrome | `wss://production-sfo.browserless.io/chrome?token=YOUR_TOKEN` |
| Playwright Firefox | `wss://production-sfo.browserless.io/firefox/playwright?token=YOUR_TOKEN` |
| Playwright WebKit | `wss://production-sfo.browserless.io/webkit/playwright?token=YOUR_TOKEN` |

Use the nearest region to reduce latency. See [Load Balancers](/baas/infrastructure/load-balancers). All endpoints require the `?token=` query parameter.

## REST API Endpoints

Browserless provides REST API endpoints for common operations.

```bash
https://production-sfo.browserless.io/screenshot?token=YOUR_TOKEN
https://production-sfo.browserless.io/pdf?token=YOUR_TOKEN
https://production-sfo.browserless.io/content?token=YOUR_TOKEN
```

## Launch Parameters and Options

See [Launch Parameters](/overview/launch-parameters) for query parameters, the encoded JSON `launch` payload, and common options.

## FAQ & Troubleshooting

<details>
<summary>How do I get started with Browserless?</summary>

Sign up for a free account at [browserless.io](https://browserless.io/signup/email?plan=free), get your API token, and follow the [Quickstart guide](/browserql/getting-started) for BQL or the [BaaS guide](/baas/start) for Puppeteer/Playwright.

</details>

<details>
<summary>What's the difference between BQL and BaaS?</summary>

BQL is a GraphQL API for declarative browser automation with built-in stealth. BaaS runs your existing Puppeteer or Playwright scripts on managed browsers. See [comparison](/overview/comparison) for details.

</details>

## Next steps

  <a href="/browserql/getting-started" className="next-step-card-link">
    
      <h3 className="next-step-card-title">BQL Quickstart</h3>
      run your first BrowserQL query
    
  </a>
  <a href="/baas/start" className="next-step-card-link">
    
      <h3 className="next-step-card-title">BaaS Quickstart</h3>
      connect Puppeteer or Playwright to Browserless
    
  </a>