use case · captcha alternatives

CAPTCHA alternatives that don't tax real users.

Updated November 7, 2026

The best CAPTCHA alternative depends on the abuse. For automated sessions, use Cloudflare Turnstile or a proof-of-work challenge such as Friendly Captcha or ALTCHA. For spammy text in forms, comments, and applications, use server-side content scoring such as SiftFy. Most sites should start with a rate limit plus an accessible honeypot, then add only the check that matches the abuse they actually see.

Every "click all the traffic lights" task is a tax on legitimate visitors and a speed bump for modern bots. The fix is not a fancier puzzle. It is choosing the right layer: a session check for bots, a text check for spam, and neither one in front of every reader by default. For the editorial ranking by reader friction, see CAPTCHA alternatives for blogs compared.

six options

What each alternative actually verifies.

These tools are often listed as if they were interchangeable. They are not: some verify a browser session, some verify work, and one reads the message.

CAPTCHA alternatives compared by what they verify, user friction, cost, best fit, and what they cannot do
OptionVerifiesReader frictionCostBest fitWhat it does not do
Cloudflare TurnstileWhether a browser session looks automatedUsually invisible; may challengeFreeSites already on Cloudflare that need a bot checkReturns a token, not a spam score for the message
hCaptchaHuman interaction through a challengeVisible puzzle or passive checkFree tier; paid plansSites that want a drop-in reCAPTCHA replacementStill a session check; accessibility and conversion cost
Friendly CaptchaProof of work in the browserInvisible for most visitorsFree tier; paid plansEU privacy and GDPR-sensitive formsProof of work is not content classification
ALTCHAOpen-source proof of workInvisible or a small widgetFree / self-hostedTeams that want to self-host the challengeDoes not read the submitted text
Honeypot fieldWhether a bot fills a hidden inputNone when implemented accessiblyFreeA first, cheap layer on any formHeadless browsers and human spam pass
SiftFy content scoringWhether submitted text looks like spamNone; runs server-side10,000 free requests/month, then $9/moContact forms, comments, applications, signups with free textNot a bot challenge, email validator, or IP reputation service

Pricing shapes checked 7 November 2026. Verify current plans with each vendor before you buy.

the layer problem

CAPTCHA answers a question that stopped mattering.

On-page CAPTCHAs solve "is this a real browser session" — a question that stopped being useful around the time bots started running real headless browsers. They do not solve "is this content spammy," which is the question that actually matters for a contact form, comment section, or application. A bot driving Chromium can pass reCAPTCHA v3 reliably; a real customer on a flaky phone connection often cannot.

The cost shows up in conversion data. Form-completion rates typically drop when a visible challenge is on the page, and the drop is concentrated among users on slow connections, older browsers, and accessibility tools — exactly the visitors who should not be paying the tax. Meanwhile the spam keeps coming, because spam is a content-classification problem and a challenge is a session problem.

the replacement

Move the check off the screen.

The form goes from this:

html
<!-- before: reCAPTCHA on every form, every visitor pays the friction tax -->
<form action="/api/contact" method="POST">
  <input type="email" name="email" required>
  <textarea name="message" required></textarea>
  <div class="g-recaptcha" data-sitekey="6Lc..."></div>
  <button type="submit">Send</button>
</form>
<script src="https://www.google.com/recaptcha/api.js" async defer></script>

To this:

html
<!-- after: clean form, classification on the server -->
<form action="/api/contact" method="POST">
  <input type="email" name="email" required>
  <textarea name="message" required></textarea>
  <button type="submit">Send</button>
</form>

The work moves to the server-side handler that was already processing the form. About fifteen added lines:

typescriptServer-side scoring with a fail-open timeout
// /api/contact handler — the work reCAPTCHA was doing, moved server-side.
export async function POST(req: Request) {
  const { email, message } = await req.json();

  let probability = 0;
  let ceiling = null;
  try {
    const resp = await fetch("https://api.siftfy.io/v1/predict", {
      method: "POST",
      headers: {
        "Content-Type": "application/json",
        "X-API-Key": process.env.SIFTFY_KEY!,
      },
      body: JSON.stringify({ text: message }),
      signal: AbortSignal.timeout(2000),
    });
    if (resp.ok) {
      ({ spam_probability: probability, max_confidence: ceiling = null } = await resp.json());
    }
  } catch {
    // Fail open on transport failure: losing one borderline lead beats
    // breaking the form for everyone during an outage.
  }

  if (ceiling !== null && probability > ceiling) {
    // Always 200 to the form so spammers cannot tune against the threshold.
    return Response.json({ ok: true });
  }

  await sendEmail({ to: process.env.INBOX!, from: email, body: message });
  return Response.json({ ok: true });
}

