Questions regarding new reCAPTCHA 2025 changes

Hello guys! 

Got a few questions regarding the new reCAPTCHA changes done by Google.

I did receive the email "Weโ€™re writing to inform you that all Google reCAPTCHA keys will need to be migrated to a Google Cloud project by the end of 2025..." as most of you probably already did.

So far based on my research I am aware of the following, but you can confirm my questions please: 

1. The existing V2 Checkbox, V2 Invisible and V3 keys will continue to work even after this change, however, Google is not specifying is they will automatically migrate the keys themselves, or what happens if the user does not migrate all the keys.  Will they still be available/working on the sites used? 

From my understanding, they are suggesting to migrate otherwise, the sites may loose protection if the reCAPTCHA service surpasses more than 10.000 requests (which is the Free tier limit).

2. I noticed that when using the new Cloud view, the user can now create reCAPTCHA keys which are defaulted in V3, and they can also create V2 Checkbox (I am not a robot keys) as seen below.

My question here is now - how can we create new V2 Invisible keys moving forward? Will that be handled through google Console as well moving forward, or, there's a different approach that need to be considered? 

lucian123_0-1739956262455.png

3. Last but not least, and related to the above (V2 invisible key generation) - will the old/legacy console view will still be available? That's the only way the user can still create V2 Invisible keys as far as I noticed. https://www.google.com/recaptcha/admin/create 

I wonder if this will still be available in the future, or if it will be completely replateed by the new Google Cloud Platform.


Any help would be greatly appreciated!! 

Solved Solved
1 5 1,891
1 ACCEPTED SOLUTION

Hi @lucian123

Welcome to Google Cloud Community! 

1. Existing V2 Keys (Checkbox, Invisible, V3) after Migration:

  • Will the keys continue to work? Yes, if you migrate them to a Google Cloud project before the end of 2025.

  • Will Google automatically migrate them? No, Google will not automatically migrate the keys themselves. You must perform the migration.

  • What happens if I don't migrate? Your reCAPTCHA service may stop functioning correctly, especially if your usage exceeds the free tier limits. It's highly recommended to migrate to avoid interruption.

In short: Migrate or risk service disruption (especially if you exceed 10,000 requests). See the documentation about Quota and limits of reCAPTCHA.

2. Creating New V2 Invisible Keys in the New Cloud View:

  • How to create V2 Invisible keys now? Currently, you cannot directly create V2 Invisible keys in the new Cloud console. This functionality is not present. It is possible that Google will add this functionality in the future. For feature requests we encourage you to create a public issue tracker

  • Alternative to V2 Invisible? You can choose a V3 key type now, but there's no way to generate a V2 Invisible key for new implementations on the Google Cloud Console.

In short: Google is encouraging adoption of reCAPTCHA v3.

3. Availability of the Old/Legacy Console View:

  • Will the old console be available? Probably not indefinitely. It's almost certain that the old console will eventually be deprecated and completely replaced by the Google Cloud Platform.

  • What if I need V2 Invisible and the old console is gone?

    • Monitor Google's announcements. If a new way to create V2 Invisible keys isn't added to the Cloud console, you may need to re-evaluate your reCAPTCHA strategy or consider other solutions. 

    • Migrating to reCAPTCHA v3 is recommended.

Note: For updated features and deprecated functionality check here reCAPTCHA release notes.

Additionally, see the Frequently Asked Questions about reCAPTCHA this may help you for other questions like migration process, errors you might encounter and more.

If you encounter issues during the migration process and need further assistance, please reach out to our Google Cloud Support team.

Was this helpful? If so, please accept this answer as โ€œSolutionโ€. If you need additional assistance, reply here within 2 business days and Iโ€™ll be happy to help.

View solution in original post

5 REPLIES 5

Hi @lucian123

Welcome to Google Cloud Community! 

1. Existing V2 Keys (Checkbox, Invisible, V3) after Migration:

  • Will the keys continue to work? Yes, if you migrate them to a Google Cloud project before the end of 2025.

  • Will Google automatically migrate them? No, Google will not automatically migrate the keys themselves. You must perform the migration.

  • What happens if I don't migrate? Your reCAPTCHA service may stop functioning correctly, especially if your usage exceeds the free tier limits. It's highly recommended to migrate to avoid interruption.

In short: Migrate or risk service disruption (especially if you exceed 10,000 requests). See the documentation about Quota and limits of reCAPTCHA.

2. Creating New V2 Invisible Keys in the New Cloud View:

  • How to create V2 Invisible keys now? Currently, you cannot directly create V2 Invisible keys in the new Cloud console. This functionality is not present. It is possible that Google will add this functionality in the future. For feature requests we encourage you to create a public issue tracker

  • Alternative to V2 Invisible? You can choose a V3 key type now, but there's no way to generate a V2 Invisible key for new implementations on the Google Cloud Console.

In short: Google is encouraging adoption of reCAPTCHA v3.

3. Availability of the Old/Legacy Console View:

  • Will the old console be available? Probably not indefinitely. It's almost certain that the old console will eventually be deprecated and completely replaced by the Google Cloud Platform.

  • What if I need V2 Invisible and the old console is gone?

    • Monitor Google's announcements. If a new way to create V2 Invisible keys isn't added to the Cloud console, you may need to re-evaluate your reCAPTCHA strategy or consider other solutions. 

    • Migrating to reCAPTCHA v3 is recommended.

Note: For updated features and deprecated functionality check here reCAPTCHA release notes.

Additionally, see the Frequently Asked Questions about reCAPTCHA this may help you for other questions like migration process, errors you might encounter and more.

If you encounter issues during the migration process and need further assistance, please reach out to our Google Cloud Support team.

Was this helpful? If so, please accept this answer as โ€œSolutionโ€. If you need additional assistance, reply here within 2 business days and Iโ€™ll be happy to help.

Really appreciate all the answers provided, really helpful! Thank you

DSI
Bronze 1
Bronze 1

Please, I would like to confirm information that was not entirely clear to me.

With the migration to the new platform, will the old quotas currently announced in versions V2 and V3 (1000 calls per second or 1000000 calls per month) cease to exist?

My website has more than 10000 monthly checks with version v2, so will I be required to activate billing?

Is activating billing the same as using the Enterprise version?

Thank you in advance.

DSI
Bronze 1
Bronze 1

Please, I would like to confirm information that was not entirely clear to me.With the migration to the new platform, will the old quotas currently announced in versions V2 and V3 (1000 calls per second or 1000000 calls per month) cease to exist?

My website has more than 10000 monthly checks with version v2, so will I be required to activate billing?

Is activating billing the same as using the Enterprise version?

Thank you in advance.

Hi @DSI

For the best assistance with your concern, It is recommended to create a new question.

Thank you.