Note: The Google Maps Platform Premium Plan is no longer available for sign up or new customers.
This page is only for customers with the new version of the Google Maps Platform Premium Plan, which became available in January 2016.
Have the Premium Plan or a previous license?
To determine which license you have:
> In the Google Cloud Support Portal,
click Maps: Usage Report on the left.
> Does the ID at the top of the report have the following format?
gme-[company] & proj-[number] ([type])
If yes, you have the Premium Plan.
If no, you have a previous license
(Maps APIs for Work or Maps API for Business).
Usage rates
With the Google Maps Platform Premium Plan, your application consumes quota at different rates, depending on the APIs it requests.
Maps APIs Credits
As a Premium Plan customer, you purchase quota—called Maps APIs Credits—for one or more years, based on an estimate of your application's annual usage. All of your application's requests for Maps APIs consume credits from the pool of credits you purchased. For example, if your application uses the Maps JavaScript API to display a map, it will consume credits for the Maps JavaScript API map loads. If your application consumes all of the credits in the pool, you can purchase additional credits, as needed.
Usage rates by API
| This type of API request... | Consumes this many Maps APIs Credits... |
|---|---|
| Maps JavaScript API map load | 1 |
| Maps Static API, Street View Static API map load |
0.25 |
| Street View Static API metadata request |
0 |
| Mobile SDKs (Android, iOS) map load | 1 |
| Places API server-side and client-side request; excluding Place Autocomplete | 2 |
| Place Autocomplete (server-side and client-side) request | 0.1 |
| Web service APIs (server-side) request: Geocoding API, Directions API, Distance Matrix API (per element), Elevation API, Geolocation API, Time Zone API, Roads API | 0.25 (after included daily usage limit) |
| Client-side request: Geocoding API, Directions API, Distance Matrix API (per element), Elevation API | 0.25 (after included daily usage limit) |
Map loads
Web APIs:
A single map load is charged when any of the following occur:
- A web page or application displays a map using the Maps JavaScript API.
- An application requests a single map image from the Maps Static API.
Street View panoramas are charged separately from map loads:
- A static Street View panorama is charged for each request to the Street View Static API to embed a static (non-interactive) Street View panorama.
- A dynamic Street View panorama is charged for each instantiation of a panorama object in a Maps JavaScript API, Maps SDK for Android, Maps SDK for iOS application.
After a web page or application loads a map, or a static map image, or a Street View panorama, any user interactions with it, such as panning, zooming, or switching map layers, do not generate additional map loads or affect usage limits.
Mobile SDKs:
A single map load is charged for each instantiation of a Google map or panorama object in an Android or iOS mobile application:
- A
GMSMapVieworGMSPanoramaViewobject on iOS. - One of
MapFragment,SupportMapFragment,MapView,StreetViewPanoramaFragment,SupportStreetViewPanoramaFragment, orStreetViewPanoramaViewon Android. A map load is counted each time the relatedonCreate()method is called.
Once a mobile application loads a map or a Street View panorama, any user interactions with it do not generate additional map loads or affect usage limits.
Places API usage
Requests for Place Search, Details, and Photos are charged separately from requests for Place Autocomplete. For example, in an Autocomplete widget, if a user enters an average of 5 characters (keystrokes) to find a place, and the user then selects that place to get details about it, your application consumes credits as follows:
5 Place Autocomplete requests × 0.1 (0.5 credits) + Place Details (place selection) request (2 credits) = 2.5 credits
The Places SDK for Android and the Places SDK for iOS are not available for sale and therefore not included with the Premium Plan.
The Places API is too expensive. What can I do to reduce costs?
We recommend using the
Maps JavaScript API Place autocomplete widget.
To reduce the cost of using the autocomplete widget, use the
placeIdOnly option to enable direct access to
place IDs from the
Place Autocomplete service. The placeIdOnly option skips
Places Details requests for applications
that only need an address, not full business details. To get the corresponding
address, pass place IDs to the geocoding service or the Geocoding API.
You may also pass place IDs to the directions or distance matrix service or the
Directions API or Distance Matrix API
instead of an address text string or latitude/longiture pair.
The Google Maps API Geocoder Tool and the
Place Autocomplete and Directions example have been updated to illustrate how
to use the
placeIdOnly option.
Usage Limits
Total usage limits
All of your application's requests for APIs consume Maps APIs Credits. Therefore, your application's total usage limit is determined by the number of credits you purchased. If you run out of Maps APIs Credits, your application's requests will continue to succeed, but your account may be subject to overage fees. In this case, you'll need to renew your Google Maps Platform Premium Plan license as soon as possible to avoid a suspension of your account. As you consume your quota, Google sends consumption notices via email based on the following increments: at 25% used (if used within the first 60 days), 50%, 75%, 85%, 100%, 110%, and 130%.
Maps JavaScript API
Requests for the Maps JavaScript API that generate map loads are applied against the total number of Maps APIs Credits purchased annually for your Premium Plan.
Maps JavaScript API services (client side)
The following are usage limits for client-side services that your application requests from the Maps JavaScript API:
| Service | Limits |
|---|---|
| Directions | Shared* daily free quota of 100,000 requests per 24 hours; additional requests applied against the annual purchase of Maps APIs Credits. Maximum of 25 waypoints per request. Rate limit applied per user session, regardless of how many users share the same project.** |
| Elevation | Shared* daily free quota of 100,000 requests per 24 hours; additional requests applied against the annual purchase of Maps APIs Credits. Maximum of 512 points per request. Rate limit applied per user session, regardless of how many users share the same project.** |
| Geocoding | Shared* daily free quota of 100,000 requests per 24 hours; additional requests applied against the annual purchase of Maps APIs Credits. Rate limit applied per user session, regardless of how many users share the same project.** |
| Distance Matrix | Shared* daily free quota of 100,000 elements per
24 hours; additional requests applied against the annual purchase of Maps APIs
Credits. Up to
100 elements per request
(with a maximum of 25 origins and 25 destinations
per request). Note: requests
using mode=transit or using the optional parameter
departure_time when mode=driving are limited
to 100 elements per request. Rate limit
applied per user session, regardless of how many users share the same project.**
|
* The
** When you first load the API, you are allocated an initial quota of
requests. Once you use this quota, the API enforces rate limits on additional requests
on a per-second basis. If too many requests are made within a certain time period, the API
returns an |
|
Google Maps Mobile SDKs
| Services | Limits |
|---|---|
Maps SDK for Android |
|
Each map load is applied against the total number of Maps APIs Credits purchased for your Premium Plan |
Google Maps Image APIs
| Services | Limits |
|---|---|
| Maps Static API | Requests are applied against the total number of Maps APIs Credits you purchased for your Premium Plan. The maximum image size is 2048 by 2048 pixels, depending on the |
Street View Static API |
Requests are applied against the total number of Maps APIs Credits you purchased for your Premium Plan. The maximum image size is 2048 by 2048 pixels. Note that Street View Static API metadata requests are free and do not consume any Maps APIs Credits. |
Your application can request Maps Static API images up to 2048 by 2048 pixels.
Because the scale value in a static map request affects the number of
pixels returned, the maximum size value is different for
each scale level:
| Scale | Max Size | Returns |
|---|---|---|
| 1 | 2048x2048 |
2048x2048 |
| 2 | 1024x1024 |
2048x2048 |
| 4 | 512x512 |
2048x2048 |
The Street View Static API does not support the scale parameter.
Web service APIs
| Web service | Limits |
|---|---|
| Directions | Shared* daily free quota of 100,000 requests per 24 hours; additional requests applied against the annual purchase of Maps APIs Credits. Maximum of 25 waypoints per request. 50** requests per second. |
| Elevation | Shared* daily free quota of 100,000 requests per 24 hours; additional requests applied against the annual purchase of Maps APIs Credits. Maximum of 512 points per request. 50** requests per second. |
| Geocoding | Shared* daily free quota of 100,000 requests per 24 hours; additional requests applied against the annual purchase of Maps APIs Credits. 50** requests per second. |
| Distance Matrix | Shared* daily free quota of 100,000 elements per
24 hours; additional requests applied against the annual purchase of Maps APIs
Credits. Up to
625 elements
per request (with a maximum of 25 origins and 25 destinations
per request). Rate limit
of 1,000 elements per second.
Note: requests using the optional parameter departure_time
when mode=driving are limited to
100 elements per request. |
| Geolocation | Shared* daily free quota of 100,000 requests per 24 hours; additional requests applied against the annual purchase of Maps APIs Credits. 50** requests per second. |
| Time Zone | Shared* daily free quota of 100,000 requests per 24 hours; additional requests applied against the annual purchase of Maps APIs Credits. 50** requests per second. |
| Roads | Shared* daily free quota of 100,000 requests per 24 hours; additional requests applied against the annual purchase of Maps APIs Credits. 50** requests per second. Each request may contain up to 100 points. |
* The
** Default rate limit, to prevent abuse. Learn how to optimize web service usage or request a rate limit (QPS) increase. |
|
Places API
| Services | Limits |
|---|---|
| Places API |
Requests are applied against the total number of Maps APIs Credits you purchased for your Premium Plan. Default rate limit is 50 requests per second. Learn how to optimize web service usage or request a rate limit (QPS) increase. |
| Places API client-side services | Requests are applied against the total number of Maps APIs Credits you purchased for your Premium Plan. Unlimited requests per second, per Premium Plan project.* Additional rate limit applied per user session, regardless of how many users share the same project.** |
|
* All web applications using the credentials of same Premium Plan project. ** When you first load the API, you are allocated an initial quota of requests. Once you use this quota, the API enforces rate limits on additional requests on a per-second basis. If too many requests are made within a certain time period, the API returns an OVER_QUERY_LIMIT response code. The per-session rate limit prevents the use of client-side services for batch requests. For batch requests, use our web service APIs. |
|
Usage model summary
The following chart provides a summary of our Google Maps Platform Premium Plan usage rates and usage limits:
