AI-generated Key Takeaways
-
Google Maps Platform pricing is primarily pay-as-you-go, with charges based on usage across various SKUs (e.g., Dynamic Maps, Places Library).
-
Dynamic Maps are billed per load, while Dynamic Street View is billed per panorama; both offer volume-based discounts.
-
Places Library features like Autocomplete, Place Details, and Nearby Search have varying SKUs and prices based on data requested.
-
A $200 monthly credit is available until February 28, 2025, for qualifying Google Maps Platform SKUs.
-
You need to enable billing and use an API key to utilize the services, and manage costs via the Google Cloud Console.
Maps JavaScript API requests generate calls to different SKUs depending on the type of request: for example, map loads trigger the Dynamic Maps SKU and panoramas trigger the Dynamic Street View SKU. Calls to the Places Library, Maps JavaScript API and other JavaScript services are priced separately. For more information, see the SKU details and pricing lists in the following table.
SKU details and pricing for the Maps JavaScript API
The following table shows the SKU details and pricing for the Maps JavaScript API.
Routes library pricing details
The Route and RouteMatrix classes each have three SKUs that determine the
cost of a request. The SKU used to determine the cost is based on the service
you use, Route class or RouteMatrix class, and the features that you use in
the request. For example:
Compute route requests are billed for each Request.
Compute route matrix requests are billed per ELEMENT returned from the request. The number of elements is the number of origins multiplied by the number of destinations. For example, if a request contains two origins and three destinations, then the request is billed for six elements.
The features you use determine which SKU category is billed:
Essentials: Billed for requests that use only basic features with a maximum of 10 intermediate waypoints.
Pro: Billed for requests that use an advanced feature, such as the
TRAFFIC_AWAREorTRAFFIC_AWARE_OPTIMALroute modifiers.Enterprise: Billed for requests that use an enterprise feature, such as two-wheel routing.
The following usage limits are in place for the JavaScript.
Compute routes
Rate limit of 3,000 queries per minute.
Maximum allowed number of intermediate waypoints per
computeRoutesrequest request is 25.
Compute route matrix
The rate limit is 3,000 elements per minute, calculated by number of origins times the number of destinations.
Maximum allowed number of origins and destinations that you can specify by using a place ID or address is 50.
Maximum allowed total number of elements per
computeRouteMatrixrequest withroutingPreferenceset toTRAFFIC_AWARE_OPTIMALis 100.Maximum allowed total number of elements per
computeRouteMatrixrequest withtravelModeset toTRANSITis 100.Maximum allowed total number of elements per
computeRouteMatrixrequest otherwise is 625.
Quotas and usage limits
To review and manage your quotas and usage limits for the Maps JavaScript API, see Quotas and quota alerts.
Adjust quota
Quota limits define the maximum number of requests allowed for a specific API or service within a given timeframe. When the number of requests in your project reaches the quota limit, your service stops responding to requests.
To modify a quota value for your API, follow these steps:
- In the Cloud console, navigate to Google Maps Platform > Quotas.
- Select the API for which you want to modify the quota.
- Identify the quota value that you want to change, and select it using the checkbox.
- Click Edit, enter a new quota value, and click Submit request.
View quota increase requests
To view all quota increase requests, including past and pending requests:
- In the Cloud console, navigate to Google Maps Platform > Quotas.
- Select the API for which you want to view the quota increase request.
- Click Increase Requests.
Terms of Use restrictions
For complete details on allowed usage, consult the License Restrictions section in the Google Maps Platform Terms of Service.