Playwright
Hacker ApprovedThe most recommended of 12 browser automation tools
A fast, easy-to-set-up browser automation and testing tool with auto-waiting and screenshots, widely used to let AI coding agents check their UI work; tests can still be brittle.
A fast, easy-to-set-up browser automation and testing tool with auto-waiting and screenshots, widely used to let AI coding agents check their UI work; tests can still be brittle.
165 people gave an opinion
- recommend it
- 137
- criticize it
- 28
- approval share
- 83%
Recommended in 12 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Owned for 3 months
Median of the 3 owners who said how long they have had it.
Each square is one year.
Why it carries the badge
- 137 people recommend itNeeds 10 or more, met.
- 4.9 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 12 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Lets AI agents verify UI
“Same playwright is phenomenal. You can also have the agent browse with MCP to figure out the workflow, then bang out a repeatable playwright script for it.”
Comment from 16 Apr 2026 in “Show HN: Libretto – Making AI browser automations deterministic” “Playwright seems to do fine at visual stuff? It takes screenshots and the model evaluates them. That's most of what I use Playwright for.”
Comment from 24 Mar 2026 in “Show HN: ProofShot – Give AI coding agents eyes to verify the UI they build” “Getting them to take screenshots with playwright/puppeteer and look at them as part of their development iteration cycle works well.”
Comment from 11 Mar 2026 in “Why does AI tell you to use Terminal so much?” - Comment from 11 Feb 2026 in “Show HN: JavaScript-first, open-source WYSIWYG DOCX editor”
- Comment from 24 Mar 2026 in “Show HN: ProofShot – Give AI coding agents eyes to verify the UI they build”
- Comment from 12 Apr 2026 in “Why AI Sucks at Front End”
- Comment from 13 Feb 2026 in “I asked Claude Code to remove jQuery. It failed miserably”
- Comment from 24 Mar 2026 in “Show HN: ProofShot – Give AI coding agents eyes to verify the UI they build”
- Comment from 15 Jun 2026 in “Ask HN: Has anyone replaced Claude/GPT with a local model for daily coding?”
- Comment from 13 Feb 2026 in “I asked Claude Code to remove jQuery. It failed miserably”
- Comment from 17 Jul 2026 on Hacker News
- Comment from 5 Jul 2026 in “The Safari MCP server for web developers”
Auto-waiting and clean API
“playwright provides a lot of benefits that we like in terms of being code - like auto-waiting, good syntax for a lot of operations”
Comment from 8 Jun 2026 in “Launch HN: Intuned (YC S22) – Build and run reliable browser automations as code” “Playwright's screenshot comparison (toHaveScreenshot) combined with proper wait strategies has gotten pretty solid.”
Comment from 28 Jan 2026 in “Ask HN: Do you use a visual debugging AI tool?” “Things that have helped me elsewhere: Playwright with page.wait_for_selector rather than networkidle”
Comment from 28 Apr 2026 in “Scraping 241 UK council planning portals – 2.6M decisions so far” - Comment from 5 May 2026 in “Computer Use Is 45x More Expensive Than Structured APIs”
- Comment from 24 Dec 2025 in “Show HN: Vibium – Browser automation for AI and humans, by Selenium's creator”
Screenshots, traces and visual comparison
“Playwright seems to do fine at visual stuff? It takes screenshots and the model evaluates them. That's most of what I use Playwright for.”
Comment from 24 Mar 2026 in “Show HN: ProofShot – Give AI coding agents eyes to verify the UI they build” “Getting them to take screenshots with playwright/puppeteer and look at them as part of their development iteration cycle works well.”
Comment from 11 Mar 2026 in “Why does AI tell you to use Terminal so much?” “Playwright's screenshot comparison (toHaveScreenshot) combined with proper wait strategies has gotten pretty solid.”
Comment from 28 Jan 2026 in “Ask HN: Do you use a visual debugging AI tool?” - Comment from 6 Jan 2026 in “Visual regression tests for personal blogs”
Fast and easy setup
“Playwright really simplifies getting setup. It won't work for everyone, but within 30 seconds Playwright will download it's needed browsers along with a test runner.”
Comment from 24 Dec 2025 in “Show HN: Vibium – Browser automation for AI and humans, by Selenium's creator” “playwright got a lot of things right. one of the big ones was a fast websockets+json way to drive the browser”
Comment from 24 Dec 2025 in “Show HN: Vibium – Browser automation for AI and humans, by Selenium's creator” “Building simple web-scraping scripts with nbb driving Playwright is so much faster than using any other stack”
Comment from 28 Jul 2026 in “Steel Bank Common Lisp version 2.6.7” - Comment from 12 Jan 2026 in “Lightpanda migrate DOM implementation to Zig”
- Comment from 24 Dec 2025 in “Show HN: Vibium – Browser automation for AI and humans, by Selenium's creator”
- Comment from 24 Mar 2026 in “What are the best headless browsers?”
What people warn about
Each mark is one comment
Tests brittle and finicky
“that kind of test tends to be brittle and annoying to write (I guess I don't have to write them anymore, but they are still brittle)”
Comment from 2 Aug 2026 in “Developers are attached to tools because tools encode trust” “Tools like Selenium and Playwright have introduced explicit waits, which observe the DOM. This helps, but doesn't solve everything.”
Comment from 23 Jan 2026 in “The Slow Death of Productivity: Why Time.sleep() Is Killing Your Automation” “getting them to a state where they reliably pass has always been so much more finicky than it should be”
Comment from 2 Apr 2026 in “Show HN: Playwright Test Studio” - Comment from 2 Jun 2026 in “Show HN: NUA an agent that tests for product correctness”
Inefficient, floods agent context
“I've had some luck on the web app side if I use playwright or similar for the model to interact with but still far from efficient.”
Comment from 26 Aug 2026 in “Ask HN: What is one simple thing LLMs are insanely bad at?” “My main issue with Playwright (and chrome-devtools) is that they pollute the context with a massive amount of stuff.”
Comment from 3 Feb 2026 in “Two kinds of AI users are emerging. The gap between them is astonishing” “duct-taping browser automation (Playwright, CDP, MCP wrappers) onto an interface designed for humans”
Comment from 15 Mar 2026 in “Let your Coding Agent debug the browser session with Chrome DevTools MCP” - Comment from 7 Feb 2026 in “Show HN: Smooth CLI – Token-efficient browser for AI agents”
Detected by anti-bot defenses
“Rolling your own Playwright / Puppeteer cluster works until target sites deploy new JA4/TLS fingerprints”
Comment from 2 Oct 2026 in “Ask HN: Who is hiring? (October 2026)” “the project that my CC is working on now is a playwright clone that is not easily detectable”
Comment from 24 Mar 2026 in “OpenClaw Is a Security Nightmare Dressed Up as a Daydream”
Other browser automation tools people recommend
The four most recommended other browser automation tools, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Playwright | 137 | 28 | 83% | 12 | 3 mo3 owners | Approved |
| Playwright CLI | 19 | 1 | 95% | 5 | — | Approved |
| Selenium | 15 | 5 | 75% | 5 | — | Approved |
| Puppeteer | 14 | 16 | 47% | 10 | — | — |
| Stagehand | 13 | 2 | 87% | 7 | — | Approved |
What people said
40 of the 199 comments that mention it, newest first. Each links to the original comment.
“Rolling your own Playwright / Puppeteer cluster works until target sites deploy new JA4/TLS fingerprints”
“I've had some luck on the web app side if I use playwright or similar for the model to interact with but still far from efficient.”
“that kind of test tends to be brittle and annoying to write (I guess I don't have to write them anymore, but they are still brittle)”
“Building simple web-scraping scripts with nbb driving Playwright is so much faster than using any other stack”
“works better with how models are already trained on playwright to interact with browser”
“Really like this approach to keeping Playwright deterministic while still getting AI-assisted fixes via PRs”
“Once it tracks down the bugs - boom! You have an end to end test to add to your suite.”
“with a Playwright task which attempts to surface errors to the agent who introduced the previous code block”
“playwright provides a lot of benefits that we like in terms of being code - like auto-waiting, good syntax for a lot of operations”
“This beats writing playwrights which often break when a major UI update happens.”
“guardrails not only in textfiles but much more in executable code (linters, tests, dependency checks, playwright, ...)”
“Playwright tests are an absolute delight to read, write and maintain on properly accessible sites”
“Things that have helped me elsewhere: Playwright with page.wait_for_selector rather than networkidle”
“I just created a playwright cli skill in about 30 minutes and I've been using it for months.”
“Same playwright is phenomenal. You can also have the agent browse with MCP to figure out the workflow, then bang out a repeatable playwright script for it.”
“Ask it to take control of a browser using something like Playwright and use the UI itself like an end user would”
“what turned me off it was the likelihood anyone not already using Playwright would have to update their frontend”
“getting them to a state where they reliably pass has always been so much more finicky than it should be”
“Playwright seems to do fine at visual stuff? It takes screenshots and the model evaluates them. That's most of what I use Playwright for.”
“If you want something that mostly just works, Playwright is still the easiest default.”
“often the playwright skill will verify using DOM API instead of wasting tokens on screenshots”
“the project that my CC is working on now is a playwright clone that is not easily detectable”
“I've also had Claude run javascript code on a page using playwright-cli to figure out why a button wasn't working as it should.”
“I give agent either a simple browser or Playwright access to proper browsers to do this. It works quite well”
“duct-taping browser automation (Playwright, CDP, MCP wrappers) onto an interface designed for humans”
“Getting them to take screenshots with playwright/puppeteer and look at them as part of their development iteration cycle works well.”
“I've found Playwright tests to be a decent way of getting Claude to do what you're talking about.”
“Ask it to install and use Playwright to confirm rendering and flow. ... it definitely helps cut down on bugs.”
“using Claude Code with Playwright tests as the feedback signal is a clever way to grind through the spec without losing your mind”
“exposing Playwright-level primitives to a foundation model is fundamentally the wrong interface”
“My main issue with Playwright (and chrome-devtools) is that they pollute the context with a massive amount of stuff.”
“Playwright's screenshot comparison (toHaveScreenshot) combined with proper wait strategies has gotten pretty solid.”
“Tools like Selenium and Playwright have introduced explicit waits, which observe the DOM. This helps, but doesn't solve everything.”
“Playwright has a driver for example and its far faster and less resource hungry than Chrome.”
“It comes with a nice overview page that shows all the failed tests including traces and screenshots.”
“Playwright really simplifies getting setup. It won't work for everyone, but within 30 seconds Playwright will download it's needed browsers along with a test runner.”
“playwright got a lot of things right. one of the big ones was a fast websockets+json way to drive the browser”
“it's fast, easy to use, has popular features like auto-waiting, integrated video recording”
“Playwright in vision mode (as opposed to using the default a11y tree) and Codex for understanding worked best”
“This, paired with chrome devtools and playwright, had been a real productivity booster for me, and is quite fun.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.