Is Google Maps API free in 2026? The per-SKU limits, and the calls that cost nothing

Google Maps Platform still has a free tier, but not the one most articles describe. The old $200 monthly credit is gone, so the answer to is Google Maps API free now depends on which SKUs your map calls: a few are free at any volume, most give you 10,000 calls a month, and some stop at 1,000.

That distinction decides whether a store locator, a contact-page map or an address field on a checkout form costs you nothing or arrives as a bill. Below is what Google's own pricing list, billing FAQ and docs say as of October 23, 2026 - the per-SKU caps, the SKUs priced at $0, where small sites actually get charged, and the one setting that stops a charge rather than emailing you about it.

Is Google Maps API free? It depends on the SKU, not the API

Google does not bill per API. It bills per SKU, and each SKU carries its own free monthly allowance of what Google calls billable events. The allowance is set by the tier the SKU belongs to, and Google's pricing list publishes the cap next to every one.

The allowance sits on each SKU separately. Ten thousand Geocoding calls do not touch the Dynamic Maps allowance, and spending the Dynamic Maps allowance does not reduce what Geocoding gives you free. That is the part that trips people up in both directions: a project can look busy and still bill $0, and a project can look quiet and still bill, because one page view often fires several SKUs at once.

One API can also span tiers. Routes, Places and Maps each have Essentials, Pro and Enterprise SKUs, and the fields you request decide which one you land on - so the same endpoint can be free this week and billable next week if a developer adds a field.

The $200 monthly credit ended on March 1, 2025

If you read somewhere that Google gives every project $200 of free Maps usage a month, that was true until March 1, 2025. Google's billing and pricing FAQ describes the change as "modifying the USD $200 monthly recurring credit by offering a free monthly usage threshold for each Core Services SKU," with Essentials at 10,000 free monthly billable events, Pro at 5,000 and Enterprise at 1,000.

The FAQ works a plain example. A customer making 20,000 Geocoding requests a month paid $0 before March 1, 2025, because the $200 credit absorbed it. From that date they get 10,000 free requests and are billed for the other 10,000, for a bill of $50 a month.

In our view this is the single reason the question keeps getting asked: the change is 19 months old, and a large share of the pages ranking for it are either older than the change or published by companies that sell a Maps alternative. Both have a reason to describe the free tier as worse or simpler than it is. The arithmetic above comes from Google's own FAQ, and you can check it against the pricing list in a minute. It is the same pattern we found when we looked at whether Indeed is free for employers - the vendor's own terms were clearer than anything written about them.

One honesty note: Google's pricing list says upcoming changes include adjustments to discounts and credits, and that some services are moving to Legacy status. The free thresholds below are what the page showed on October 23, 2026, and the page itself is the only version that counts.

Which Google Maps APIs are free at any volume

This is the part almost nobody writes down. Google's pricing list marks a set of SKUs as Unlimited rather than giving them a numeric cap. As of October 2026 they are:

• Maps: Embed, Maps SDK, Street View Metadata
• Places API (New): Autocomplete Session Usage, Place Details Essentials (IDs Only), Text Search Essentials (IDs Only)
• Places API Legacy: Autocomplete per session when included with Place Details, Basic Data, Find Place (ID only), Place Details ID Refresh

The Embed one has real consequences. The Maps Embed API billing page states that "the Maps Embed API is free to use with unlimited requests" and that "there are no daily or usage rate limitations when using the Maps Embed API," with no short-term queries-per-second or long-term queries-per-day limits either. An API key is still required for every request.

So a single-location map - a restaurant's address, a clinic's front door, an office on a contact page - can be an Embed iframe that never bills, at any traffic level. Build the same map with the Maps JavaScript API and you are spending the Dynamic Maps allowance: 10,000 map loads a month, roughly 330 a day.

Skip the Embed API if you need to draw your own markers, cluster hundreds of pins, react to clicks on the map, restyle it to your brand, or read coordinates back into your app. Those are the things you pay Dynamic Maps for, and they are worth paying for. The mistake is paying for them on a page that only ever shows one pin.

How many free calls Google Maps API gives a real store locator

Take a locator with 40 branches, 15,000 visits a month, where each visit loads a map and geocodes one typed address. The map loads sit on Dynamic Maps: 15,000 against a 10,000 cap, so 5,000 are billable. The address lookups sit on Geocoding, which has its own 10,000, so all 15,000 do not fit there either.

Two changes make that free. Cache the geocoded coordinates for your own 40 branches once instead of geocoding on every page view, and the Geocoding SKU drops to near zero. Serve the map as an Embed where the page only needs to show locations, and the Dynamic Maps line disappears. The remaining question is whether your interface genuinely needs the interactive map, and that is a product decision, not a billing one.

The general rule we would apply: count billable events per page view, per SKU, before you count visitors. A page that fires four SKUs on load hits four separate caps, and the first one to run out is the one that bills.

