Turnstile, reCAPTCHA or a honeypot: stopping form spam
Compare the honeypot, rate limits, Cloudflare Turnstile and Google reCAPTCHA, and learn which layers most forms really need.
2 min read
On this page
Any form on the public web gets spam sooner or later. Bots fill in every field they find, scripts post straight to your endpoint, and some people paste the same advert into every contact form they see. There is no single fix, but a few layers together stop nearly all of it without making real visitors solve puzzles. Here is how the options compare and where to start.
Layer 1: the honeypot
A honeypot is a field people never see and bots happily fill in. When it arrives with a value, the submission is almost certainly automated. It costs real visitors nothing and catches a surprising share of simple bots.
Formpik's snippet includes one called _gotcha. A submission that fills it is stored as spam, with the reason recorded, and runs no flows, so nobody gets an email about it. Hide it properly, with aria-hidden on its wrapper and tabindex="-1", so screen reader users are never asked to fill it in.
Layer 2: limits
Limits slow down anything that sends many submissions quickly. Formpik takes at most 120 posts a minute from one address, and each form has its own hourly limit per visitor that you set in its settings. Repeats of the same submission within 10 seconds are dropped, which also protects you from double clicks.
Layer 3: field rules
Many spam messages share patterns that field rules catch on the server:
- Most links in a message, since adverts are full of them.
- Blocked words, for the phrases you keep seeing.
- No throwaway emails, which refuses disposable mailboxes.
- Work emails only, for business forms where a free mailbox is a bad sign.
Layer 4: a bot check widget
When spam still gets through, add a challenge widget. Both main options usually run invisibly and only show a puzzle when something looks wrong.
- Cloudflare Turnstile is free, does not need a Google account, and is designed to avoid visual puzzles for most visitors. It adds a token named
cf-turnstile-responseto the form. - Google reCAPTCHA is the long-standing option many people recognise. It adds
g-recaptcha-response. Check how it fits your privacy policy, since it sends visitor signals to Google.
In Formpik, choose the one you use under Bot check in the form's settings and add its widget to your page. Formpik verifies the token with every submission, and a missing or failed check stores the submission as spam instead of running your flows.
Which layers do you need?
- Every form: the honeypot and the limits. They are on from the start.
- Forms that attract adverts: add link and word rules.
- Sign-up and high-value forms that are still targeted: add Turnstile or reCAPTCHA.
Check what was caught
Spam is never thrown away silently. Filter the Submissions inbox by spam to see what was caught and why. If a real person was caught by mistake, release the submission and its flows run as if it had arrived normally.
Related guides
- Security, spam protection and limits.
- Form settings, including the hourly limit and the bot check.
- How to stop form spam without punishing real people.
- Form validation that agrees in the browser and on the server.
- An accessible web form checklist.
References
- Turnstile documentation, Cloudflare.
- reCAPTCHA, Google for Developers.
- Input Validation Cheat Sheet, OWASP.

