What Is Friendly Captcha? – Definition and How It Works

Learn how Friendly Captcha's proof-of-work approach replaces puzzles, and what that means for automated access.

Friendly Captcha is a CAPTCHA alternative that asks the browser to perform computational work instead of asking the user to solve a puzzle. It is positioned around privacy and accessibility.

1. Proof of Work, Not Recognition

The mechanism is different in kind from image CAPTCHAs:

1. The widget requests a puzzle from the service.
2. The browser computes a solution — a cryptographic search, not a visual task.
3. The solution is submitted with the form.
4. The site's server verifies it against the service.

The user does nothing but wait, usually briefly. There is no image to classify, no slider to drag, and no accessibility barrier from visual tasks.

2. Enforcement by Cost

Because the defence is computational, the economics are explicit: each attempt costs CPU time. One submission is trivial; thousands become expensive.

Difficulty can also scale with suspicion, so a client that looks automated is asked to do more work. That is the same escalation principle other products apply to puzzle difficulty, expressed in compute instead.

The implication for automation is unusual: the challenge is solvable by a script — it is arithmetic, not perception — but solving it at scale costs real resources, which is exactly the intended deterrent.

3. Identifying It

The .frc-captcha class and the frc-captcha-solution form field are unambiguous, and the widget markup is present in the initial HTML.

4. Why Sites Choose It

• Privacy positioning — less client fingerprinting than score-based alternatives, and EU-oriented data handling.
• Accessibility — no visual or audio task, so no accessibility fallback needed.
• No user friction — nothing to solve, which improves form completion.
• GDPR comfort — a common driver for European deployments.

Seeing it therefore suggests a site that has weighed privacy and accessibility, which often correlates with a more permissive stance on ordinary access generally.

5. What It Does and Does Not Stop

Stops: high-volume automated form submission, because per-attempt compute cost makes mass abuse uneconomic.

Does not stop: a low-volume determined actor, since the work is computable. Nor does it identify who the client is, since it deliberately collects less than fingerprinting products.

That trade is the point — it accepts weaker identification in exchange for privacy, and relies on cost rather than certainty.

6. Practical Notes for Collection

It guards forms, not content. Like most widget CAPTCHAs, it sits on submissions — contact forms, signups, comments. Public page collection is typically unaffected.

A slow page load may be the work running. In a browser context, the computation takes time. A pipeline with tight timeouts can time out mid-computation and record a failure that was actually just slow.

Do not automate form submission behind it. The compute cost is a deliberate barrier to exactly that, and the form is almost never the data you need.

7. Compared With Score-Based CAPTCHAs

Neither is strictly better; they defend against different volumes and accept different privacy trade-offs.

8. Summary

Friendly Captcha replaces puzzles with browser-side proof of work, verified server-side, and is chosen for privacy, accessibility, and zero user friction.

Recognise it from the .frc-captcha element and frc-captcha-solution field; it deters mass form abuse through per-attempt compute cost rather than by identifying clients, so it rarely affects public page collection — but allow generous timeouts, because the computation genuinely takes time in a browser.

Potential Related Glossary

• DataDome
• Browser Fingerprints
• Headless Browser
• Concurrency vs Parallelism