Why Are CAPTCHAs So Hard? Because They Stopped Working on Machines in 2014

The honest answer is uncomfortable and it is on the record, published by the company that runs most of them.

In December 2014, Google’s own security blog announced that “today’s Artificial Intelligence technology can solve even the most difficult variant of distorted text at 99.8% accuracy. Thus distorted text, on its own, is no longer a dependable test.”

That was twelve years ago. The puzzle stopped separating humans from machines, and it kept being shown to humans.

The task was always designed to take something from you

This is not a conspiracy theory. It is in the founding paper.

Von Ahn, Blum, Hopper and Langford (2003), at Eurocrypt, wrote in their abstract:

“Much like research in cryptography has had a positive impact on algorithms for factoring and discrete log, we hope that the use of hard AI problems for security purposes allows us to advance the field of Artificial Intelligence.”

And: “captchas based on these AI problem families, then, imply a win-win situation: either the problems remain unsolved and there is a way to differentiate humans from computers, or the problems are solved and there is a way to communicate covertly on some channels.”

Five years later the same group made the harvesting explicit. Von Ahn, Maurer, McMillen, Abraham and Blum (2008), in Science, described reCAPTCHA feeding unrecognised words from book scans into CAPTCHA challenges:

• reCAPTCHA transcription accuracy: 99.1% at word level - 216 errors in 24,080 words
• Standard OCR on the same words: 83.5% - 3,976 errors
• Professional human “key and verify” transcription: more than 99%

So unpaid users matched professional transcribers. In one year, the paper reports, people solved more than 1.2 billion CAPTCHAs, deciphering over 440 million words - “equivalent to over 17,600 books manually transcribed.”

Google bought reCAPTCHA in September 2009 and said why on its own blog: to “increase fraud and spam protection for Google products but also to improve our books and newspaper scanning process.”

The labour harvesting was designed, disclosed and celebrated. That part is documented fact.

What it costs you, measured

Searles, Prapty and Tsudik (2025), at the Symposium on Usable Security and Privacy, ran a 13-month live field study on a real account-creation service. Participants were unwitting - going about ordinary business, not told they were in a study.

Over 3,600 distinct users; 9,141 valid records; over 9,000 reCAPTCHAv2 challenges.

Challenge type	Mean	Median
Checkbox only	1.85 s	1.67 s
Image challenge	10.3 s	8.20 s
All sessions	3.53 s	1.83 s

About 20% of sessions escalated to an image challenge. That 10.3 seconds is the number that matches your experience of the thing; the 3.53-second average is dominated by the 80% of cases where you just clicked a box.

The very large number, and why we are not printing it

That paper is also the source of a figure now everywhere: 819 million hours spent on reCAPTCHA, worth $6.1 billion in free wages, and a separate claim of $888 billion in cookie value to Google.

We traced how they were built, and we are not printing them as findings.

The hours figure assumes 100 million reCAPTCHAs per day, every day, from 2009 to 2023 - a rate taken from an archived 2010 Google FAQ and held constant for fourteen years. It also uses a US federal minimum wage of $7.5; the actual figure has been $7.25 since July 2009.

The arithmetic is internally consistent. The inputs are not defensible. And note the tension with the Science paper’s own 2008 figure of 1.2 billion CAPTCHAs in a year - about 3.3 million a day, not 100 million.

The $888 billion figure fails harder. It multiplies sessions by a per-cookie value drawn from a study measuring cookies over an average 279-day lifetime, so one user generates many sessions but one cookie. It uses that study’s mean of €2.522 when the median is €0.022 - a skew of roughly 115 times. And the value in question is publisher ad-impression revenue on a European ad exchange, not revenue accruing to Google from reCAPTCHA.

We are describing these numbers rather than repeating them, because they are the most widely circulated claims about CAPTCHAs and they do not hold up.

One more correction, in fairness to Google. We could find no current Google document stating that reCAPTCHA v2 image answers train its machine-learning models. Its current documentation says the opposite: “Data gathered is used only for reCAPTCHA’s operation and security, not for personalized advertising by Google.” The documented harvesting belongs to the text and book-scanning era. The image-era claim is an inference, and we are labelling it as one.

The machines already win

Searles and colleagues (2023), at the 32nd USENIX Security Symposium, had 1,400 participants solve 14,000 CAPTCHAs across modern schemes.

Human solving times ran from 3.1-4.9 seconds for a reCAPTCHA checkbox to 18.1-42.8 seconds for the harder puzzle schemes, with accuracy between 50% and 85% depending on scheme.

Against published bot performance: bots solved reCAPTCHA click in 1.4 seconds at 100% against humans at 3.1-4.9 seconds and 71-85%. On distorted text, bots managed under a second at 99.8% against humans at 9-15.3 seconds and 50-84%.

Important caveat: the bot figures in that comparison are taken from prior published attacks, not run by these authors. It is a literature comparison, not a head-to-head experiment.

