To do this, load the v3 site key as documented, and then explicitly render v2 using grecaptcha.render.

You are allowed to hide the badge as long as you include the reCAPTCHA branding visibly in the user flow. Please include the following text:

Yes, please use “www.recaptcha.net” in your code in circumstances when “www.google.com” is not accessible.

• First, replace <script src=”https://www.google.com/recaptcha/api.js” async defer></script> with <script src=”https://www.recaptcha.net/recaptcha/api.js” async defer></script>
• After that, apply the same to everywhere else that uses “www.google.com/recaptcha/” on your site.

After that, apply the same to everywhere else that uses “www.google.com/recaptcha/” on your site.

reCAPTCHA v2 is not going away! We will continue to fully support and improve security and usability for v2.

reCAPTCHA v3 is intended for power users, site owners that want more data about their traffic, and for use cases in which it is not appropriate to show a challenge to the user.

For example, a registration page might still use reCAPTCHA v2 for a higher-friction challenge, whereas more common actions like sign-in, searches, comments, or voting might use reCAPTCHA v3. To see more details, see the reCAPTCHA v3 developer guide.

For reCAPTCHA v3, create a separate key for testing environments. Scores may not be accurate as reCAPTCHA v3 relies on seeing real traffic.

For reCAPTCHA v2, use the following test keys. You will always get No CAPTCHA and all verification requests will pass.