The reader sees the form they expected. The score never touches the browser, so spammers cannot probe for it. The third-party Google script that was tracking every visitor is gone, privacy improves, and your CSP gets simpler.

decision rule

Pick by the abuse, not by the label.

Bots flood the endpoint

Rate-limit at the edge; add Turnstile or proof of work only when the flood starts.

Real-looking browsers submit junk text

Score the message server-side. A challenge will not read it, and a bot will pass the challenge.

Both happen at once

Layer them: rate limit, then content score, then a challenge as the abuse-only fallback.

Accessibility or privacy is the constraint

Use an accessible honeypot plus content scoring. Avoid visual puzzles on the default path.

one call, two checks

Content Gate: a bot score and a content verdict.

Siftfy's Content Gate (private beta) puts an invisible check on the form and judges the text in the same server-side call. Its siteverify response carries a 0–100 bot score with coarse reasons, and on an enforce site it blocks sessions at a threshold you set per form, 90 by default. There is still no puzzle and no cookie. It is bot-resistant, not bot-proof: a carefully driven real browser can still score low, so the content check stays the backstop.

Try the live demo to see the exact response a backend gets, or read Content Gate vs Cloudflare Turnstile for how it differs from a pass/fail challenge.

edge cases

What to handle before you ship.

  • Volumetric abuse. Pair Siftfy with a basic rate-limiter per IP or session. Classification is per message; it does not help when a script is brute-forcing the endpoint.
  • Honeypot first. A hidden field that real users do not fill is a free extra signal. Reject a non-empty honeypot before calling Siftfy and save a request.
  • Multilingual forms. The model is primarily English-trained. The confidence ceiling is per language and can be lower than English, so read it from each response rather than raising a constant.
  • Never reveal the score. Always return 200 on a hard block. A 4xx tells the spammer to rephrase; a 200 tells them their content shipped.

CAPTCHA alternative questions

What is the best CAPTCHA alternative?

It depends on the abuse. For automated sessions, Cloudflare Turnstile or a proof-of-work challenge such as Friendly Captcha removes most of the puzzle friction. For spammy text in forms, comments, and applications, server-side content scoring such as SiftFy reads the message instead of the browser. Most sites benefit from a cheap first layer (honeypot plus rate limit) and one check that matches the actual abuse.

Is Cloudflare Turnstile better than reCAPTCHA?

Turnstile is usually less intrusive, free, and does not require a Google script on the page. It still answers the same question reCAPTCHA answers: whether a session looks automated. It does not tell you whether a submitted message is spam. If your problem is junk text from real-looking browsers, pair Turnstile with content scoring or skip the challenge and score the text.

Can I replace reCAPTCHA without hurting conversion?

Yes. Remove the challenge from the default path, add rate limits and an accessible honeypot, and score the submitted text on the server. Keep an invisible challenge available as an abuse-only fallback. The reader sees the form they expected; the spam decision happens where the user cannot see or tune against it.

Do CAPTCHA alternatives work on static sites?

Yes, if the form posts to a small serverless function or edge worker. The function holds the API key, calls the classifier, and forwards only the submissions that pass. Never call a spam API directly from browser JavaScript with a secret key, and do not rely on client-side validation as a security boundary.

What is the cheapest CAPTCHA alternative?

A honeypot field and a rate limit are free and catch basic automation. Siftfy's free tier adds server-side content scoring for 10,000 requests a month with no card, which covers most small sites. Turnstile, Friendly Captcha, and ALTCHA also have free options, but each still adds a browser-side script or proof-of-work step.

Are CAPTCHA alternatives accessible?

Content scoring and honeypots add no visual task, so they avoid the worst accessibility failures of image puzzles. Proof-of-work challenges are also usually invisible. If you keep a challenge, choose one with an audio or non-visual path, test it with a keyboard and screen reader, and make it appear only when risk signals justify it.

start free

Score a real submission in five minutes.

10,000 requests a month free, no card. One endpoint, a calibrated probability, and no puzzle for your readers.