Plesner, Vontobel and Wattenhofer (2024), accepted at COMPSAC, report: “we can solve 100% of the captchas, while previous work only solved 68-71%.” They also found “no significant difference in the number of challenges humans and bots must solve to pass.”

Their own conclusion notes the experiments covered 50 to 100 runs and recommends future work “possibly ranging in the hundreds or thousands.” A 100% rate over roughly a hundred runs is not a 100% rate in general.

The system also leans on something other than the puzzle. With cookies and browsing history present, the median number of challenges required dropped from 5.00 to 2.00. Which is the tell: the current version, reCAPTCHA v3, per Google’s own developer documentation, “will never interrupt your users” and instead “returns a score (1.0 is very likely a good interaction, 0.0 is very likely a bot),” with a default threshold of 0.5.

The puzzle was never the security. It is increasingly not even the mechanism.

Who pays most

Bigham and Cavender (2009), at CHI, tested audio CAPTCHAs with 162 participants - 89 blind, 73 sighted.

Group and format	First-try success	Mean completion
Blind, audio	43%	50.9 s
Sighted, audio	39%	22.8 s
Sighted, visual	nearly 80%	9.9 s

A blind user takes roughly five times as long and succeeds at about half the rate. An optimised non-visual interface raised blind first-try success to 68.5%, which shows the gap is a design failure rather than a law of nature.

The W3C reached the same place. Its document on the inaccessibility of CAPTCHA states: “All interactive approaches require users to perform a task believed to be relatively easy for humans but difficult for robots. Unfortunately the very nature of the interactive task inherently excludes many people with disabilities, resulting in a denial of service to these users.”

It names blind users, low-vision users, deaf and hard-of-hearing users - audio alternatives are distorted to the point of unintelligibility - users with cognitive disabilities, and non-English speakers.

And you can just buy your way past

Motoyama and colleagues (2010), at USENIX Security, measured the CAPTCHA-solving service market directly, submitting tens of thousands of challenges to eight services over months.

Verbatim: “the customer cost to have 1,000 CAPTCHAs solved is now commonly $2/1,000 and can be as low as $1/1,000.” Accuracy across services ran 80.45% to 98.62%, with a median response of 14 seconds.

On the worker side: “in 2007, CAPTCHA solving routinely commanded wages as high as $10/1,000, but by mid-2008 a typical offer had sunk to $1.5/1,000, $1/1,000 by mid-2009, and today $0.75/1,000 is common.” The average monthly payout to the top 100 workers at one service was $106.31, falling to $47.32 a month later.

That data is from 2009-2010 and we are not presenting it as current pricing. We could locate no peer-reviewed measurement of CAPTCHA-farm prices since. Every current figure we found was vendor marketing.

But the structural point survives: a determined attacker pays a fraction of a cent. You pay ten seconds.

What this leaves you with

They are hard because they have to be. Once machines read distorted text at 99.8%, the only way to keep a puzzle machine-proof is to make it human-hostile too. The difficulty you experience is the residue of a lost arms race.

They are not primarily testing the puzzle any more. Risk scoring, cookies and browsing history do much of the work; the challenge is what happens when the score is ambiguous.

The cost is unevenly distributed. Blind users pay roughly five times the time for half the success rate.

Be sceptical of the enormous dollar figures, including the ones in the peer-reviewed paper. They rest on a 2010 FAQ, a wage that does not exist, and a mean 115 times its own median.

And a real gap worth knowing: we could find no study measuring whether CAPTCHAs actually reduce abuse. The literature measures human cost, machine solvability and solver prices. What happens to spam when you remove the CAPTCHA appears to be essentially unstudied.

For another interface that spends your attention while you wait, see the psychology of waiting. For consent interfaces that ask you to agree to things you cannot read, see do people read terms and conditions and should I accept cookies.

Limitations of this article

We could not verify the “100 million per day” figure that drives the widely quoted hours claim. It is sourced to an archived 2010 Google FAQ we could not open. That is why we describe the extrapolation rather than repeat its output.

The bot-versus-human comparison mixes sources. The human data is the authors’; the bot data comes from prior published attacks.

The 100% solve rate rests on roughly 50-100 runs, by the authors’ own account, and required a VPN, simulated mouse movement and cookies.

The CAPTCHA-farm pricing is sixteen years old.

We could not confirm exact page numbers for the accessibility study, and we report the W3C document as the Group Draft Note it currently is, dated 16 December 2021 - not as a finished Working Group Note.

Two disclosures. The 2023 bot-comparison paper includes authors at Microsoft and a US national laboratory - one a Google competitor. The 2008 Science paper was written by reCAPTCHA’s founders about their own system, twelve months before Google bought it. And the paper making the $888 billion claim carries no funding statement or competing-interests declaration at all, which is itself notable in a paper naming a company.

For the adjacent problem of repeated account-entry tasks, RoboForm provides password storage and form autofill; it does not solve CAPTCHAs.