Eleven years after a developer first reverse-engineered a Google Map, there are more than three million location-informed apps and websites generating billions of requests daily, all powered by Google Maps APIs. From unicorns to passion projects to public service, the power of maps and location data is limited only by the creativity of developers.

The Internet landscape has dramatically shifted from desktops to mobile devices in the last decade, and as a result, our services have evolved to meet the needs of our developers and their users. More devices means exponentially more requests, and hundreds of millions of global users are just coming online. Therefore, today we are announcing a few updates to bring more simplicity and consistency to our Standard Plan limits and pricing.

As of June 22, 2016 we are making the following changes to the Google Maps APIs Standard Plan:

  1. We no longer support keyless access (any request that doesn't include an API key). Future product updates are only available for requests made with an API key. API keys allow us to contact developers when required and help us identify misbehaving implementations.
  2. We have implemented a simple 25,000 map loads per day free limit to new Google Maps JavaScript API, Static Maps API, and Street View Image API implementations. The confusing 90-consecutive-day grace period for these APIs is being retired on October 12, 2016. With this change, developers can predictably plan for growth while media sites and US nonprofits can request more quota at no charge via our dedicated support programs.
  3. We have reduced the daily map load maximum limit you can purchase for Google Maps JavaScript API, Static Maps API, and Street View Image API from 1,000,000 to 100,000 requests per API.* We believe higher-volume developers are best served with a Premium Plan license, which includes technical support and a Service Level Agreement, and with this change we've also created consistency between Standard Plan quotas across our maps and web service APIs.
  4. We now count Google Maps JavaScript API client-side requests towards the daily limit of the associated web service API.*

The new policies will apply immediately to all Maps API implementations created on or after June 22nd, 2016.

Existing applications have been grandfathered based on their current usage to ensure that they continue to function both now and in the future. We will also be proactively contacting all existing API key users who, based on usage growth patterns, may be impacted in the future. If you’re an existing user, please take the time to read our Policy Update for Standard Plan summary for details on how each of these changes might affect your implementation.

Posted by Ken Hoetmer, Product Manager, Google Maps APIs

* Exceptions may apply for implementations that were exceeding new quotas prior to June 22, 2016.


While at Google I/O, I had a chance to sit down for a cup of coffee with Ankur Kotwal, Developer Advocate at Google and Ken Hoetmer, Product Manager for the Google Maps APIs. Both had an interesting perspective on how maps have evolved and where they are headed.

In Ankur’s session we discussed technologies beyond the visualization aspects of maps, including the Directions API, Places API and Roads API. He highlighted innovative ways developers are using Google Maps APIs including VR, marker clustering and heatmaps. We also spoke about Santa Tracker, which Ankur has been a part of for four years (he also revealed what Santa likes to do during his time off). Ankur announced the new Google Maps APIs Beta program, so if you have not signed-up, head over to the site to apply.

Learn about developing Geo applications over Coffee with Ankur Kotwal

While speaking with Ken, we discussed how he started working with maps and the Google Maps API as well as how he eventually landed at Google on the Sydney maps team. Ken spoke about how use cases have evolved from interactive maps to more powerful applications and insights driven by location information made available through the APIs. He shared details about some newer APIs including native iOS and Android Places API, Roads API, Directions API and Predictive Travel Time (estimating travel time and routes based on now or in the future). He also highlighted some notable location-based intelligence use cases including Uber, GoJek, Dash Labs and the city of Sydney.

Google Maps APIs and Coffee with Product Manager Ken Hoetmer

About Laurence: I am a Developer Advocate at Google, working on mobile services, specializing in cross-platform developer technologies. As the host of 'Coffee with a Googler' on the Google Developers channel I’m able to meet with some of those most creative and inspiring developers at Google and learn about the projects they’re leading. When I’m not Googling, I’m involved in many things, including working on the revival comics for the Stargate TV shows, and enjoying the geek cred that this brings.


Over the past few months we've rolled out several JavaScript console error message improvements designed to help developers implement Google Maps JavaScript API into web apps. Our goal was to:

  • Give developers more descriptive error messages
  • Provide developers with a suggested solution to resolve the error
  • Avoid popups for displaying error messages
  • Create a positive experience for end-users in the event an error occurs

How do developers usually use the JavaScript console? When? Why?
Web developers use browser tools to develop and debug their applications. They can find various messages in the JavaScript console to which their application, libraries or APIs write. For users of our Google Maps JavaScript API, we have returned error messages in the JavaScript console for some types of Maps API errors. But, these messages were often not descriptive enough for web developers to investigate the issue and find solutions.

What happened when users saw the old error messages?
Our previous popup error messages showed up on the top of the web page. This JavaScript alert prevented users from interacting with the page until the “OK” button was clicked, even if they were not interacting with the map. We served 4 basic error messages that pointed to the general troubleshooting page of our website.

What do developers and users see now?
We now display 21 different error messages in the console —you can see the full list in our developer documentation. In addition, we've provided direct links from specific errors to self-service solutions on the developer site. We've also simplified the error messages displayed to end users -the improved error appears in the map div itself, allowing users to interact with the rest of the page even if the map load fails.
JS Console error message.png

We hope these changes will improve your implementation and interactions with your end users.

I’ve been a Technical Solutions Engineer at Google for 6 years. I enjoy working on the Google Maps APIs because there is always a new discovery on maps. Outside of Google, I love beer, especially after skiing in the mountains.


While at Google I/O, Laurence Moroney and I had a chance to present our session titled ‘Streamlining developer experiences with the Google Maps APIs’. We’re pleased to share it more broadly for those of you who were not able to be there in person:
Streamlining developer experiences with the Google Maps APIs
The Google Maps APIs provide a seamless experience for developers of all levels. Some want to offer a map or directions but don't want to build these things themselves; this can be achieved with just a few lines of code. Other developers prefer to integrate natively with off-the-shelf widgets. Finally, some developers want complete control over every aspect of the presentation. This session highlights the Maps APIs that represent the full gamut of the developer experiences, enabling you to get going immediately and scale as necessary. You'll see how widgets and services can be added over time with a suite of Maps APIs, services and libraries.
I am a Developer Advocate at Google experienced in building on Android and the Google Maps API. I am based out of the Google Sydney office and lead the Geo Developer Relations & Next Billion Users Developer Relations team to inspire developers towards building on the Google developer platform. When I’m not at Google inspiring other developers, I enjoy spending time with my kids.


The Google Maps Operations team gets to work with thousands of developers each year to create great user experiences and powerful analytics built on maps and location data. We drew from these experiences to create a brand new Google Maps APIs course, in collaboration with Udacity, that teaches developers best practices when using our web APIs.
Google Maps 03.jpg

The new course, available today for free, gives you step-by-step tutorials that demonstrate how to integrate maps and location features into your website, and how to get useful location related data using various Web Service APIs.

You’ll walk through building a real-estate listings site using a uniquely styled Google map, data visualization, and street view panoramas. You’ll practice developing location-related features: calculate distance between locations, get directions, and view places of interest data.
You’ll also see other examples of Google Maps APIs in action and learn how to secure and monitor your deployment using the Google APIs Console. At the end of the course, you’ll have built your first map-enabled site and be ready to create your own projects using location data, services, and maps!

Whether you’re new to Google Maps APIs or just want a refresher, head over to Udacity to learn about how to start adding location features and map visualizations into your websites, today!

I happily joined Google in September, 2015. I love working with the Google Maps APIs because they are easy to build with and enable end users to have an intuitive, familiar experience in any site or app. Outside of Google I like to play Zelda, eat pizza and drink coffee with my dog.


At Google I/O, Ravi Palanki, Android Place API technical lead and I presented our session titled ‘Understand your Place in this world’. Even if you were not able to attend Google I/O in person, you can now watch our session:
Understand your Place in this world
Humans navigate a world made up of places with names, addresses and phone numbers—not lat/long coordinates. The Google Places API enables an app or website to present location data to users in a human-centered fashion. In this session we shared how you can use the Places API to discover your environment. I walked the audience through the main use cases and Places API functionalities, across mobile and web. We also showed off some newly-released mobile widgets, and Ravi did a deep-dive into the benefits of the mobile platform, such as optimization for mobile device battery life and increased device accuracy. This session is a great starting point to learn how the Places API can make all your apps -- not just map-centric ones -- smarter.
With the Google Places API you get data from the same database used by Google Maps and Google+ Local. Places features more than 100 million businesses and points of interest that are updated frequently through owner-verified listings and user-moderated contributions.
  • Use the power of mobile to give your users contextual information about where they are, when they’re there with the Places API for Android.
  • Search for and retrieve rich information about local businesses and points of interest, available on every screen with the Places API Web Service.
  • Add autocomplete to any application, providing type-ahead location-based predictions like the search on Google Maps.
I am a product manager on the Maps API team. In my role, I focus on the Places API across all platforms and geographies. When I’m not at Google, I love running coastal trails, playing the piano and enjoying the fantastic lifestyle in Sydney!


Day 1 done! We had a great first day at Google I/O—more than 800 developers visited our Geo sandbox to check out apps, play with 360 degree cameras and most importantly, chat with our engineers, product managers, and developer advocates about the apps they’re building.

The Geo sandbox features Sugarbear, a 1959 PD-4104 General Motors Coach that measures 35’ long by 8’ wide with a diesel engine outfitted for biodiesel. Sugarbear made an epic trip across the USA after last year’s I/O and we’ve brought her back this year for more demo fun. You can engage with interactive maps experiences and check out customer applications inside the bus. Climb Yosemite's El Capitan, calculate your solar potential with Project Sunroof, and see how Nest and the Environmental Defense Fund use location data to make our lives better. Sugarbear also features Google Maps APIs customers Trucker Path, Zendrive, Postmates, GTX Corp and Vagabond.

The Google I/O event shuttle buses are also being tracked and visualized in real time by an app we built using Firebase and Google Maps APIs. Within the Geo sandbox you can check out the app on the big screen and chat with the developers about how it works on the inside (hint: ask for Brett).

Geo also hosted one session yesterday: Location and Proximity Superpowers: Eddystone + Google Beacon Platform and we have several additional sessions on Thursday and Friday, including Understand your Place in this world and Building geo services that scale.

Finally, don’t forget about our office hours—scheduled for Thursday, May 19 at 4pm. We’ll be in the tent for an hour...bring your Maps and Location questions for our Product Managers and Developer Advocates.