Cloudflare Turnstile vs reCAPTCHA: why we migrated and what it cost us

We ripped reCAPTCHA out of five production sites and replaced it with Cloudflare Turnstile. Here's the actual work, the bot traffic before and after, and where Turnstile still bites.

Cloudflare Turnstile vs reCAPTCHA: why we migrated and what it cost us
KEY TAKEAWAYS
  • ↳Turnstile is free, no image puzzles, and doesn't ship the reCAPTCHA v3 tracking bundle to your users.
  • ↳The migration is roughly a two-hour job per site: swap script tag, swap widget, swap server-side verify endpoint.
  • ↳Turnstile's Managed mode blocked about the same volume of form spam as reCAPTCHA v3 in our tests, with fewer false positives on mobile Safari.
  • ↳You will lose reCAPTCHA's risk score. If you were branching logic on 0.3 vs 0.7, plan for that before you cut over.
  • ↳Turnstile does not solve API abuse or credential stuffing on its own. Pair it with Cloudflare WAF rate limiting.

Last February a client pinged me at 11pm because their contact form was getting hit with 400 spam submissions a day. They had reCAPTCHA v3 installed. It was doing something, apparently, but Zapier was still forwarding Viagra ads to their sales inbox.

We swapped it out for Cloudflare Turnstile the next morning. Spam dropped to under 10 a day within a week. That was the first of five sites we migrated in 2024, and I want to write down what actually happened, because most of the “Turnstile vs reCAPTCHA” posts online read like they were written by someone who has never shipped either.

why we left reCAPTCHA

Three reasons, in the order they mattered to me.

One, the script. reCAPTCHA v3 loads roughly 480KB of JavaScript from google.com and gstatic.com on every page you put it on. Not just the form page. Google’s own docs recommend loading it site-wide so the risk score has enough signal. That is a lot of third-party JS running on your marketing pages, and it shows up in every Lighthouse audit as a top offender.

Two, the tracking. reCAPTCHA is a fingerprinting product with a form-protection feature bolted on. If your privacy policy claims you don’t send user data to Google, and you have reCAPTCHA v3 on every page, your privacy policy is wrong. The French CNIL and several German DPAs have specifically flagged this. Post-Schrems II, some of our EU clients just said no.

Three, the score is a black box. reCAPTCHA v3 returns a number between 0 and 1. Google will not tell you what goes into it. When a legit customer complained they couldn’t submit a form, I had exactly zero tools to debug it. “The score was 0.2, sorry” is not a support answer.

Turnstile is not perfect, but it is free, it doesn’t require users to click fire hydrants, and Cloudflare publishes what it actually does. That was enough for me.

the migration, concretely

We migrated five sites: two Astro marketing sites, a Next.js SaaS dashboard, a Cloudflare Workers API, and one legacy PHP site I would rather not talk about. Average time per site was about two hours including QA. Here is the shape of it.

Client side, the swap is one script tag and one div. Old:

<script src="https://www.google.com/recaptcha/api.js?render=SITE_KEY"></script>
<script>
  grecaptcha.ready(() => {
    grecaptcha.execute('SITE_KEY', { action: 'contact' })
      .then(token => document.getElementById('token').value = token);
  });
</script>

New:

<script src="https://challenges.cloudflare.com/turnstile/v0/api.js" async defer></script>
<div class="cf-turnstile" data-sitekey="YOUR_SITE_KEY" data-callback="onToken"></div>

Server side, you POST the token to Cloudflare instead of Google. Here is what we ship in a Cloudflare Worker:

async function verifyTurnstile(token: string, ip: string, secret: string) {
  const body = new FormData();
  body.append('secret', secret);
  body.append('response', token);
  body.append('remoteip', ip);

  const res = await fetch(
    'https://challenges.cloudflare.com/turnstile/v0/siteverify',
    { method: 'POST', body }
  );
  const data = await res.json() as { success: boolean; 'error-codes'?: string[] };
  return data.success;
}

That is the entire integration. No score threshold to tune, no action names to match, no enterprise tier upsell.

what the numbers looked like

On the client site I mentioned, over a 30-day window before and after:

Same form, same traffic sources, same Resend inbox. I did not touch anything else on the site during that window.

