microsoft/playwright

Choose this fork only if you need its older, customized behavior. For most adopters, upstream Playwright is the safer choice because this fork is materially behind and heavily diverged.

Choose the upstream Playwright unless you specifically need this fork’s legacy patching and internal workflow customizations. This fork is too far behind upstream for most new adopters, but it can still make sense as a frozen, customized base for teams that already depend on it.

Choose this fork only if you need its custom browser/tooling changes and can absorb long-term maintenance. If you want current Playwright features, compatibility, and lower upgrade risk, upstream is the better default.

Prefer this fork only if its custom browser patches and workflow additions are required; otherwise upstream Playwright is the safer default because this fork is older, highly divergent, and likely to lag on fixes and browser updates.

Prefer this fork only if you need its specific trace/config/workflow changes or you are prepared to maintain a forked Playwright surface. If you want maximum compatibility, documentation support, and low-risk adoption, upstream is the safer choice.

Prefer this fork if you want Playwright adapted for MCP/agent workflows and are willing to trade upstream parity for custom tooling. Prefer upstream if you want the safest path for browser/test-runner updates and the least maintenance burden.

Prefer this fork only if you need its custom browser and workflow changes and can support ongoing rebasing. If you want a broadly current, low-maintenance Playwright base, upstream is the safer choice.

Choose this fork if your priority is AI/browser research workflows and richer page/network extraction. Choose upstream if you need the most current Playwright releases, stability, and low-merge-risk maintenance.

Choose this fork only if its custom browser patches or workflow changes are specifically valuable to you. For most adopters, upstream Playwright is the safer default because this fork is substantially behind and significantly diverged.