Playwright logo
Verified by SaaSOffers
FreeDeveloper & IT

Playwright: Free and Open Source Testing Framework

Free & Open Source
Verified November 2026

Microsoft end-to-end testing framework for modern web apps across all browsers.

Claim Free Deal

Free. No credit card required

✓ Verified deal✓ No spam, ever✓ 10,000+ startups

Deal Highlights

Free & Open Source
Deal Value
Instant Access
Access Type
Developer & IT
Category

The Playwright Offer

Offer: Free & Open Source. Requirement: none. There is no account, no promo code and no signup link. You install the package and use it.

Playwright is released by Microsoft under the Apache-2.0 license. The framework, its test runner, the bundled MCP server and CLI, and the VS Code extension cost $0. What can cost money is the infrastructure around it: CI minutes, cloud browsers and hosted reporting. This page prices those parts so you know what a real setup costs.

We checked these facts against Playwright's official docs and GitHub repository in November 2026. Prices for paid services come from each vendor's own pricing page, checked the same month.

Playwright drives Chromium, Firefox and WebKit through a single API. You can use it as a test runner (Playwright Test), as a library for browser scripts, or as a browser tool for AI agents. The GitHub repository was created on November 15, 2019. In November 2026 it had 99,138 stars and 6,791 forks. The latest release was v1.64.1, published October 14, 2026. The @playwright/test npm package was downloaded 104,750,936 times in the week of October 26 to November 1, 2026.

Playwright homepage

Playwright Pricing and the Costs Around It

Playwright itself has no paid tier. The table lists the free parts first, then the paid services teams commonly add.

ComponentPrice billed yearlyBilled monthlyKey limits
Playwright Test (@playwright/test)$0$0Apache-2.0; Chromium, Firefox and WebKit on Windows, macOS and Linux
Playwright MCP and playwright-cli$0$0Bundled since v1.62 (npx playwright mcp, npx playwright cli)
VS Code extension$0$0Test authoring and debugging inside VS Code
Trace viewer (trace.playwright.dev)$0$0Loads the trace in your browser, sends no data externally
GitHub Actions, Linux 2-core runnerNo yearly plan$0.006 per minuteFree in public repos; private repos get $12 (Free) or $18 (Team) of included usage a month
GitHub Actions, macOS 3 or 4-core runnerNo yearly plan$0.062 per minuteAbout 10.3 times the Linux rate
Azure Playwright Workspaces (cloud browsers)Pay as you goRate not shown in page text30-day free trial with 100 browser minutes, 1 trial workspace per subscription

System requirements

Playwright Test needs Node.js 22.x, 24.x or 26.x. Supported systems are Windows 11+, Windows Server 2019+ or WSL, macOS 14 (Sonoma) or later, and Debian 12 / 13 or Ubuntu 22.04 / 24.04 / 26.04 on x86-64 or arm64. Python, Java and .NET versions exist too. Python uses the pytest-playwright plugin and runs with the pytest command.

Bundled browser versions

The README in November 2026 listed Chromium 158.0.8127.2, Firefox 159.0 and WebKit 27.2. Playwright updates these versions with each release, so after an upgrade you may need to rerun npx playwright install. The docs show sample download sizes of about 281 MB for Chromium, 187 MB for Firefox and 180 MB for WebKit. Branded channels are also supported: chrome, msedge, chrome-beta, msedge-beta and their dev and canary builds.

What the free framework doesn't include

  • Hosted results. The HTML report and traces are files. You store them yourself, for example as CI artifacts (500 MB of artifact storage on GitHub Free, 2 GB on GitHub Team).
  • Real Safari. WebKit is built from the WebKit main branch, not the branded Safari app.
  • Branded Firefox. Playwright tracks recent Firefox Stable with its own build. Branded Firefox is not supported.
  • Physical phones. Mobile testing uses emulation with device descriptors such as Pixel 5 and iPhone 12.
  • Free CI on private repos. Runner minutes on private repositories are billed once the included usage runs out.
  • A cloud browser grid. Running hundreds of browsers at once needs your own machines or a paid service such as Azure Playwright Workspaces or BrowserStack.

What a 5-Person Team Pays

The framework is $0, so the real bill is CI. Assume a private GitHub repository on the GitHub Team plan, a Playwright suite that takes 10 minutes on one Linux 2-core runner, and 20 runs a workday across 22 workdays.

  • Runs: 20 x 22 = 440 runs a month
  • Minutes: 440 x 10 = 4,400 minutes
  • Cost: 4,400 x $0.006 = $26.40
  • Minus GitHub Team included usage: $26.40 - $18 = $8.40 a month, or $100.80 a year