The 8 that got through were mostly hand-typed by real humans in click farms. No CAPTCHA stops those. If you want to stop those you need honeypots, submission rate limits, and content filtering. Turnstile is not going to save you from a $2/hour worker in Bangladesh who is genuinely filling out your form.

where Turnstile hurts

Mobile Safari with Lockdown Mode on will occasionally get stuck on the invisible challenge. We saw this maybe 1 in 300 sessions. The fix is to switch the widget from Managed to Non-Interactive, or to fall back to a visible checkbox after a 10-second timeout. Cloudflare has an expired-callback you can wire up.

If you use hCaptcha-style Enterprise features, Turnstile does not have them. There is no risk score, no per-request action labels, no analytics beyond the Cloudflare dashboard. If your fraud team was building models on top of reCAPTCHA Enterprise scores, Turnstile is a downgrade. For a contact form or a signup page, none of that matters.

Turnstile also does not do anything about API abuse. If someone finds your /api/contact endpoint and hits it directly without a token, Turnstile is not going to help. You need to actually verify the token server-side on every request, and rate-limit the endpoint at the edge. We use Cloudflare’s built-in rate limiting rules for that, one rule per endpoint, usually 10 requests per minute per IP.

the honest cost

Across five sites, migration took me about 11 hours total including testing on staging, updating privacy policies, and writing internal docs. Zero dollars in licensing because Turnstile is free up to 1 million verifications a month, which none of our clients come close to.

We deleted about 480KB of Google JS from marketing pages. Lighthouse Performance scores went up 4 to 12 points depending on the site. The Astro site that was already scoring 98 went to 100 on mobile.

One client’s legal team asked for a DPA. Cloudflare has one, it is on their trust portal, done in a day.

should you switch

If you are using reCAPTCHA v3 on a marketing site or a contact form, yes, tomorrow. There is no reason to keep shipping Google’s tracker to your users for a job Turnstile does equally well.

If you are on reCAPTCHA Enterprise and you actually use the risk scores in production fraud logic, it is more complicated. Turnstile does not replace that. You would be replacing a scalpel with a doorstop.

If you are already on Cloudflare for DNS or your CDN, the migration is genuinely a morning of work. If you are not, this is a decent reason to move your DNS over, but that is a bigger conversation.

We do this kind of unglamorous cleanup a lot when we finish half-built products. Ripping out heavy third-party scripts, tightening the WAF, replacing whatever was duct-taped in during the last sprint. If you have a form problem or a bot problem or a “why is our site 4MB” problem, get in touch.

FREQUENTLY ASKED

Common questions

▸Is Cloudflare Turnstile actually free?

Yes, up to 1 million siteverify calls per month, with no credit card required. You do not need to be a Cloudflare customer for anything else. Sign up, get a site key and secret, and you are done. Above 1M/month you contact sales, but I have never seen a client hit that on form protection alone.

▸Does Turnstile work without Cloudflare hosting my site?

Yes. Turnstile is a standalone product. Your site can be on Vercel, Netlify, a Hetzner box, whatever. You just call challenges.cloudflare.com/turnstile/v0/siteverify from your backend to verify the token. The only thing you need a Cloudflare account for is generating the site key and secret.

▸Will Turnstile stop all my form spam?

No. It stops automated bots very well. It does not stop humans in click farms who hand-fill forms for pennies. For those you need honeypot fields, rate limiting, and content filtering on the submission itself. In our data Turnstile cut spam by about 98% on one site, but the last 2% was hand-typed and no CAPTCHA will catch that.

▸What do I do about the missing reCAPTCHA score?

If you were branching logic on the score (allow above 0.7, review 0.3 to 0.7, block below 0.3), you need to redesign that flow before migrating. Turnstile is binary: token valid or not. For anything more sophisticated you either move that logic server-side using your own signals, or you stay on reCAPTCHA Enterprise.

▸How do I test Turnstile in development?

Cloudflare publishes dummy site keys that always pass, always fail, or always show the interactive challenge. Use 1x00000000000000000000AA for always-passes in local dev. The corresponding secret keys are in their docs. Do not use your production site key on localhost, it will not resolve correctly against your domain allowlist.

SOURCES
  1. [1]
    Cloudflare Turnstile documentationdevelopers.cloudflare.com
  2. [2]
    Turnstile server-side validationdevelopers.cloudflare.com
  3. [3]
  4. [4]

Related posts