Playwright is free. The framework is open source under the Apache License 2.0, and the capabilities teams assume are paid extras (cross-browser testing, parallel execution, and sharding) all ship in the free runner. What costs money is the infrastructure Playwright runs on: your CI compute, and, if you choose it, a managed cloud-browser grid. Here is the honest breakdown of where the money actually goes.
Is Playwright free to use?
Yes. Playwright is licensed under the Apache License 2.0, with copyright held by Microsoft, and the published npm package declares the same license independently. You can use it commercially, modify it, and run it at any scale with no license fee.
Three capabilities that teams often expect to sit behind a paywall are included at no cost in the open-source test runner:
Cross-browser testing across Chromium, Firefox, and WebKit from one API, on Windows, macOS, and Linux (source).
Parallel execution. The runner starts several worker processes that run at the same time (source).
Sharding, which splits one suite across multiple machines (source).
So the framework is free, and so are its headline testing features.
So where does Playwright actually cost money?
The pattern is simple: Playwright gives you the scaling primitives for free, but the machines those primitives run on are billed. Sharding exists to run a suite "on multiple machines," and those machines are either your CI runners or a managed grid.
| What you use | Free in Playwright? | Where the cost lands |
|---|---|---|
| The framework (Apache 2.0) | Yes | None |
| Cross-browser drivers | Yes | None |
| Parallel workers | Yes | None |
| Sharding across machines | Yes (the feature) | The machines it runs on |
| CI runner minutes | Not applicable | Billed per minute by your CI provider |
| Managed cloud-browser grid | Not applicable | Azure App Testing, billed per test minute |
What does Microsoft's managed Playwright grid cost?
Microsoft's managed cloud-browser service for Playwright is Playwright Workspaces, now part of Azure App Testing. Its published rate is per test minute, by operating system: $0.01 per Linux test minute and $0.02 per Windows test minute, on top of a free tier (Azure App Testing pricing). A free trial covers 30 days and 100 test minutes; after that, you pay only for the overage.
One naming trap to avoid: the older standalone product, "Microsoft Playwright Testing," was retired in 2026 and folded into Azure App Testing. The $0.0002 per-minute figure still circulating online belongs to that dead service. Budget against Azure App Testing's current rates, not the retired one.
Why doesn't parallelizing more lower your Playwright bill?
Because a managed "test minute" measures the total test-execution time across a run, billed by the second, not the wall-clock time you wait. Microsoft's own worked example: 50 tests at 12 seconds each is billed as 10 test minutes (50 x 12 / 60) (source). Adding workers finishes the suite faster, but the metered total stays the same. More parallelism buys speed, not a smaller invoice. Microsoft's docs make the same point from the other direction: adding worker processes does not always shorten suite completion time, because client compute, network latency, and test complexity all intervene.
That is the single most useful thing to understand before you size a Playwright budget.
How does Playwright compare with commercial testing tools on cost?
Carefully, because the products are not the same shape. Playwright is a free framework; commercial options bundle that framework value into paid SaaS. Cloud grids such as BrowserStack, LambdaTest, and Sauce Labs price by parallel sessions or subscription tiers, and their public pages put real numbers behind a sign-in or a sales conversation, so confirm the current rate on the vendor's own pricing page rather than trusting a third-party summary. A reporting and analytics layer is a separate category again: Cypress Cloud, the dashboard for the open-source Cypress runner, starts at $67 per month billed annually. That is a useful reference for what a paid test-tooling SaaS costs, but it is not a like-for-like substitute for a cloud-browser grid.
For a buyer, the practical move is to compare by category (framework, then CI compute, then managed grid, then reporting SaaS), not by a single headline price.
What is the real total cost of running Playwright?
The largest line in a mature Playwright program usually carries no price tag at all: the engineering time to write and maintain the suite. Flaky-test triage and selector upkeep tend to outweigh infrastructure spend, though no neutral public figure exists, so treat it as a staffing assumption rather than a quoted number.
Below the human cost, CI compute is the most universal infrastructure expense. Hosted runners are billed per minute, and paid plans bundle a fixed monthly allowance that resets each cycle (GitHub Pro includes 3,000 Actions minutes per month). Check your provider's live per-minute rate for the runner class you use, because rates vary by operating system and machine size.
The verdict: what should you budget for Playwright?
The license is free; the minutes are not. Adopt Playwright expecting to pay for three things, in rough order of size: the engineering time to build and maintain tests, the CI minutes your suite burns on every run, and, only if you want managed cloud browsers, Azure App Testing's Playwright Workspaces at $0.01 to $0.02 per test minute. The framework will never send you an invoice. Your CI provider will.
Sources
Playwright LICENSE (Apache 2.0), Microsoft, GitHub, 2026. https://github.com/microsoft/playwright/blob/main/LICENSE
playwright npm package metadata (license Apache-2.0), 2026. https://www.npmjs.com/package/playwright
Playwright README (cross-browser support), 2026. https://github.com/microsoft/playwright
Playwright documentation, parallelism and sharding, 2026. https://playwright.dev/docs/test-parallel
Playwright Workspaces overview, Microsoft Learn, 2026. https://learn.microsoft.com/en-us/azure/app-testing/playwright-workspaces/overview-what-is-microsoft-playwright-workspaces
Azure App Testing pricing (billing model and free trial), 2026. https://azure.microsoft.com/en-us/pricing/details/app-testing/
Playwright Workspaces free trial, Microsoft Learn, 2026. https://learn.microsoft.com/en-us/azure/app-testing/playwright-workspaces/how-to-try-playwright-workspaces-free
Determine optimal configuration, Microsoft Learn, 2026. https://learn.microsoft.com/en-us/azure/app-testing/playwright-workspaces/concept-determine-optimal-configuration
About billing for GitHub Actions, GitHub Docs, 2026. https://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions
Cypress pricing, 2026. https://www.cypress.io/pricing
Email Us
Call Us
