Cloud-based maps styling now has a refreshed map style available for web and mobile. This update to map styling includes a new default color palette, modernized pins, and improvements to map experiences and usability. For more information, see New map style for Google Maps Platform. To start using the new map colors with cloud-based maps styling, see Update a map style to the latest version.
[[["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-02-24 UTC."],[[["Before updating a production map style, it's recommended to test changes in a duplicated style to ensure desired results."],["The testing process involves duplicating the production style, making and publishing changes, associating it with a separate map ID for staging, and thoroughly testing in the staging environment."],["Once satisfied with the tested changes, associate the updated style with your production map ID for implementation."],["Duplicated styles do not inherit version history from the original, requiring manual updates to the original style for historical tracking."],["Style changes may take a few hours to reflect across all platforms and devices."]]],["To test map style updates before production, duplicate the existing production map style. Make and publish changes to the duplicate, then associate it with a separate map ID for staging. Test the style in the staging environment. If satisfied, link the updated style to the production map ID. Note that style changes can take a few hours to appear. Duplicated styles don't maintain version history; for history, apply tested changes to the original style.\n"]]