Playwright Cloud Testing: BrowserStack, Sauce Labs & AWS (2026)

Last updated: June 27, 2026 · 8 min read

Playwright in the cloud gives you 100+ browser/OS/device combos without maintaining your own grid. This guide compares the top cloud providers in 2026 with setup, pricing, and best practices. Pair it with our Playwright Complete Guide, BrowserStack vs LambdaTest comparison, and GitHub Actions CI guide.

• Coverage — 100+ browser/OS combos vs. 3–5 on your own grid
• Speed — parallel execution across many machines
• Reliability — no maintenance burden
• Scale — burst from 10 to 1000 parallel sessions for releases
• Mobile testing — real iOS and Android devices

For the underlying setup, see our Playwright Complete Guide and Playwright framework setup with TypeScript.

BrowserStack

• Strengths: Real device coverage, enterprise-ready, strong support
• Pricing: $199/month (live), $99/month (automate)
• Playwright support: Native, well-documented
• Best for: Enterprise, mobile, customer-facing apps

Sauce Labs

• Strengths: Cross-browser + mobile, good free tier
• Pricing: $39/month (live), $149/month (automate)
• Playwright support: Native
• Best for: Startups, mid-market

LambdaTest

• Strengths: Cost-effective, fast-growing, good CI integration
• Pricing: $99/month (real devices)
• Playwright support: Native
• Best for: Cost-conscious teams, parallel-heavy workflows

AWS Device Farm

• Strengths: AWS integration, pay-as-you-go, supports Appium
• Pricing: $0.17/device minute
• Playwright support: Limited (more Appium-focused)
• Best for: AWS-native shops

Microsoft Playwright Cloud (preview)

• Strengths: First-party Microsoft integration
• Pricing: TBD (preview)
• Playwright support: Native
• Best for: Microsoft shops

For a deep head-to-head, see BrowserStack vs LambdaTest.

Step 1 — Get credentials

Sign up at browserstack.com and grab your userName and accessKey from Settings → Access Keys.

Step 2 — Set environment variables

export BROWSERSTACK_USERNAME="your_username"
export BROWSERSTACK_ACCESS_KEY="your_access_key"

Step 3 — Update Playwright config

// playwright.config.ts
import { defineConfig, devices } from '@playwright/test';

export default defineConfig({
  projects: [
    {
      name: 'browserstack-chrome',
      use: {
        ...devices['Desktop Chrome'],
        connectOptions: {
          wsEndpoint: `wss://cdp.browserstack.com/playwright?caps=${encodeURIComponent(JSON.stringify({
            browser: 'chrome',
            os: 'Windows',
            os_version: '11',
            browser_version: 'latest',
            name: 'Playwright smoke test',
            build: 'playwright-build-1',
          }))}`,
        },
      },
    },
  ],
});

Step 4 — Run

npx playwright test --project=browserstack-chrome

// playwright.config.ts
export default defineConfig({
  projects: [
    {
      name: 'sauce-chrome',
      use: {
        ...devices['Desktop Chrome'],
        connectOptions: {
          wsEndpoint: `wss://ondemand.us-west-1.saucelabs.com:443/playwright?caps=${encodeURIComponent(JSON.stringify({
            browserName: 'chrome',
            platformName: 'Windows 11',
            browserVersion: 'latest',
            'sauce:options': { name: 'Playwright test', build: 'playwright-build-1' },
          }))}`,
        },
      },
    },
  ],
});

export default defineConfig({
  projects: [
    {
      name: 'lambdatest-chrome',
      use: {
        ...devices['Desktop Chrome'],
        connectOptions: {
          wsEndpoint: `wss://cdp.lambdatest.com/playwright?capabilities=${encodeURIComponent(JSON.stringify({
            browserName: 'chrome',
            platform: 'Windows 11',
            'LT:Options': { build: 'Playwright build', name: 'Playwright test' },
          }))}`,
        },
      },
    },
  ],
});

AWS Device Farm is more Appium-focused, but Playwright works through the WebDriver protocol:

const driver = await new chrome.DriverSession(
  'https://prod.us-west-2.devicefarm.amazonaws.com',
  'arn:aws:devicefarm:us-west-2:123456789:test-grid:MyProject',
  { platformVersion: '1.20.0' }
);

Realistically, AWS Device Farm is weaker for Playwright than the dedicated testing platforms.

GitHub Actions with BrowserStack

- name: Run Playwright on BrowserStack
  run: npx playwright test
  env:
    BROWSERSTACK_USERNAME: ${{ secrets.BROWSERSTACK_USERNAME }}
    BROWSERSTACK_ACCESS_KEY: ${{ secrets.BROWSERSTACK_ACCESS_KEY }}

GitHub Actions with Sauce Labs

- name: Run Playwright on Sauce Labs
  run: npx playwright test
  env:
    SAUCE_USERNAME: ${{ secrets.SAUCE_USERNAME }}
    SAUCE_ACCESS_KEY: ${{ secrets.SAUCE_ACCESS_KEY }}

For full CI patterns, see our GitHub Actions Selenium CI guide.

Do

• Use parallel execution aggressively (50+ parallel sessions for CI)
• Cache dependencies to reduce cloud minutes
• Use retries only for known-flaky tests
• Store credentials in secrets, never in code
• Capture video + traces for debugging

Don't

• Don't run the full suite on every PR (use a smoke subset)
• Don't use cloud for local development (use local browsers)
• Don't ignore cloud provider rate limits
• Don't commit test artifacts (videos, traces) to git

Mistake 1 — Not caching dependencies

Cloud runners download node_modules on every run. Cache them with actions/cache or cache: 'npm' in setup-node.

Mistake 2 — Running everything on every commit

Smoke on every PR. Full E2E nightly. E2E pre-release.

Mistake 3 — Not handling timeouts

// playwright.config.ts
use: {
  actionTimeout: 15000,
  navigationTimeout: 30000,
}

Mistake 4 — Sharing state across parallel sessions

Each test should have isolated state. Don't share databases or browser profiles.

Mistake 5 — Ignoring rate limits

Use retries with exponential backoff.

Mistake 6 — Not monitoring costs

Cloud testing can be expensive. Track usage and set budget alerts.

1. Use parallel execution aggressively — 100 tests in 10 parallel sessions = 1/10 the runtime.
2. Shard tests across machines for >50 parallel sessions.
3. Use Docker for self-hosting when you exceed 500 tests/day.
4. Cache browser binaries between runs.
5. Run smoke tests only in CI — full E2E nightly.
6. Track per-test cost with annotations and prune expensive tests.

1. Audit your local tests — find local-only dependencies and hardcoded URLs.
2. Externalize configuration — replace page.goto('https://staging.example.com') with page.goto(process.env.BASE_URL).
3. Add secrets management via GitHub Actions secrets.
4. Run smoke tests first — verify in the cloud before scaling.
5. Migrate the full suite incrementally — Week 1 smoke, Week 2 critical paths, Week 3 full regression.
6. Add parallel execution — 10x speedup is common.
7. Set up monitoring — execution time, failure rate, cost per test, uptime.
8. Optimize continuously — Trace Viewer, dependency caching, parallel workers.
9. Set up alerts — failure rate > 5%, slow runs, downtime.
10. Document the setup — local vs cloud runs, debugging, costs.

• Playwright Complete Guide
• Playwright Framework Setup with TypeScript
• Playwright Page Object Model in TypeScript
• BrowserStack vs LambdaTest
• GitHub Actions Selenium CI
• Playwright Interview Questions