Most growing apps hit the same moment. The Google Maps Platform invoice arrives and it does not match the budget. Map loads from visitors who bounce after fifteen seconds, autocomplete requests from every address field, place lookups from every search: each one has its own SKU, its own free allowance and its own price per 1,000 calls.
This guide explains how Google Maps Platform pricing works in 2026, recalculates the cost of a typical app at three usage levels from Google's published list prices, and sets those numbers next to MapAtlas pricing for the same workload. Every rate below comes from the Google Maps Platform pricing page, checked on 26 September 2026.
How Google Maps Platform pricing works
Google Maps Platform charges per API product and per call. There is no single "Google Maps API". There are more than fifteen products, each billed under one or more SKUs. The ones most apps use fall into three groups.
Maps products
- Maps JavaScript API: the interactive web map. Billed per Dynamic Maps load, which happens every time a page initialises the map.
- Static Maps API: non-interactive map images. Billed per image request.
- Street View Static API: static Street View imagery, billed under its own SKU.
- Maps Embed API: free and unlimited for standard embeds without JavaScript customisation.
Routes products
- Routes API (Compute Routes) and the legacy Directions API: point-to-point routes. Billed per request, with higher SKUs for features such as traffic-aware routing.
- Route Matrix and the legacy Distance Matrix API: many-to-many travel times. Billed per element, one element per origin and destination pair.
- Roads API: snap-to-road and speed limit data, billed separately.
Places products
- Geocoding API: converts addresses to coordinates and back. Billed per request.
- Places Text Search and Nearby Search: search for places. The price depends on which fields you request.
- Place Details: detailed information about one place, again priced by field tier (Essentials, Pro or Enterprise).
- Place Autocomplete: suggestions as the user types. Billed per request, with session rules covered below.
- Geolocation API: device location from cell towers and Wi-Fi, billed separately.
Free usage since March 2025
Google used to give every billing account a $200 monthly credit. On 1 March 2025 it replaced that credit with a free monthly allowance per SKU. Essentials SKUs such as Dynamic Maps, Geocoding and Autocomplete Requests include 10,000 free billable events a month. Pro SKUs include 5,000 and Enterprise SKUs 1,000. A few SKUs, such as the Maps Embed API, are unlimited.
The same change extended automatic volume discounts. Prices drop at 100,000, 500,000, 1,000,000 and 5,000,000 monthly events, counted across all projects on one billing account. You do not need an enterprise agreement to get them.
| SKU | Free per month | 0 to 100k | 100k to 500k | 500k to 1M | 1M to 5M |
|---|---|---|---|---|---|
| Dynamic Maps | 10,000 | $7.00 | $5.60 | $4.20 | $2.10 |
| Geocoding | 10,000 | $5.00 | $4.00 | $3.00 | $1.50 |
| Autocomplete Requests | 10,000 | $2.83 | $2.27 | $1.70 | $0.85 |
| Place Details Essentials | 10,000 | $5.00 | $4.00 | $3.00 | $1.50 |
| Place Details Pro | 5,000 | $17.00 | $13.60 | $10.20 | $5.10 |
| Compute Routes Essentials | 10,000 | $5.00 | $4.00 | $3.00 | $1.50 |
Prices are USD per 1,000 billable events.
Real cost calculations at three usage levels
The scenario is a local search app with an interactive map, an address search field with autocomplete, place details and route calculations. The model below applies the free allowance first and then the volume tiers, exactly as Google bills them.
Assumptions per active user per month:
- Map loads: one Dynamic Maps load per user.
- Geocoding: 0.1 requests per user, for typed searches.
- Autocomplete: 3 sessions per user, each sending 4 requests before the user picks a result, then one Place Details Essentials call for the address.
- Place details: 0.5 Place Details Pro calls per user, for business detail pages.
- Routes: 0.2 Compute Routes Essentials requests per user.
10,000 monthly users
| SKU | Volume | Monthly cost |
|---|---|---|
| Dynamic Maps | 10,000 loads | $0.00 |
| Geocoding | 1,000 requests | $0.00 |
| Autocomplete Requests | 120,000 requests | $300.10 |
| Place Details Essentials | 30,000 requests | $100.00 |
| Place Details Pro | 5,000 requests | $0.00 |
| Compute Routes Essentials | 2,000 requests | $0.00 |
| Total | $400.10 |
At this size the free allowances cover most SKUs. Autocomplete is the exception, because every keystroke request counts.
100,000 monthly users
| SKU | Volume | Monthly cost |
|---|---|---|
| Dynamic Maps | 100,000 loads | $630.00 |
| Geocoding | 10,000 requests | $0.00 |
| Autocomplete Requests | 1,200,000 requests | $2,182.70 |
| Place Details Essentials | 300,000 requests | $1,250.00 |
| Place Details Pro | 50,000 requests | $765.00 |
| Compute Routes Essentials | 20,000 requests | $50.00 |
| Total | $4,877.70 |
1,000,000 monthly users
| SKU | Volume | Monthly cost |
|---|---|---|
| Dynamic Maps | 1,000,000 loads | $4,970.00 |
| Geocoding | 100,000 requests | $450.00 |
| Autocomplete Requests | 12,000,000 requests | $6,882.70 |
| Place Details Essentials | 3,000,000 requests | $6,550.00 |
| Place Details Pro | 500,000 requests | $7,055.00 |
| Compute Routes Essentials | 200,000 requests | $850.00 |
| Total | $26,757.70 |
These are list prices for the stated usage mix. Your bill changes with the number of requests per autocomplete session, the fields you request, and any contract you sign with Google. Rerun the numbers with your own traffic before you commit to a budget.
The cost drivers most developers miss
Autocomplete requests
Autocomplete is the most common source of bill shock. Under Google's session pricing for Places API (New), a session that ends in a Place Details Essentials call bills its first 12 autocomplete requests at the Autocomplete Requests rate, then the Place Details call. A session that ends in a Pro or Enterprise Place Details call bills no autocomplete requests, only the details call. A session the user abandons bills every request. Debounce the input field and always send a session token.
Field tiers on Place Details and Text Search
Places prices depend on the fields you ask for. The same Place Details call costs $5.00 per 1,000 at Essentials and $17.00 at Pro in the first tier. Asking for one Pro field, such as the display name, moves the whole call to the Pro price. Request the smallest field mask that answers the question.
Distance matrix scaling
Route Matrix and the legacy Distance Matrix API bill per element, and an element is one origin and destination pair. A request with 5 origins and 5 destinations is 25 elements. Delivery planners and "nearest location" features can generate large element counts from a few user actions.
Attribution and terms of service
Google Maps Platform requires Google attribution on map displays, and its terms restrict caching content and using it to build a competing product. Read the Google Maps Platform terms before you plan to store results.
MapAtlas pricing for the same workload
MapAtlas bills fewer SKUs. The pricing page lists the tiers, and the calculator there uses the same numbers. For the scenario above, the comparable MapAtlas services are map loads, search sessions (one per autocomplete session), geocoding and navigation. Place Details Pro has no direct counterpart, so the Google column below leaves it out to compare like with like.
| Monthly users | Google Maps Platform, same basket (USD) | MapAtlas (EUR) |
|---|---|---|
| 10,000 | $400.10 | €46.00 |
| 100,000 | $4,112.70 | €908.00 |
| 1,000,000 | $19,702.70 | €7,563.04 |
MapAtlas prices are in euros and Google prices in US dollars, so convert at the current rate before comparing. The difference comes from three parts of the price list:
- Session billing for search. MapAtlas bills an autocomplete session once, however many keystrokes it takes, so the per-request line that dominates the Google bill does not exist.
- Larger free allowances. 25,000 geocoding requests, 10,000 search sessions, 10,000 map loads and 100,000 navigation requests are free every month.
- Lower map load rates. Each map load tier is priced below the matching Dynamic Maps tier.
GDPR and compliance costs
The price per call is only part of the cost in an EU context. Google LLC is a US company, which brings US law such as the CLOUD Act into the analysis of any data you send it. Depending on your sector, that can mean data protection impact assessments, legal review time and, in regulated industries, changes to your architecture.
Our EU developer GDPR guide covers this in detail. MapAtlas processes requests in the EU by default. The why developers choose MapAtlas page covers the same ground from the product side.
Is migration worth it?
Run the numbers with your own traffic first. Export a month of usage per SKU from the Google Cloud console, apply the tiers above, and compare the result with the MapAtlas calculator.
Interactive maps, geocoding, address autocomplete and routing are available in MapAtlas. Street View and some proprietary Google Places content are not, so check your feature list against the capability pages for map visualisation, geocoding and routing before you plan a migration.
For factors beyond price, see switching from the Google Maps API and map API options for EU developers.
To test the APIs on your own data, sign up for a free account. No credit card is required for the free tier.
Frequently Asked Questions
Does Google Maps still offer the $200 monthly free credit in 2026?
No. On 1 March 2025 Google replaced the $200 monthly credit with a free monthly allowance per SKU: 10,000 billable events for Essentials SKUs such as Dynamic Maps and Geocoding, 5,000 for Pro SKUs and 1,000 for Enterprise SKUs. A few SKUs, such as the Maps Embed API, stay unlimited. Check the Google Maps Platform pricing page for the current figures before you budget.
What is the most expensive Google Maps API product?
Per call, the Pro and Enterprise Places SKUs are the most expensive: Text Search Pro lists at $32 per 1,000 requests and Place Details Pro at $17 per 1,000 in the first volume tier. In total spend, Dynamic Maps and Places Autocomplete usually dominate consumer apps because every page view and every keystroke session can trigger them.
How hard is it to migrate from Google Maps to MapAtlas?
The effort depends on how many Google-specific features you use. Swapping map rendering, geocoding, autocomplete and routing means updating API calls and keys and then testing each flow. Features MapAtlas does not offer, such as Street View, need a separate decision. Check the capability pages and the pricing calculator against your own usage before you plan the work.
