hCaptcha vs Turnstile, side by side.
hCaptcha and Cloudflare Turnstile both give the browser a single-use token that your server checks with the vendor. They load from different scripts, write to different form fields, verify at different endpoints, and keep tokens alive for different lengths of time. The bigger difference is what a visitor sees: hCaptcha can show an image challenge, and Turnstile never does. This guide compares the two from each vendor’s own docs, read in November 2026.
What each one is
hCaptcha is made by Intuition Machines. Its widget shows a checkbox, and when a visit looks risky it follows with an image challenge; hCaptcha says it picks what to show from the difficulty level the site sets. It also has an invisible mode with no checkbox, a “99.9% Passive” mode on the Pro plan that hCaptcha says aims to keep challenges to under 0.1% of real people, and fully passive modes with a risk score on Enterprise.
Turnstile is Cloudflare’s CAPTCHA alternative. Cloudflare says it runs small non-interactive JavaScript challenges in the browser (proof-of-work, proof-of-space, probing for web APIs, checks for browser quirks and human behaviour) and sets the difficulty per visitor. When it does need the visitor, it asks them to tick a box; there are no images or text to decipher. It can be embedded on any site without sending traffic through Cloudflare. It runs on the same Challenge Platform as Cloudflare’s challenge pages, but Turnstile is the widget a site embeds itself.
hCaptcha vs Turnstile at a glance
| hCaptcha | Cloudflare Turnstile | |
|---|---|---|
| Vendor | Intuition Machines (IMI) | Cloudflare |
| Widget script | js.hcaptcha.com/1/api.js | challenges.cloudflare.com/ |
| Container class | h-captcha | cf-turnstile |
| JavaScript global | hcaptcha, plus a grecaptcha compatibility hook unless recaptchacompat=off | turnstile |
| Token field | h-captcha-response | cf-turnstile-response (the name can be changed) |
| Token validity | 120s by default, single-use | 300s, single-use |
| Verify endpoint | api.hcaptcha.com/siteverify | challenges.cloudflare.com/ |
| Request body | Form-encoded only, no JSON | Form-encoded or JSON |
| Verify parameters | secret, response, remoteip (recommended), sitekey (recommended) | secret, response, remoteip (optional), idempotency_key (optional) |
| Expired or reused token | expired-input-response, already-seen-response | timeout-or-duplicate for both |
| Widget modes | Checkbox, invisible; 99.9% Passive on Pro; Passive on Enterprise | Managed, Non-Interactive, Invisible |
| What a visitor may see | A checkbox, then an image challenge if the visit looks risky | At most a checkbox; no images or text to decipher |
| Score in siteverify | Enterprise only: score + score_reason, a risk score | None; returns action, cdata, and ephemeral_id on Enterprise |
| Free plan | Basic, $0 | Free, unlimited challenges, up to 20 widgets |
| Paid plans | Pro $139/mo ($99/mo yearly); Enterprise by quote | Enterprise by quote |
Token mechanics
The flow is the same for both. The widget runs on the page, the visitor
passes, and the widget puts a token into a hidden field that rides along with
the form post. Your server then sends that token to the vendor’s
siteverify endpoint. Only the names change:
<div class="h-captcha" data-sitekey="f5ab1c2d-..."></div>
<!-- after a pass, hCaptcha adds to the form: -->
<textarea name="h-captcha-response">P1_eyJ0eXAi...UV8w</textarea> <div class="cf-turnstile" data-sitekey="1x00000000000000000000AA"></div>
<!-- after a pass, Turnstile adds to the form (test sitekey shown): -->
<input type="hidden" name="cf-turnstile-response" value="XXXX.DUMMY.TOKEN.XXXX" /> Lifetime: Cloudflare says
a Turnstile token is valid for 300 seconds after it is generated; hCaptcha’s
default is 120 seconds. Reuse: both are single-use, but
hCaptcha tells you which rule failed (expired-input-response or
already-seen-response) while Turnstile answers
timeout-or-duplicate either way. Field name:
Turnstile lets a site rename the field with response-field-name,
or turn it off and read the token with turnstile.getResponse(),
so a page may not have a cf-turnstile-response input at all.
Cloudflare also caps a Turnstile token at 2,048 characters.
Siteverify side by side
Both endpoints take a POST with secret and response
and answer in JSON. hCaptcha wants a form-encoded body and refuses JSON. It
recommends sending remoteip (on Enterprise that also turns on
risk scores) and sitekey, so a token solved on an easier sitekey
cannot be redeemed on yours.
curl https://api.hcaptcha.com/siteverify \
-d secret="$HCAPTCHA_SECRET" \
-d response="$TOKEN" \
-d remoteip="$USER_IP" \
-d sitekey="f5ab1c2d-7e8f-4a9b-b1c2-d3e4f5a6b7c8"
Turnstile accepts form-encoded or JSON. remoteip is optional, and
there is no sitekey parameter. It adds
idempotency_key: a UUID you generate so you can safely retry a
validation call.
curl https://challenges.cloudflare.com/turnstile/v0/siteverify \
-H "Content-Type: application/json" \
-d '{
"secret": "'"$TURNSTILE_SECRET"'",
"response": "'"$TOKEN"'",
"remoteip": "'"$USER_IP"'",
"idempotency_key": "'"$(uuidgen)"'"
}'
Both answers carry success, challenge_ts,
hostname and error-codes. hCaptcha Enterprise adds
score and score_reason. Turnstile adds the
action and cdata values the page set on the widget,
and on Enterprise a metadata.ephemeral_id:
{
"success": true,
"challenge_ts": "2022-02-28T15:14:30.096Z",
"hostname": "example.com",
"error-codes": [],
"action": "login",
"cdata": "sessionid-123456789",
"metadata": { "ephemeral_id": "x:9f78e0ed210960d7693b167e" }
}
Cloudflare tells you to check action and hostname
when you set them. hCaptcha warns that its hostname comes from
the visitor’s browser and should not be used for authentication. The full
hCaptcha request, response and error list is in
hCaptcha siteverify and
hCaptcha error codes.
Widget modes: what visitors see
- hCaptcha (Basic plan) shows a checkbox and may follow it
with an image challenge. Invisible mode drops the checkbox: you bind the
widget to a button or call
hcaptcha.execute(), and an image challenge can still appear. Both are on every plan. - hCaptcha Pro makes “99.9% Passive” the default for new sitekeys. Enterprise adds Passive difficulty, where no visible challenge is ever shown and the site consumes the risk score instead. hCaptcha notes that going fully passive trades away some protection compared with its active challenge modes.
- Turnstile Managed (Cloudflare’s recommended mode) decides per visitor whether to show a checkbox. Non-Interactive shows the widget with a spinner but never asks the visitor to do anything. Invisible shows nothing at all. All three are on the free plan.
Turnstile has no image challenge to fall back on, and hCaptcha’s own comparison makes that its main argument: it says Turnstile decides at one checkpoint, while hCaptcha Enterprise looks at the whole session and can raise the challenge difficulty, and that continuous signals on Cloudflare’s side need a separate Bot Management feature. Cloudflare’s docs make the opposite case: most visitors pass without doing anything.
Plans and pricing
As of November 2026, Cloudflare’s plans page lists two Turnstile plans. Free has unlimited challenges, every widget mode, up to 20 widgets per account, 10 hostnames per widget and 7 days of analytics. Enterprise is by quote and adds unlimited widgets, up to 200 hostnames per widget, widgets that work on any hostname, 30 days of analytics, Ephemeral IDs and the option to remove Cloudflare branding.
hCaptcha’s pricing page lists Basic at $0, Pro at $139 a month billed monthly or $99 a month billed yearly, with 100,000 evals included and $0.99 per 1,000 after that, and Enterprise by quote. Pro adds the 99.9% Passive mode, custom themes and analytics. The plan-by-plan detail is in hCaptcha pricing.
So for a site that mainly wants fewer visible challenges, Turnstile’s free plan already has modes where visitors usually see nothing, while hCaptcha’s 99.9% Passive mode starts on Pro. What hCaptcha’s paid plans add on top is the risk score, the difficulty controls and the Enterprise features around them.
Privacy and accessibility
Cloudflare says Turnstile processes only the data it needs for the security check and does not access, store or transmit form entries or other page inputs. If you use Invisible mode, you must link Cloudflare’s Turnstile Privacy Addendum from your own privacy policy. hCaptcha says it is “not in the business of selling individually targeted ads”, acts as a data processor under GDPR, and asks sites running invisible hCaptcha to show a short notice linking its privacy policy and terms. Enterprise customers can strip the visitor’s IP before it reaches hCaptcha by serving it from their own subdomain.
On accessibility, Cloudflare states WCAG 2.2 AA compliance for Turnstile. hCaptcha says it believes its service meets WCAG and Section 508, and offers text challenges in over 100 languages plus an email-verification route (covered in the hCaptcha accessibility cookie).
How to tell which one a page uses
Open the page where the widget actually appears (many sites load it only on the login or checkout step) and look for:
- Script source.
js.hcaptcha.com/1/api.jsis hCaptcha;challenges.cloudflare.com/is Turnstile. Cloudflare says Turnstile’s script must be loaded from that exact URL. hCaptcha Enterprise sites can serve hCaptcha from their own subdomain, so a missingturnstile/ v0/ api.js hcaptcha.comscript does not rule hCaptcha out. - Container and field.
h-captchaandh-captcha-responsemean hCaptcha;cf-turnstileandcf-turnstile-responsemean Turnstile. Turnstile’s explicit rendering uses a container without the class, and its field can be renamed, so check the script too. - JavaScript globals.
window.hcaptchaorwindow.turnstile. Agrecaptchaglobal proves nothing here: hCaptcha inserts one by default for reCAPTCHA-era code.
Paste this into the DevTools console to check all three at once:
const srcs = [...document.scripts].map((s) => s.src);
({
hcaptcha:
typeof window.hcaptcha !== "undefined" ||
srcs.some((u) => u.includes("hcaptcha.com/1/api.js")) ||
!!document.querySelector('.h-captcha, [name="h-captcha-response"]'),
turnstile:
typeof window.turnstile !== "undefined" ||
srcs.some((u) => u.includes("challenges.cloudflare.com/turnstile/")) ||
!!document.querySelector('.cf-turnstile, [name="cf-turnstile-response"]'),
});
A full-page check in front of a whole site is one of Cloudflare’s challenge
pages, a separate product on the same Challenge Platform, not an embedded
Turnstile widget. If
hcaptcha comes back true, the
sitekey guide shows how to read the key.
Switching between them
hCaptcha to Turnstile has an official path:
Cloudflare’s migration guide.
Create a Turnstile widget to get a sitekey and secret, then swap the script,
the render call, the form field and the siteverify URL. Cloudflare notes that
Turnstile supports render() and hCaptcha’s invisible mode with
execute(). For implicit rendering, the container class changes
from h-captcha to cf-turnstile.
<!-- client -->
- <script src="https://js.hcaptcha.com/1/api.js" async defer></script>
+ <script src="https://challenges.cloudflare.com/turnstile/v0/api.js" async defer></script>
- <div class="h-captcha" data-sitekey="..."></div>
+ <div class="cf-turnstile" data-sitekey="..."></div>
- hcaptcha.render(element, { sitekey: "..." })
+ turnstile.render(element, { sitekey: "..." })
<!-- server -->
- token = form["h-captcha-response"]
+ token = form["cf-turnstile-response"]
- POST https://api.hcaptcha.com/siteverify
+ POST https://challenges.cloudflare.com/turnstile/v0/siteverify - Drop the
sitekeyparameter from siteverify; Turnstile has none. Checkhostnameand, if you set one,actioninstead. - Score logic has nothing to read. Turnstile’s siteverify returns no score, so hCaptcha Enterprise threshold checks need a different signal.
- Error handling merges. Code that treated
expired-input-responseandalready-seen-responsedifferently now seestimeout-or-duplicatefor both. - Test with each vendor’s keys. Turnstile’s test sitekey
1x00000000000000000000AAalways passes and issues the dummy tokenXXXX.DUMMY.TOKEN.XXXX; its test secret1x0000000000000000000000000000000AAaccepts only that token. hCaptcha’s are in hCaptcha test sitekeys, and hCaptcha warns they give no bot protection. Keep both sets out of production.
Turnstile to hCaptcha is the same swap in reverse, plus three
things Turnstile did not need: send siteverify a form body instead of JSON,
pass sitekey, and verify within 120 seconds rather than 300.
Automating a page with hCaptcha or Turnstile
If you automate a page you are allowed to automate and it runs hCaptcha,
NoneCap is an hCaptcha solver service. You
POST the sitekey and page url, and get back a real
P1_ token to submit as the page’s h-captcha-response,
including on invisible and Enterprise sitekeys:
curl "https://api.nonecap.com/v1/solves?wait=90" \
-H "Authorization: Bearer $NONECAP_KEY" \
-H "Content-Type: application/json" \
-d '{
"type": "hcaptcha",
"sitekey": "f5ab1c2d-7e8f-4a9b-b1c2-d3e4f5a6b7c8",
"url": "https://target.example/login"
}' The API reference has the full solve object and samples in every language.
To be clear about scope: NoneCap solves hCaptcha only. Cloudflare Turnstile is not something NoneCap solves, so if the page above came back
turnstile: true, NoneCap will not help with it.
Last updated November 2026.
Frequently asked
Is Cloudflare Turnstile better than hCaptcha?
Are hCaptcha and Turnstile tokens interchangeable?
h-captcha-response token that only api.hcaptcha.com/siteverify accepts. Turnstile writes a cf-turnstile-response token that only challenges.cloudflare.com/turnstile/v0/siteverify accepts. Different vendors issue and check them, so a token from one never verifies with the other.How long is a Turnstile token valid compared with hCaptcha?
expired-input-response, already-seen-response); Turnstile uses timeout-or-duplicate for both.Is Turnstile free?
How do I switch from hCaptcha to Turnstile?
api.js, replace hcaptcha.render() with turnstile.render() and your Turnstile sitekey, read cf-turnstile-response on the server and post it to Turnstile’s siteverify URL. Turnstile supports the render() call and hCaptcha’s invisible mode with execute(). If your backend used hCaptcha Enterprise scores, that logic has nothing to read on Turnstile.How can I tell whether a page uses hCaptcha or Turnstile?
js.hcaptcha.com/1/api.js script, an h-captcha container, an h-captcha-response field or a global hcaptcha object means hCaptcha. A script from challenges.cloudflare.com/turnstile/, a cf-turnstile container, a cf-turnstile-response field or a global turnstile object means Turnstile.Does NoneCap solve Turnstile?
h-captcha-response token. Turnstile is not something NoneCap solves, so do not point a Turnstile workload at it.