Address autocomplete bills by the session, and that is where the surprise lives

Autocomplete is the SKU most likely to charge a small site, because it is billed by session rather than by keystroke and the session rules are not obvious. Google's session pricing page sets out the mechanics.

A session begins with the first Autocomplete (New) request that includes a session token and continues through later Autocomplete requests with the same token. It is then terminated by a request to Place Details (New) or Address Validation that uses that token. Three rules follow from that, and all three cost money when they are broken:

1. Sessions that never reach a terminating Place Details (New) or Address Validation request are billed only for their Autocomplete requests, under the Autocomplete Requests SKU - the per-request rate, with no session discount.
2. In the location-only case, where the session ends with one Place Details (New) request for Essentials fields, the first 12 Autocomplete requests are billed at the Autocomplete Requests SKU. Requests after the first 12 fall under Autocomplete Session Usage, "meaning there is no charge for those requests," and the terminating request is billed at Place Details Essentials.
3. Reusing a token after its session has ended is billed as if no session token were sent at all.

The practical reading: sending session tokens and always finishing with a Place Details call is what turns a stream of keystrokes into one cheap or free session. An autocomplete field that fires requests without a token, or that lets users abandon the field without selecting a place, pays per keystroke up to 12 of them per attempt. On a checkout form with thousands of abandoned address fields a month, that is the line item people cannot explain.

A quota cap stops a bill. A budget alert does not

The sentence we would put in front of every new Maps project is on Google's cost management page, stated flatly: "Setting a budget does not automatically cap Google Cloud or Google Maps Platform usage or spending." Budget alert emails "don't automatically prevent the use or billing of your services." They tell you after the fact.

What does cap spending is a quota. The same page says quotas "restrict how much of a Google Maps Platform service can be used by your Google Cloud project" and that quota limits "prevent unexpected charges by capping the number of requests your project can make." Quotas exist by default and can be adjusted per service in the Google Cloud console.

The trade-off is real and Google names it: "setting a quota too low can impact your ability to use the API." A quota that bites during a traffic spike breaks your map for real visitors. Our own approach would be to set each quota a comfortable multiple above your normal day rather than just above it, and to treat the budget alert as the thing that tells you to go look at the quota. The page also warns that the Quotas page is not a source of truth for billing, so reconcile against the billing report, not the quota counter.

Prototyping without a credit card: the Maps Demo Key

If what you actually want is to try the API before anything touches a payment method, the Maps Demo Key is Google's answer: a no-cost key that lets you start prototyping "without entering billing information." It needs a personal Google Account - Workspace accounts are not eligible - and Google says it "is not designed for production use."

It covers a limited set of features. On the Maps JavaScript API side: 2D and 3D map rendering, markers and events, map styling, the Places UI Kit, drawing tools and the Place class. On the web service side: Maps Grounding Lite, Places API (New), Geocoding API v4, Compute Routes and the Weather API. Places API (New) under the demo key excludes user-generated content such as photos and reviews, and anything outside the supported list requires attaching a billing account or creating a standard key.

Two details make it genuinely safe for evaluation. The key has no HTTP referrer, IP or app restrictions, so it is not something to ship. And when you reach its daily limit, Google says "your usage is paused until the following day with no risk of charges" - the opposite behavior to a standard key, which bills past the free threshold instead of stopping.

When another maps provider is cheaper than Google's free tier

For straightforward map rendering and geocoding at moderate volume, two providers listed in our Maps & Location category publish larger free allowances than Google's Essentials SKUs. Prices below are from each vendor's own pricing page, checked October 23, 2026.

Mapbox lists no free allowance for its Permanent Geocoding API, which is the one you need if you intend to store coordinates - worth checking before you plan around the 100,000 temporary requests. Geoapify's allowance is in credits rather than requests: its pricing page says a simple Geocoding, Places or Routing request generally costs one credit, while map tiles and isolines are counted differently.

The counter-argument for staying with Google is about place data rather than pixels. If your product depends on business listings, opening hours, reviews or search quality for obscure addresses, we would treat the dataset as the thing you are actually paying for, and a cheaper tile bill does not replace it. Upfynd lists 67 Maps & Location products as of October 2026, including the open-source library OpenLayers and Stadia Maps, so the shortlist is longer than two - but switching costs are concentrated in the data, not the SDK.

What to do this week

Open your Google Cloud billing report and group it by SKU, not by API. That report, not any article, tells you which caps you are near. Then make three decisions: move any single-pin map to the Embed API, cache geocodes you look up more than once, and put a quota on every SKU that appears in the report.

If you are choosing a provider rather than trimming a bill, start from the Maps & Location category and the location features in our e-commerce listings, and verify every number on the vendor's own pricing page before you commit - ours included. If you build a mapping or location tool yourself, you can list it on Upfynd for free.