DEPRECATED: Legacy cloud styling is deprecated and is slated for retirement starting on or after March 18, 2025. At that point, your legacy map styles will automatically update. Google recommends you update to the new cloud-based maps styling before March 2025. For more information about the deprecation, see
Deprecations. To update your legacy styles, see
Update a map style to the latest version.
Set up and billing - legacy cloud-based maps styling
Before you begin
Create a map ID:
To use cloud-based maps styling, your map must be loaded using a
map ID.
Update from hard-coded styling:
Before adding a map ID to use cloud-based maps styling
on an existing map that is customized with hard-coded styling, such as JSON or
URL query parameters, remove the hard-coded styling to avoid a
potential conflict with future features. You can
import your JSON styling into a new map style.
Billing
Using cloud-based maps styling requires a
map ID. On
Maps SDK for Android, Maps SDK for iOS, and JavaScript,
using a map ID incurs a charge against the
Dynamic Maps SKU. On the Maps Static API,
using a map ID incurs a charge against
the Static Maps SKU.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-03-01 UTC.
[null,null,["Last updated 2025-03-01 UTC."],[[["Cloud-based map styling requires using a map ID, which is linked to specific billing SKUs."],["Before implementing cloud-based styling, remove any existing hard-coded styling from your maps to prevent conflicts."],["A map ID is necessary to utilize cloud-based map styling features."],["Using cloud-based map styling with a map ID will incur charges based on the specific Maps SDK or API you are using."]]],[]]
