Video summary

I Bypassed reCAPTCHA in Playwright with Browserless — And Ran 5 Browsers Concurrently

Main summary

Key takeaways

Technology

Technological concept / problem

Automation frameworks like Playwright and Puppeteer often trigger bot-detection measures such as Google reCAPTCHA, blocking login and other actions that would normally be performed by a human.

The video frames this as a common pain point for automation test engineers, since reCAPTCHA is designed to prevent bots from authenticating.

Product / feature being demonstrated: Browserless

The video demonstrates Browserless (including Browserless as a Service) to:

  • Bypass CAPTCHA / bot detectors (specifically reCAPTCHA)
  • Scale automation by managing large browser pools, so you can run many automated browser sessions without handling browser binary/version issues yourself

Mentioned capabilities

  • Website automation and scraping
  • “Get past captchas and bot detectors” via Browserless + its browser queue / managed service

Tutorial / guide flow shown

1) Bypassing bot detection for automation (reCAPTCHA)

  • The demo uses a local app and a production-like app.
  • The production-like flow requires login plus “verify you are not a robot.”
  • For this test, bot detection is forced using a Cloudflare tunneling URL.

Code changes for CAPTCHA bypass

  • Enable Browserless stealth mode
  • Set proxy as residential
  • Use a “wait for CAPTCHA” step
  • Call browserless.solve_captcha (invoked via CDP / Chrome DevTools Protocol) to automatically solve the CAPTCHA during login

Outcome shown

  • CAPTCHA-enabled login succeeds automatically.
  • After the script runs, the employee list increases—indicating the login and subsequent automated actions worked.

2) Concurrent browser automation using a managed browser pool

  • Shows using Browserless to run multiple browser instances concurrently.
  • Key setup parameters shown in code:
    • Browserless token
    • Browserless endpoint URL for managed browsers
    • Maximum concurrent browsers (example: 5)
    • Retries / delay
  • A test scenario navigates to the app and creates “employees.”
  • Uses async control (e.g., a semaphore) to manage concurrency.
  • Connects to the managed browser via CDP.

Outcome shown

  • No browsers run on the local machine; sessions run “on the Browserless side.”
  • Increasing concurrency raises the rate of automated user creation (employee counts rise after refresh).

Key takeaways / analysis points

Browserless is presented as a way to:

  1. Avoid manual CAPTCHA handling in Playwright/Puppeteer automation by using an explicit CAPTCHA-solving API (solve_captcha)
  2. Run parallel automation safely and at scale using managed browser pooling, reducing operational overhead such as updates and broken browser/library/version management

Main speakers / sources

  • Source: The video creator speaking directly (no specific named person in the subtitles)
  • Product/company referenced: Browserless (including “Browserless as a Service”)
  • Platform referenced: Google reCAPTCHA
  • Infrastructure referenced: Cloudflare tunneling
  • Automation technologies referenced: Playwright, Puppeteer, CDP (Chrome DevTools Protocol)

Original video