Friendly Captcha is a German, privacy-oriented CAPTCHA based on proof-of-work. A Web Worker solves a cryptographic puzzle while the visitor clicks once, or not at all in zero-click mode. It uses no image grids and no tracking cookies. As with ALTCHA, the easiest path is to let the computation run and collect the response.
How to identifyLink to How to identify
- A
<div class="frc-captcha" data-sitekey="...">container - An "I am human" button showing a progress ring, then a checkmark
- A hidden
frc-captcha-responseinput (the name can be changed) - v2 API calls to
https://global.frcapi.com/api/v2/captcha/ - The
widget.module.min.jsscript or the Friendly Captchasdk - A "Protected by Friendly Captcha" notice
Widget modesLink to Widget modes
- Smart (default): session signals decide whether a click is needed.
- One-click: the visitor clicks once, then the computation completes.
- Zero-click: the widget finishes by itself.
How it worksLink to How it works
- Using the site key, the widget fetches a challenge from Friendly Captcha.
- A Web Worker solves a VDF / proof-of-work puzzle. This is CPU work, not a task for the visitor.
- The resulting string is stored in
frc-captcha-responseor a custom field. - The site's server checks it with its API key at
https://global.frcapi.com/api/v2/captcha/siteverify. - A response expires and can be used only once.
Free bypass methodsLink to Free bypass methods
| Method | What it does | Success Rate | Link |
|---|---|---|---|
| Real browser (Playwright/DrissionPage) | Lets the official widget do the work, then reads the response | ~100% | g1879/DrissionPage |
| Patchright / Camoufox | Stealth browsers for the smart and zero-click modes | 85-95% | Kaliiiiiiiiii-Vinyzu/patchright-python |
| Official JS SDK | Runs the SDK in Node or a headless browser and calls getResponse() |
~100% | FriendlyCaptcha/friendly-captcha-sdk |
| undetected-chromedriver | Selenium with detection patches | 80-95% | ultrafunkamsterdam/undetected-chromedriver |
Practical approachLink to Practical approach
- Load the page in a real browser with JavaScript on.
- If the mode needs a click, move to the widget naturally and click it.
- Wait for the
completedstate, or keep checking the hiddenfrc-captcha-responsefield. - Send the form with that response and leave the widget alone afterwards.
- In zero-click mode there is nothing to do but wait for the response to appear.
Practical tipsLink to Practical tips
- Solving is CPU-bound and can take a second or two on modest machines. Set timeouts with that in mind.
- The widget needs Web Workers and WASM. Some locked-down headless setups disable them, and the widget then fails.
- Responses expire and are single-use, so read the value just before submitting.
- Smart and zero-click modes still weigh risk signals. A clean IP and an ordinary browser profile help.
- The server verifies responses with a secret API key, so there is no shortcut: the proof-of-work has to be solved for real.