[flagged]
Using Cloudflare Workers and reCAPTCHA v3 for a Static Site Contact Form
11–13 of 13 posts
Re: Using Cloudflare Workers and reCAPTCHA v3 for a Static Site Contact Form
#12Workers are great for this sort of thing and these days with Turnstile and Email Sending beta[1] you can have Cloudflare handle it all 1 - https://developers.cloudflare.com/email-service/
[dead]
Re: Using Cloudflare Workers and reCAPTCHA v3 for a Static Site Contact Form
#13Worth saying for the personal-site case specifically, which is most of the static sites people bolt a contact form onto: the form is often not worth the infrastructure at all.
I maintain an open-source portfolio template (https://github.com/p32929/portfolio-v2) and the contact section is deliberately just links - email, GitHub, LinkedIn. No endpoint, no captcha, no keys to rotate, and nothing to migrate when a free tier moves under you, which is exactly what happened to reCAPTCHA v3 per the top comment.
The honest counter-argument is that a form converts better than a mailto link. For a business that is true and measurable. For a CV or portfolio site it mostly is not: the messages you actually want arrive by email or DM anyway, and the form collects SEO spam, which is why you then need a captcha, which is this entire thread.
If you do need the form, the Turnstile suggestion upthread is the right shape - one vendor, one failure mode, instead of three services stitched together.