What's changing?
Starting November 13, 2024, users will need to use a Cloud project to access the Earth Engine platform. If you use Earth Engine noncommercially, you can continue using the platform for free—you'll just need to set up a Cloud project to do so.
We will be making the following changes over the course of the year:
- End of June 2024: All new Earth Engine users must access Earth Engine using Cloud projects
- Starting September 16, 2024, we will be limiting quotas for users not using Cloud projects, and most new Earth Engine features will only be available when accessing Earth Engine with a Cloud project
- Starting November 13, 2024, accessing Earth Engine will require a correctly configured Cloud project
In order to access your Earth Engine data (assets, Apps) or run computations after November 13, 2024, you'll need to use a Cloud project. If you don't configure a Cloud project, your data will continue to be stored in Earth Engine in accordance with our terms, but you'll need to use a Cloud project to access them.
What is individual access without a Cloud project?
All Earth Engine users prior to 2022 signed up for "individual" Earth Engine access (without a Cloud project) using the Earth Engine signup page. After Earth Engine became a Google Cloud API in 2022, users no longer needed to sign up for individual access and could configure access with a Cloud project. Some users continue to use Earth Engine through individual access and we are requiring all users to transition to access with a Cloud project. If you continue to rely on individual access, you will lose access to Earth Engine in late 2024.
What do I need to do?
Using the account that's signed up for legacy individual access, visit the legacy signup access page to see whether your account and any service accounts are signed up for individual access without a Cloud project.
If your account is configured for individual access without a Cloud project, you'll need to ensure that all of your requests (as well as all requests from any service accounts listed on that page) are configured to specify a Cloud project. See how to transition your access.
If you're unable to use Cloud projects at your institution, you can request a temporary exception to keep using your non-Cloud access. See the section covering how to request this exception. If your account uses a Cloud project, then all of the Earth Engine use associated with that account is already going through Google Cloud, and you're not affected by this change. No further action is required.
Transition to use Cloud projects
Step 1: Get a project
Follow the Earth Engine Cloud project setup guide to walk through the process of creating a new project or configuring one that you already have access to.
If you already have access to a Cloud project (one that a colleague or IT administrator has shared, for example), you only need to ensure that you have the correct roles and permissions.
If you don't already have access to a project, you can create one using the project registration page page. You'll also have to accept the Google Cloud terms of service. When creating a Cloud project, make sure to use the same email as your individual access to ensure your assets and scripts transfer to the cloud project.
In order to access your legacy assets, you'll need to use an account which has permission (usually the same account that created them).
Step 2: Ensure that the Earth Engine API is enabled
Visit the Earth Engine API page in the Cloud console and, after making sure you have the right project selected in the top drop-down, click "Enable"
Step 3: Configure a billing account
For projects using Earth Engine noncommercially, you don't need to configure a billing account or a form of payment. If you add one, you won't incur any Earth Engine charges if you register your project (Step 4) as noncommercial, but you may incur charges from other Cloud products and services.
For projects using Earth Engine commercially, you will need to configure a billing account that's backed by a form of payment (usually a credit card). This billing account will be charged for Earth Engine use as well as for the use of any other Cloud products and services.
Step 4: Register the project
Before you can use a project to call Earth Engine, you'll also need to register each project with on the registration page. During registration, you can select a paid or unpaid project configuration depending on your use case. See the Earth Engine noncommercial page for more details about what kinds of projects qualify for free quota.
Step 5: Select a subscription
Commercial users will need to select a subscription during registration if there's not one already present on the billing account. Note that you may not have permission to see your project's billing configuration (for example, if you're using someone else's project).
If your billing account doesn't have a subscription for Earth Engine, it will be charged for use based on the Limited plan.
Step 6: Use that project when calling Earth Engine
The Earth Engine Cloud projects documentation covers how to use projects across all Earth Engine surfaces. Ensure that you have the right project selected.
What happens if I do nothing?
If you don't configure a Cloud project, your Earth Engine data (assets and EE Apps) will continue to be stored in Earth Engine in accordance with the Terms of Service, but you'll need to use a Cloud project to send any requests to Earth Engine. Because scripts are tied to users, they will continue to be accessible and editable from the underlying Git repository at earthengine.googlesource.com.
If you'd like to delete your Earth Engine data without configuring a Cloud project, send us a data deletion request and we'll get back to you within 10 business days.
How to request an exception
If you're unable to configure a Cloud project to use with Earth Engine, we may grant you more time to continue using your individual access without a Cloud project. This exception process requires manual review, so it may take several weeks and exceptions are not guaranteed. To request a temporary exception, see the access guide and submit an application.
Getting help
For questions, concerns, or comments, reach out to Earth Engine registration support.
FAQ
Q: Will I be required to submit a credit card when I migrate to a Cloud
project?
A: No, no form of payment is required to set up a Cloud project with Earth
Engine.
Q: What happens to my scripts and assets if I don't migrate to a Cloud
project?
A: Your scripts and assets will persist as described in the Terms of
Service, but you'll need to use a registered Cloud project in
order to access the EE platform. Your scripts will continue to be accessible
from the underlying Git repository at
earthengine.googlesource.com.