The $18 included usage is shared with your other workflows, so builds and deploys reduce it. On a public repository the same runs cost $0.

The same team on a hosted test dashboard

The Cypress App is also free (MIT license). Teams that want hosted run history usually add Cypress Cloud. Its free Starter plan includes 500 test results a month. Say each run has 40 tests:

  • Results: 440 x 40 = 17,600 a month, or 211,200 a year
  • Cypress Cloud Team: $799 a year, includes 120,000 results a year
  • Overage: (211,200 - 120,000) = 91,200 x $6 per 1,000 = $547.20
  • Total: $799 + $547.20 = $1,346.20 a year, on top of the same CI minutes

With Playwright, the equivalent is uploading the HTML report and trace.zip files as CI artifacts. That stays inside the 2 GB GitHub Team artifact allowance if you keep retention short. You give up a hosted dashboard with flake analytics. You keep $1,346.20.

What a 10-Person Team Pays, All Three Browsers

Now a 10-person team runs 40 builds a workday. The suite takes 12 minutes per browser, and they shard by browser into 3 parallel jobs (Chromium, Firefox, WebKit). Each job is billed separately.

Option A: all 3 browsers on every run

  • Runs: 40 x 22 = 880 a month
  • Minutes: 880 x 12 x 3 = 31,680
  • Cost: 31,680 x $0.006 = $190.08, minus $18 = $172.08 a month, or $2,064.96 a year

Option B: Chromium on pull requests, all 3 browsers on merges to main

Assume 30 of the 40 daily runs are pull requests and 10 are merges.

  • Pull requests: 30 x 22 x 12 = 7,920 minutes
  • Merges: 10 x 22 x 12 x 3 = 7,920 minutes
  • Total: 15,840 x $0.006 = $95.04, minus $18 = $77.04 a month, or $924.48 a year

Option B saves $95.04 a month, $1,140.48 a year, and still tests Firefox and WebKit before code reaches main.

One more check on runner choice. WebKit runs on Linux in Playwright, so you rarely need macOS runners. The same 7,920 merge minutes on macOS 3 or 4-core runners would cost 7,920 x $0.062 = $491.04 a month, against $47.52 on Linux.

For comparison, BrowserStack Automate starts at $99 a month billed annually ($1,188 a year) on its Desktop plan. That buys a hosted browser grid. Option B on Linux costs less than that ($924.48 a year). Option A ($2,064.96 a year) costs more, so at that volume either cut the browser matrix on pull requests or compare it with a hosted grid.

How Playwright Test Works

Parallel runs and sharding

By default, test files run in parallel, and tests inside one file run in order in the same worker process. Set fullyParallel: true to run tests inside a file in parallel too. To split a suite across machines, run npx playwright test --shard=2/3 on each of 3 jobs. Workers shut down after a test failure, so the next tests start in a clean environment.

Browsers and devices

Tests run headless and in parallel across Chromium, Firefox and WebKit by default. Add --headed to watch the browser, or --project=chromium to run 1 browser. Mobile projects such as "Mobile Chrome" and "Mobile Safari" use device descriptors such as Pixel 5 and iPhone 12.

Debugging tools

  • UI Mode (npx playwright test --ui): watch mode, live step view and time travel debugging.
  • HTML report (npx playwright show-report): opens on its own only when tests fail.
  • Trace viewer (npx playwright show-trace path/to/trace.zip): a film strip and DOM snapshots for each action, plus console output, network requests and errors. Trace modes include 'off', 'on', 'on-first-retry' and 'retain-on-failure'.

AI agent support

Since v1.62, Playwright bundles the Playwright MCP server and playwright-cli. The MCP server lets agents control pages through structured accessibility snapshots, with no vision model or screenshots needed. The README describes the CLI as built for coding agents and more token-efficient than MCP. Version 1.64 added WebMCP: tools a page registers through the experimental WebMCP browser API show up to the agent as webmcp_<tool>. Pass --no-webmcp to turn that off.

Recent features worth knowing

  • v1.64: --shuffle randomizes test order, testProject.default keeps a project configured but not run by default, and locator.within() scopes one locator inside another.
  • v1.63: tests that share a named lock never run at the same time, across files, workers and projects. locator.visible() replaces the :visible pseudo-class.
  • v1.62: retryStrategy: 'isolated' runs all retries at the end in a single worker. Snapshots can be stored as WebP.
  • v1.61: a Credentials virtual authenticator answers WebAuthn (passkey) prompts, and traces now include WebSocket requests.

