Google Maps Licensing Explained

How Google Maps Licensing Works

Our store locator uses three Google Maps Platform APIs: Maps JavaScript API, Geocoding API, and Places API (New). Each of these APIs is billed separately based on the number of requests made per month.

Google provides every account with a free monthly usage allowance across all APIs. For the vast majority of retail stores and small-to-medium businesses, this free tier is more than sufficient — you would need tens of thousands of map loads or geocoding requests per month before any charges apply. A typical store locator used by real customers, not automated bots, will comfortably stay within the free limits.


What Each API Does

Maps JavaScript API

Renders an interactive map in the browser. Every time a visitor opens a page with an embedded map, it counts as one Dynamic Maps load. This is the visual map that users can pan, zoom, and interact with. The free tier covers 10,000 map loads per month.

Geocoding API

Converts a human-readable address (e.g., "123 Main St, New York") into geographic coordinates (latitude/longitude) and vice versa. This is used when a user types their address to find nearby store locations, or when store addresses need to be pinned on the map. The free tier covers 10,000 geocoding requests per month.

Places API (New)

Powers address autocomplete, place search, and place detail lookups. When a user starts typing an address and sees suggestions appear in a dropdown, that's the Autocomplete feature of the Places API. The free tier covers 10,000 autocomplete requests per month. Autocomplete sessions (where multiple keystrokes lead to a single place selection) can also be billed as a single session at no additional charge under the Autocomplete Session Usage SKU, which has unlimited free usage.


How Google Maps' Free Tier Works

Google Maps Platform uses a pay-as-you-go model billed per 1,000 requests (called "events"). Each API has a free usage cap — requests within that cap cost $0. Charges only apply once you exceed the monthly cap.

Note: In March 2025, Google updated its pricing structure for the Maps Platform. The new system consolidates SKUs into Essentials, Pro, and Enterprise tiers, and introduced tiered volume discounts across a wider range of usage bands. The free caps listed below reflect the current pricing as of this update.

Free Tier Caps for Our Three APIs

All prices are in USD per 1,000 requests. Free cap resets every calendar month.

API / SKU Free Monthly Cap Price after cap (up to 100K) Price 100K–500K Price 500K–1M
Maps JavaScript API



Dynamic Maps (map loads) 10,000 $7.00 $5.60 $4.20
Geocoding API



Geocoding 10,000 $5.00 $4.00 $3.00
Places API (New)



Autocomplete Requests 10,000 $2.83 $2.27 $1.70
Autocomplete Session Usage Unlimited
Place Details Essentials 10,000 $5.00 $4.00 $3.00
Place Details Essentials (IDs Only) Unlimited
Text Search Essentials (IDs Only) Unlimited

Key takeaway: A store with moderate traffic — say, a few hundred unique visitors per day using the store locator — will typically generate well under 10,000 map loads, geocoding requests, and autocomplete queries per month. That means $0 in Google Maps costs for most stores.


Tips for Reducing Costs 💡

If your store's usage grows and you start approaching the free tier limits, these strategies can help keep costs low:

  • Enter your store addresses accurately from the start.

    Every time the app needs to look up the coordinates of a store address, it uses one geocoding request. If you frequently edit or re-enter store addresses, those lookups add up. Getting addresses right the first time means the app only needs to look them up once and can reuse the result indefinitely.

  • Don't add placeholder or test stores to your live account.

    Each store location you add gets geocoded (converted to map coordinates). Adding fake or temporary stores — and then deleting and re-adding them — burns through requests unnecessarily. Use a staging or test environment for experimentation if your plan supports it.

  • Load the map only when needed.

    Instead of initializing the full interactive map on page load, consider showing a static image or placeholder first, and loading the JavaScript map only when the user interacts with it (e.g., clicks a "Show Map" button). This reduces Dynamic Maps loads for users who never interact with the map.

  • Keep your store count reasonable.

    The store locator loads map data for all your active locations. If you have a large number of stores, consider whether all of them need to be listed — deactivating locations that are permanently closed removes unnecessary map requests.

  • Be aware of high-traffic events.

    If you run a promotion, send a large email campaign, or get featured in the press, your website traffic can spike sharply. A sudden surge in visitors to your store locator page will increase map usage proportionally. For planned campaigns, it's worth checking your current usage beforehand so you know how much headroom you have.

  • Check your usage once a month.

    You can see how many API requests your store locator has made in the Google Cloud Console under APIs & Services → Metrics. You don't need to understand the technical details — just look at whether the numbers are growing month over month. If they're climbing toward 10,000, it's a good time to contact support.

  • Set up a billing alert so you're never surprised.

    In the Google Cloud Console, you can set a budget alert that sends you an email if your Maps usage is about to incur charges. Go to Billing → Budgets & Alerts and set a threshold of, say, $1 — this way you'll get a heads-up well before any real cost appears. It takes two minutes to set up and gives you complete peace of mind.


Do you need help?

If you have any questions or run into issues, please contact us — we’re happy to help. Contact support.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us