Playwright
Microsoft's open-source library for automating Chromium, Firefox and WebKit browsers.
Recommended for cross-browser end-to-end testing123 and as a browser tool that lets AI coding agents check their own work,456 plus scraping and site automation.789 A recurring caveat is that agents still miss UX problems even with Playwright in the loop,1011 and stock Playwright can be flagged as a bot and uses a lot of memory.12
Why people recommend it
AI agent testing · 3
Gives coding agents a real browser to test, screenshot and debug their own changes.
“I give agent either a simple browser or Playwright access to proper browsers to do this. It works quite well”
“told it to use PlayWright to control the browser and test by itself. After some hangs, that I had to stop manually, it did all by itself, and finally fixed the bug.”
Show 1 more
“it will write Playwright code to validate its work, and that becomes forever part of the codebase”
End-to-end testing · 3
A go-to tool for automated e2e tests that exercise the whole app.
“the big advantage of playwright is that it's cross-browser. It's still my go-to tool for automated testing”
“Playwright is a useful and justified abstraction in the testing workflow”
Show 1 more
“built in the browser with playwright. This continues to expose so much more than individual unit/tool tests”
Scraping and automation · 3
Used to scrape sites, intercept requests and automate routine web interactions.
“Nowadays, I use playwright to scrape websites for thing I care about”
“I use Playwright to intercept all requests and responses and have Claude Code navigate to a website”
Show 1 more
“automated the hell out of my most important interactions with the site using Playwright”
Cross-browser · 3
Runs tests across Chrome, Firefox and Safari/WebKit, including on Linux and Windows.
“the big advantage of playwright is that it's cross-browser. It's still my go-to tool for automated testing”
“I do use safari in my playwright tests”
Show 1 more
“I have multiple Playwright webkits on both Windows and Linux.”
Screenshot testing · 1
Its toHaveScreenshot comparison with proper waits has become fairly solid.
“Playwright's screenshot comparison (toHaveScreenshot) combined with proper wait strategies has gotten pretty solid.”
Caveats and dissent
Agent UX limits · 2
Even with Playwright, AI models struggle to catch UI and layout problems efficiently.
“even when you are aggressively using playwright in your agent loop”
“I've had some luck on the web app side if I use playwright or similar for the model to interact with”
Bot detection · 2
Stock Playwright is easily detected as a bot, so some pair it with antidetect browsers.
“Stock playwright screamed “I’m a bot” as anyone used it”
“things like playwright + camoufox”
Resource usage · 1
One team found the Node driver wasted significant memory and CPU.
“Stock playwright screamed “I’m a bot” as anyone used it”
Basic visual diffs · 1
Its pixelmatch-based comparison reports mismatched pixels but little about what changed.
“Playwright uses pixelmatch, which is decent but limited.”
Slow Safari runs · 1
Safari/WebKit tests take longer than Firefox and Chrome, at least on Linux.
“I do use safari in my playwright tests”
Tedious scraping · 1
One commenter replaced a tedious Playwright scraping approach with direct API calls.
“bypassed the old tedious playwright-based approach I used to rely on”
Often compared with
Who recommends it in their own words
From the makers not counted in the ranking
“I worked on Playwright before”
Threads where it came up
- The Safari MCP server for web developers 2 mentions
- Ask HN: What is your (AI) dev tech stack / workflow? (June 2026) 2 mentions
- I asked Claude Code to remove jQuery. It failed miserably 2 mentions
- Cloudflare Turnstile solver library (no headless browser required) 1 mention
- Apple's new 'Switch to Safari' campaign details why you should ditch Chrome 1 mention
- Adobe Creative Suite Cleanroom Port to Rust 1 mention
Data: playwright.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 41
“things like playwright + camoufox”
“I do use safari in my playwright tests”
“built in the browser with playwright. This continues to expose so much more than individual unit/tool tests”
“Playwright is a useful and justified abstraction in the testing workflow”
“even when you are aggressively using playwright in your agent loop”
“If I'm using something like figma or glean or playwright/chrome dev tools, plugin/skill/mcp - likely very useful.”
“I use MCP for some things, like Playwright; for web UI development”
“I use Playwright with Chrome DevTools Protocol in order to do performance testing and leak detection.”
“give it tools like playwright and github MCP for upstream context and search”
“I've had some luck on the web app side if I use playwright or similar for the model to interact with”
“if the app is web make it work very well with playwright for e2e ux tests.”
“the first layer speaks app UI specific language and runs playwright directly”
“tests it on the app with playwright or claude browser”
“production-grade testing (Jest, Cypress, Playwright, Selenium)”
“I spent a bunch of time setting up playwright testing at the start of my project”
“I also made the LLM write 60-odd unit tests and playwright tests running against production.”
“Where appropriate I have playwright take screenshots and review it as part of the chain.”
“another container with playwright with sse”
“automated the hell out of my most important interactions with the site using Playwright”
“creating that failing Playwright reproduction before any code changes”
“Stock playwright screamed “I’m a bot” as anyone used it”
“the big advantage of playwright is that it's cross-browser. It's still my go-to tool for automated testing”
“I have multiple Playwright webkits on both Windows and Linux.”
“told it to use PlayWright to control the browser and test by itself. After some hangs, that I had to stop manually, it did all by itself, and finally fixed the bug.”
“BullMQ/Playwright workers”
“We've already got tons of alternatives to it (Playwright, Puppeteer, etc.).”
“it will write Playwright code to validate its work, and that becomes forever part of the codebase”
“You also need end-to-end tests to actually run the app and verify it works, via Playwright”
“to iterate on UI tasks using Playwright”
“bypassed the old tedious playwright-based approach I used to rely on”
“doing playwright based extraction against anti-bot defenses”
“bug reproductions with screenshots via Playwright”
“have Claude debug websites using Docker + playwright + headless chrome”
“we and our customers use it heavily and reliably through playwright for various monitoring, testing and automation use cases.”
“I give agent either a simple browser or Playwright access to proper browsers to do this. It works quite well”
“tooling through Google Chrome Devtools MCP and Playwright to extract things and control the browser”
“I use Playwright to intercept all requests and responses and have Claude Code navigate to a website”
“Playwright has better anti-detection out of the box”
“For testing web apps I used to tell it "use playwright"”
“Did you tell it to use Playwright or agent-browser or anything like that?”
“Nowadays, I use playwright to scrape websites for thing I care about”