Stay organized with collections Save and categorize content based on your preferences.
This topic lists all Google Maps Platform products and features that are currently, or scheduled to be, in the Legacy stage.
How Legacy status works
Legacy is an intermediate lifecycle step to ease the transition between Generally Available services and Deprecated services.
Legacy-marked services will be officially feature frozen, and new feature requests will only be considered for updated non-Legacy services.
Legacy-marked services will retain full support.
Existing projects already using Legacy services can continue to do so.
While we envision that Legacy services will be turned down in the coming years, there is no date yet for when this will happen.
Subject to the Google Maps Platform Terms of Service Deprecation Policy, we will provide at least a 12-month notice prior to the decommission of the services.
Active services with Legacy status
This section lists all products and features which are either Legacy or scheduled to be in Legacy.
Google throws this error when your application is querying a legacy API (Places API, Directions API, or Distance Matrix API) that is not enabled on your project. In most cases, keep legacy APIs disabled on new projects.
If you own the application that's throwing this error, use the equivalent new API instead.
If you don't own the application that's throwing this error, report this issue to your application provider by sharing this URL with them, and follow their instructions to upgrade to a new version. As a short-term solution, consider activating the legacy API(s):
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-18 UTC."],[[["\u003cp\u003eThis page lists Google Maps Platform products and features transitioning to Legacy status, an intermediate step before deprecation.\u003c/p\u003e\n"],["\u003cp\u003eLegacy services are not available in new Cloud projects but remain fully supported for existing projects.\u003c/p\u003e\n"],["\u003cp\u003eWhile Legacy services will eventually be turned down, there's no set date, and a 12-month notice will be provided before decommissioning.\u003c/p\u003e\n"],["\u003cp\u003eSeveral services in Routes and Places product areas are scheduled to become Legacy on March 1, 2025, with migration guides and new service options available.\u003c/p\u003e\n"]]],["Legacy Google Maps Platform services, set to legacy status on March 1, 2025, will not be available for new Cloud projects but remain supported for existing users. Services in this phase are feature-frozen, and they are moving towards eventual decommission with a 12-month notice. Routes and Places APIs, including their JavaScript and SDK counterparts, are affected. New services will replace these, with migration guides and links to issue trackers provided for each one.\n"],null,["This topic lists all Google Maps Platform products and features that are\ncurrently, or scheduled to be, in the\n[Legacy](/maps/launch-stages#legacy) stage.\n\nHow Legacy status works\n\nLegacy is an intermediate lifecycle step to ease the transition between\nGenerally Available services and Deprecated services.\n\n- Legacy-marked services will be officially feature frozen, and new feature requests will only be considered for updated non-Legacy services.\n- Legacy-marked services will retain full support.\n- Existing projects already using Legacy services can continue to do so.\n\n While we envision that Legacy services will be turned down in the coming\n years, there is no date yet for when this will happen.\n\nSubject to the [Google Maps Platform Terms of\nService](https://cloud.google.com/maps-platform/terms) Deprecation\nPolicy, we will provide at least a 12-month notice prior to the decommission of\nthe services.\n\nActive services with Legacy status\n\nThis section lists all products and features which are either Legacy or\nscheduled to be in Legacy.\n\n| Product Area | Legacy Service Name | Legacy Date | New Service Name | Migration guide |\n|--------------|-------------------------------------------------------------------------------------|---------------|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------|\n| Routes | [Distance Matrix API](/maps/documentation/distance-matrix/overview) | March 1, 2025 | [Routes API](/maps/documentation/routes) | [Guide](/maps/documentation/routes/migrate-routes) |\n| Routes | [Directions API](/maps/documentation/directions/overview) | March 1, 2025 | [Routes API](/maps/documentation/routes) | [Guide](/maps/documentation/routes/migrate-routes) |\n| Routes | JavaScript [Distance Matrix Service](/maps/documentation/javascript/distancematrix) | March 1, 2025 | New JavaScript services will be provided in the future. \"Star\" this [public issue](https://issuetracker.google.com/255359343) to be notified of the availability of the new services. ||\n| Routes | JavaScript [Directions Service](/maps/documentation/javascript/directions) | March 1, 2025 | New JavaScript services will be provided in the future. \"Star\" this [public issue](https://issuetracker.google.com/255359343) to be notified of the availability of the new services. ||\n| Places | [Places API](/maps/documentation/places/web-service/search) | March 1, 2025 | [Places API (New)](/maps/documentation/places/web-service/op-overview) | [Guide](/maps/documentation/places/web-service/migrate-overview) |\n| Places | JavaScript [Places Service](/maps/documentation/javascript/places) | March 1, 2025 | [Place Class](/maps/documentation/javascript/place) | [Guide](/maps/documentation/javascript/places-migration-overview) |\n| Places | [Places SDK for Android](/maps/documentation/places/android-sdk/autocomplete) | March 1, 2025 | [Places SDK for Android (New)](/maps/documentation/places/android-sdk/place-autocomplete) | [Guide](/maps/documentation/places/android-sdk/migrate-overview) |\n| Places | [Places SDK for iOS](/maps/documentation/places/ios-sdk/place-details) | March 1, 2025 | [Places SDK for iOS (New)](/maps/documentation/places/ios-sdk/place-autocomplete) | [Guide](/maps/documentation/places/ios-sdk/migrate-overview) |\n\nLegacyApiNotActivatedMapError\n\nGoogle throws this error when your application is querying a legacy API ([Places\nAPI](/places/web-service/overview-legacy), [Directions API](/maps/documentation/directions/overview), or [Distance Matrix\nAPI](/maps/documentation/distance-matrix/overview)) that is not enabled on your project. In most cases, keep legacy APIs\ndisabled on new projects.\n\nIf you own the application that's throwing this error, use the [equivalent new\nAPI](#active_services_with_legacy_status) instead.\n\nIf you don't own the application that's throwing this error, report this issue\nto your application provider by sharing this URL with them, and follow their\ninstructions to upgrade to a new version. As a short-term solution, consider\nactivating the legacy API(s):\n\n- [Places API](https://console.cloud.google.com/apis/library/places-backend.googleapis.com?utm_source=Docs_error_LegacyApiNotActivatedMapError)\n- [Directions API](https://console.cloud.google.com/apis/library/directions-backend.googleapis.com?utm_source=Docs_error_LegacyApiNotActivatedMapError)\n- [Distance Matrix API](https://console.cloud.google.com/apis/library/distance-matrix-backend.googleapis.com?utm_source=Docs_error_LegacyApiNotActivatedMapError)"]]
