reCAPTCHA
Google's challenge system, now mostly an invisible score from 0.0 to 1.0 rather than a puzzle, drawing on the signals a Google-scale presence can see.
reCAPTCHA is Google's, and that provenance is its defining advantage: it scores you using signals visible to a company whose cookies, accounts and scripts are present across an enormous share of the web. When it judges a request, it is not working only from what happens on the page in front of you; it can weigh your standing with Google itself. No independent challenge vendor has that vantage point, and it is why the same request scores differently depending on whether a real Google session is in the background.
The versions are genuinely different products and the distinction matters for what you do about them. The visible v2, the I'm not a robot checkbox and the image grids, is a challenge you can be made to solve. The now-dominant v3 shows nothing at all: it observes the session and returns a score from 0.0 to 1.0 that the site's own code acts on, deciding its own threshold and its own response. Against v3 there is nothing to solve, which is the whole point, only a score to be high enough, so the goal shifts entirely from answering a puzzle to not being scored down in the first place.
That reframing is the useful part. Because v3 is a score and not a gate, the tactics are the ones that raise trust generally: a genuine browser, a clean address, coherent fingerprint and locale, human pacing, and where legitimate, an actual signed-in Google session carrying ordinary history. Everything that makes you look like a normal user of the web raises the number, and everything mechanical lowers it, before any single request is judged.
The economics of the obvious shortcut are worth stating plainly. Paid solving services return an answer token for the visible challenges, but they treat the symptom: against v3 you keep being scored low, keep paying per solve, and add latency to every request without repairing the underlying trust. They are a fallback for a genuinely stuck v2 flow, not a strategy for a v3 score you could instead raise.
One provenance note that cuts against the market's assumptions: a fresh datacenter address with no Google relationship at all often scores worse on v3 than an ordinary residential one, because the absence of any normal footprint is itself the signal. Trust here is partly a history you either have or conspicuously lack.
Frequently asked questions
What is the difference between reCAPTCHA v2 and v3?
v2 is the visible challenge, the checkbox and the image grids, something you can be asked to solve. v3 is invisible: it watches the session and returns a score from 0.0 to 1.0 that the site acts on however it chooses. Against v2 you solve a puzzle; against v3 there is no puzzle, only the task of not being scored low, which needs an entirely different approach.
Do CAPTCHA solving services work on reCAPTCHA v3?
Poorly, because there is nothing to solve. Solvers return tokens for the visible v2 challenges; v3 issues a continuous trust score, so you keep scoring low, keep paying per attempt, and add latency without fixing the cause. They make sense as a fallback for a stuck v2 flow, not as a way to satisfy a v3 score you could raise instead.
Why does reCAPTCHA trust some visitors instantly?
Because Google can see more than the page. Its cookies, accounts and scripts span much of the web, so a visitor with an ordinary Google footprint arrives already trusted, while one with none, a fresh datacenter address and no history, arrives suspect. The absence of a normal footprint is itself a negative signal, which is a vantage point no independent vendor has.
How do I raise my reCAPTCHA v3 score?
Look like a normal web user across every layer: a real browser rather than a bare client, a clean residential address, a fingerprint and locale that agree with it, human-paced interaction, and where legitimate an actual signed-in session with ordinary history. The score rewards coherence and penalises everything mechanical, so it is raised before a request is judged, not fixed afterwards.
Back to the full glossary.