Security Bot Protection CAPTCHA

How Bots Bypass CAPTCHAs and How to Protect Your Site

How bots bypass CAPTCHAs with Selenium, Playwright and solving services, and why layered protection with proof-of-work holds up against them.

Published May 07, 2026 · 6 min read · Updated Oct 10, 2026

Key takeaways

Modern bots bypass CAPTCHAs routinely
Bots get past image and checkbox CAPTCHAs with browser automation such as Selenium and Playwright, AI image solvers and paid solving services. Proof-of-work combined with a bot score holds up better, because it does not test recognition at all.
Recognition-based challenges have a ceiling
Image and text CAPTCHAs test a task that AI now handles reliably for many challenge types. Making them harder mostly hurts legitimate users, not determined bot operators.
Advanced bots are built to evade
Some bots are built specifically to slip past standard detection. Combining bot signal detection with proof-of-work means that a bot that gets past one layer still runs into the other.
Proof-of-work changes the cost equation
A cryptographic computation cannot be handed to a human CAPTCHA farm or solved faster by AI. It makes bot operations at scale expensive, however sophisticated the bot is.
On this page
  1. Why visual CAPTCHAs are easy targets
  2. How bots bypass CAPTCHAs
  3. Why recognition-based challenges don’t hold up
  4. What actually works: a layered defense
  5. TrustCaptcha: layers that work together
  6. In short
  7. Try TrustCaptcha for free
Share this post

Visual CAPTCHAs were built on one assumption: bots cannot read images the way people do. For a while, that was roughly true. It is not anymore. Getting past a visual CAPTCHA is now a well documented, low cost service that sells at a few dollars per thousand requests. For anyone defending a website, the useful questions are how these attacks work and which protection still holds.

Five steps of a bot run: the bot sends a request, the page loads in full, a challenge appears, a solving service returns the answer and the valid token is submitted with the form

Why visual CAPTCHAs are easy targets

Traditional CAPTCHAs set a visual challenge: read distorted text, find all the traffic lights, drag a puzzle piece into place. The idea was that computers could not reliably interpret ambiguous images and people could. Knowing how CAPTCHAs work at the level of the mechanism shows where that assumption breaks.

Computer vision models now beat humans on many image classification tasks, including the kinds of challenges CAPTCHA systems use. The W3C Inaccessibility of CAPTCHA note has pointed out reliability and accessibility problems with visual challenges since 2005, and the gap between human and machine performance on recognition tasks has only narrowed since then.

A CAPTCHA that relies purely on recognition can be beaten in two ways: automate the recognition, or pay a person to do it. Both are well established.

How bots bypass CAPTCHAs

Automation frameworks: Selenium, Playwright and headless browsers

Selenium and Playwright are browser automation tools built for testing web applications. They drive real browsers (Chrome, Firefox, Edge), run JavaScript, handle cookies and interact with page elements the way a person would. A bot running on Playwright sends real browser headers, loads the full page and fires click events where a user would click.

A CAPTCHA that only checks whether someone clicked a checkbox cannot tell a human click from an automated one. The browser is real, and so is the interaction.

Headless browsers go a step further. Chrome Headless runs without a visible window, which makes it faster and cheaper to scale, so attackers can run thousands of automated sessions in parallel on very little infrastructure.

CAPTCHA solving services

When automation alone cannot interpret a visual challenge, bots hand it to a solving service. There are two main models.

Human-powered farms pay workers to solve CAPTCHAs, with the bot passing challenges to them automatically and getting answers back within seconds. Prices sit at roughly $1 to $3 per thousand solutions. For valuable targets such as account registrations, ticket purchases or credential stuffing, that cost hardly matters to the attacker.

AI-based solvers are neural networks trained on large sets of CAPTCHA challenges. They run locally, cost almost nothing per request and solve most text-based challenges with near-perfect accuracy. Results on image challenges vary by type, but the gap to human performance keeps shrinking for all of them.

The recognition arms race

Image CAPTCHA difficulty has followed a clear pattern: challenges get harder, solvers get better, and legitimate users carry most of the friction. Math CAPTCHAs show this well. When they appeared, they looked like a sensible, simpler alternative to visual challenges. Today any basic automation script solves them. More complex image challenges hold out longer, but each version is eventually broken as models collect more challenge data.

Why recognition-based challenges don’t hold up

The problem is not that CAPTCHA designers lack ideas. Recognition is simply the wrong test. Any task that can be described precisely enough to train a machine on will be automated sooner or later, and that covers every visual challenge a CAPTCHA has ever used.

Harder challenges do not fix this; they only buy time. They also put a real burden on users with visual or cognitive disabilities, while bot operators wait for the next model.

Rate limiting and IP blocking help at the margins. Bots that run on Playwright at a human pace stay under simple rate limits, and larger operations rotate their IP addresses through residential proxy networks. These measures cut the volume of an attack, but they say nothing about the intent behind a request.

What actually works: a layered defense

Protection that holds against modern CAPTCHA bypass does not swap one recognition test for a harder one. It adds a layer that does not depend on recognition at all.

Four stacked protection layers, bot signal detection, proof-of-work, a honeypot with hidden trap fields and custom security rules, that let real users through and stop bots

Bot signal detection

Bot detection based on browser and behavior signals identifies automated traffic in many cases. Systems that turn these signals into a bot score can flag suspicious requests before any challenge is even shown.