Who Playwright is for

  • Web app teams shipping weekly or faster that need checks on signup, checkout and login flows before each release.
  • Teams with Safari users. WebKit coverage catches layout and API bugs that Chromium-only suites miss, without buying Mac hardware.
  • Startups on a tight CI budget. A 10-minute suite run 440 times a month costs $8.40 over GitHub Team's included usage.
  • Polyglot teams. The same browser API exists for TypeScript, JavaScript, Python, Java and .NET.
  • Teams building AI agents that need a browser. The bundled MCP server and CLI handle that without a separate tool.
  • Apps with passkey login. The v1.61 virtual authenticator tests WebAuthn flows in the page.

Playwright installation docs

When Playwright is the wrong pick

  • Teams that need real iPhones and Android phones. Emulation does not reproduce device hardware. A device cloud such as BrowserStack is the better fit.
  • Teams that must certify on branded Safari or branded Firefox. Playwright ships its own WebKit and Firefox builds.
  • Teams already deep in Cypress with a working suite and Cypress Cloud analytics they rely on. Rewriting a large suite costs more engineering time than it saves.
  • Non-developers. Playwright is code-first. UI Mode helps with debugging, but tests are code that lives in a repository.

Playwright vs Alternatives

PlaywrightCypressSeleniumBrowserStack Automate
Framework price$0, Apache-2.0$0, MIT (Cypress App)$0, source freely availablePaid service
Paid add-onNone from Playwright; Azure Workspaces optionalCypress Cloud Team $799/yr (120,000 results), Business $3,199/yrNone requiredFrom $99/month billed annually (Desktop)
Free hosted tierTrace viewer only, runs in your browserStarter: 500 results a month, 10 usersNoneNone found for Automate
BrowsersChromium, Firefox, WebKit, Chrome, EdgeChrome-family, Firefox; WebKit experimental; Electron deprecatedMajor browsers via W3C WebDriverHosted desktop browsers; mobile on Desktop & Mobile plan ($175/month billed annually)
LanguagesTS/JS, Python, Java, .NETJavaScript/TypeScriptJava, Python, C#, Ruby, JavaScript, KotlinDepends on framework used
Parallel runsBuilt in (workers, --shard)Through Cypress CloudSelenium GridPlan-based parallel tests

Cypress's WebKit support needs the experimentalWebKitSupport flag and the playwright-webkit package, and it lacks cy.origin() and Test Replay. Selenium uses Selenium Manager, a Rust command-line tool, to download drivers and browsers for you. BrowserStack's Desktop plan lists unlimited Automate users and testing minutes.

Playwright setup tips

  1. Start with the scaffold. npm init playwright@latest asks for a language (TypeScript is the default), a tests folder, an optional GitHub Actions workflow and whether to install browsers. It creates playwright.config.ts and an example.spec.ts.
  2. Cap CI workers. The docs' sample config uses workers: process.env.CI ? 2 : undefined, which matches a 2-core runner.
  3. Skip the full Chromium on headless CI. npx playwright install --with-deps --only-shell installs the headless shell plus OS dependencies and saves download time.
  4. Record traces only on retry. trace: 'on-first-retry' gives you a trace.zip for flaky failures without slowing passing runs.
  5. Shard by browser, not by habit. Run Chromium on pull requests and all 3 engines on main. In the 10-person example that cut $95.04 a month.
  6. Stay on Linux runners. WebKit runs on Linux. macOS minutes cost $0.062 against $0.006.
  7. Use --shuffle once a week. Random order exposes tests that depend on each other.
  8. Pin the version. Each release updates browser builds. Upgrade on purpose, then rerun npx playwright install.

How to get the Playwright offer

  1. Install Node.js 22.x, 24.x or 26.x.
  2. In your project folder, run npm init playwright@latest (or yarn create playwright / pnpm create playwright).
  3. Accept the browser install, or run npx playwright install later.
  4. Run npx playwright test, then npx playwright show-report.
  5. Optional: add the GitHub Actions workflow the installer offers, and the VS Code extension from the Marketplace.

There is nothing to redeem and no SaaSOffers link to click. Playwright is free for anyone, from Microsoft's own repository, under the same Apache-2.0 terms.

Who Is This Deal For?

Early-Stage Startups

Seed and pre-seed companies looking to move fast without overspending on tools.

Growing SaaS Teams

Series A+ companies scaling their stack and optimizing software costs.

Solo Founders

Indie hackers and bootstrapped founders who need enterprise tools at startup prices.

Get Free & Open Source off Playwright

Free for all startups. Claim instantly.

Sign Up & Claim

Frequently Asked Questions

Everything you need to know about this startup deal.

Get the weekly deals digest

New verified startup deals every week. No spam, ever. Unsubscribe anytime.