This layer already stops a large share of bots and spam. More sophisticated operations are built specifically to slip past signal-based detection, which is why a second layer is needed.

Proof-of-work: the layer that can’t be outsourced

Proof-of-work asks the browser to compute something instead of recognizing something. The task is cryptographic: a hash computation that takes real processing time. A legitimate user’s browser completes it in the background while the user carries on.

For a single request, the cost is negligible. For a bot operation running thousands of sessions at once, the total computation adds up. Unlike image recognition, it cannot be passed to a human solving farm, because people cannot compute hashes by hand; only machines can. And unlike AI image solvers, there is no training shortcut. The work has to be done.

When risk signals go up, the proof-of-work difficulty rises automatically. Low-risk traffic passes quickly; suspicious traffic gets a harder task. Real users are not interrupted, because the computation runs while they fill in the form.

That is the difference from recognition-based approaches: the attacker’s cost grows with the size of the attack. Image CAPTCHAs get cheaper to bypass as models improve. Proof-of-work does not.

TrustCaptcha: layers that work together

TrustCaptcha runs both mechanisms in sequence. Every request is scored on browser and behavior signals. For real users, the proof-of-work task runs in the background. For requests with higher risk signals, the difficulty goes up automatically.

There is no image to forward to a solving farm and no checkbox for a Playwright script to click. The bot detection features handle the first filter, and proof-of-work handles the rest. A bot that evades one layer still hits the other.

On top of both, TrustCaptcha adds a honeypot check and supports custom security rules. Site operators use these rules to set specific conditions that trigger extra action. Rules can match conditions such as IP address, country, language, time zone, browser, operating system or device, so teams control how protection behaves in their own setup instead of relying only on automated scoring.

For sites looking at CAPTCHA alternatives without a Google dependency or GDPR exposure, TrustCaptcha runs in EU data centers and sets no cookies. A Data Processing Agreement is included with every plan, without separate legal negotiations.

In short

  • Visual CAPTCHAs can be bypassed reliably with browser automation frameworks like Selenium or Playwright, or through CAPTCHA solving services priced below $3 per thousand challenges.
  • Making image challenges harder mainly affects legitimate users. It does not fix the underlying problem that recognition tasks can be automated.
  • Bot signal detection already stops a large share of bots and spam. More sophisticated operations are built to slip past it, which makes a second layer necessary.
  • Proof-of-work is the layer that holds when detection fails. It requires real computation that cannot be farmed out to people or sped up by AI.
  • A CAPTCHA like TrustCaptcha that combines bot signal detection, proof-of-work and custom security rules makes bypass attempts expensive and easier to spot. Whether the attack relies on automation, solving services or advanced evasion, at least one layer comes into play.

Try TrustCaptcha for free

Your users should not have to solve puzzles to prove they are human, and you should not have to choose between a smooth experience and reliable protection. Try TrustCaptcha for free for 14 days: verification without puzzles that runs while users fill in the form, and bot protection that holds up against modern bypass attempts.

FAQs

Can bots actually bypass CAPTCHAs?
Yes, regularly and cheaply. Automation frameworks like Selenium and Playwright drive real browsers that pass most visual checks. Challenges that need image recognition go to CAPTCHA solving services, which charge roughly $1 to $3 per thousand solutions. That is why recognition alone no longer protects a form.
What is a CAPTCHA solving service?
A CAPTCHA solving service takes a challenge, passes it to a human worker or an AI solver and returns a valid answer within seconds. Human-powered services pay workers per solution; AI solvers are trained on large sets of past challenges. Both are widely available and inexpensive, which is a problem for any CAPTCHA that relies on recognition.
Why do image CAPTCHAs fail against modern bots?
Image CAPTCHAs test recognition: identifying objects in photos or reading distorted text. Machine learning models now handle these tasks reliably. Once recognition can be automated, the only lever left is a harder challenge, and that hits human users harder than bots using trained models or solving services.
What is proof-of-work and why does it resist CAPTCHA bypass?
Proof-of-work asks the browser to compute a cryptographic task instead of solving a visual one. For a single request it takes milliseconds. For a bot running thousands of parallel sessions, the total computation becomes expensive. Better AI models cannot avoid that cost, and human workers cannot take it over. The difficulty also rises with the observed risk.
Does detecting Selenium or Playwright fully stop CAPTCHA bypass?
No. Bot signal detection catches many bots, but more advanced operations are built specifically to slip past it. A second layer (proof-of-work) makes sure that even a request that passes detection still pays a real computational cost. Neither layer covers both kinds of attack on its own.
How should I protect my site against CAPTCHA bypass?
Combine two layers: bot scoring based on browser and behavior signals, and proof-of-work. If a bot evades detection, it still has to do the computation. If the proof-of-work difficulty is set low, the bot score still flags suspicious patterns. Neither layer covers both kinds of attack on its own. TrustCaptcha is built on this combination, with a honeypot check and custom security rules on top.
Does an invisible CAPTCHA still protect against bots?
That depends on how it works. An invisible CAPTCHA that relies only on behavior signals can be fooled by bots that imitate human patterns. One built on proof-of-work is harder to beat, because it requires real computation however human the bot appears. TrustCaptcha combines both approaches.

Stop bots and spam

Stop spam and protect your website from bot attacks. Secure your website with our user-friendly and GDPR-compliant CAPTCHA.