Is the Google Maps API Free? What the Free Tier Covers in 2026

Free monthly usage per SKU, prices per 1,000 events, API key and billing setup, and how open-data alternatives compare

Tier cards with bars: 10,000 Essentials, 5,000 Pro and 1,000 Enterprise free Google Maps API events per SKU a month
Tier cards with bars: 10,000 Essentials, 5,000 Pro and 1,000 Enterprise free Google Maps API events per SKU a month

The Google Maps API is free up to a monthly amount per product: 10,000 events for Essentials SKUs, 5,000 for Pro and 1,000 for Enterprise; above that, usage is billed per 1,000 events. You need a billing account even when you stay within the free amounts. Google replaced the old $200 monthly credit with these per-SKU free amounts on 1 March 2025. Below: prices per 1,000 events, the API key steps, how to cap spending, and how open-data alternatives compare (all sources checked 22 October 2026).

Key takeaways

  • Free per SKU, per month: each product (SKU) has its own free amount; there is no longer a shared $200 credit.
  • Billing account needed: an API key for production sits on a project with billing; the Maps Demo Key is for prototyping only.
  • Budgets notify, quotas cap: a budget sends alerts but does not stop usage; quota limits cap the number of requests.
  • Alternatives count differently: daily credits, monthly requests or rate-limited public servers. Compare the terms, not just the numbers.

How Does the Google Maps API Free Tier Work?

The Google Maps Platform free tier is a free monthly usage amount for each SKU. A SKU is one billable product, such as Dynamic Maps, Geocoding or Compute Routes. Each SKU belongs to a category (Essentials, Pro or Enterprise), and the category sets how many events are free each month:

SKU categoryFree events per SKU per monthExamples
Essentials10,000Dynamic Maps, Static Maps, Geocoding, Autocomplete Requests, Compute Routes Essentials
Pro5,000Place Details Pro, Text Search Pro, Nearby Search Pro, Address Validation Pro
Enterprise1,000Route Optimization Fleet Routing, Address Validation Enterprise
Exceptions (Essentials)100,000Map Tiles API: 2D Map Tiles and Street View Tiles
Free usage caps from Google's Maps Platform pricing list (last updated 2026-10-21), checked 22 October 2026.

Several SKUs on the same list are marked Unlimited, meaning there is no charge for them: Embed, Maps SDK (the mobile Maps SDKs), Street View Metadata, Autocomplete Session Usage, Place Details Essentials (IDs Only) and Text Search Essentials (IDs Only).

Bar chart of Google Maps Platform free events per SKU per month: 10,000 for Essentials SKUs such as Dynamic Maps and Geocoding, 5,000 for Pro SKUs such as Place Details Pro, 1,000 for Enterprise SKUs such as Route Optimization Fleet Routing, with 100,000 for Map Tiles 2D and Street View Tiles
The free amount is set by the SKU category and applies to each SKU separately; since 1 March 2025 it replaces the $200 monthly credit. Source: Google Maps Platform pricing list, checked 22 October 2026.

What changed in March 2025

Until early 2025, every account got a $200 monthly credit that it could spend on any product. According to Google's March 2025 changes page, Google "has replaced the USD $200 monthly recurring credit with a free monthly usage threshold for each Core Services SKU", effective 1 March 2025. The practical difference: the free amount no longer moves between products. 10,000 free Geocoding events cannot be spent on Dynamic Maps.

The free amounts recur every month. Google also offers other credits:

  • New Google Cloud customers get a $300 trial credit, which can be used on Maps Platform (Maps Platform pricing).
  • Credit programs exist for nonprofits, startups, education and other groups; the Get started page lists them.

Subscription plans

Besides pay-as-you-go, Google sells monthly subscription plans that bundle popular products at a fixed price. On the Maps Platform pricing page:

PlanPrice per monthCalls included per month
Starter$10050,000
Essentials$275100,000
Pro$1,200250,000
EnterpriseCustomCustom
Google Maps Platform subscription plans, mapsplatform.google.com/pricing, checked 22 October 2026.

Each plan covers a defined set of products, listed on the pricing page. Google states that with a subscription, "Service remains uninterrupted with extra usage billed as pay-as-you-go."

How Much Does the Google Maps API Cost?

After the free amount, each SKU is billed per 1,000 events, and the price per 1,000 drops in higher volume tiers. The table shows commonly used SKUs with the price in the first paid tier:

SKUCategoryFree per monthPrice per 1,000 after free
Dynamic MapsEssentials10,000$7.00
Static MapsEssentials10,000$2.00
Map Tiles API: 2D Map TilesEssentials100,000$0.60
GeocodingEssentials10,000$5.00
Autocomplete RequestsEssentials10,000$2.83
Place DetailsEssentials10,000$5.00
Place DetailsPro5,000$17.00
Text SearchPro5,000$32.00
Nearby SearchPro5,000$32.00
Compute RoutesEssentials10,000$5.00
Compute RoutesPro5,000$10.00
Compute Route Matrix (elements)Essentials10,000$5.00
Compute Route Matrix (elements)Pro5,000$10.00
Route Optimization: Single Vehicle RoutingPro5,000$10.00
Route Optimization: Fleet RoutingEnterprise1,000$30.00
Address ValidationPro5,000$17.00
Time ZoneEssentials10,000$5.00
Prices in USD for the first volume tier; higher volumes cost less per 1,000. Source: Google Maps Platform pricing list, last updated 2026-10-21, checked 22 October 2026.

The category often depends on which fields you request, not only on which API you call. A Place Details request that asks only for Essentials fields is billed as Place Details Essentials ($5.00 per 1,000); adding fields from the Pro category moves the same request to Place Details Pro ($17.00 per 1,000). Routes work the same way: Compute Routes Essentials and Compute Routes Pro differ by the features in the request.

Worked example: a store locator for one month

To see how the free amounts and prices combine, take a store locator with a map, address autocomplete, geocoding of the entered address and a route to the nearest store. One month of usage:

SKUMonthly usageFreeBillablePrice per 1,000Cost
Dynamic Maps30,000 map loads10,00020,000$7.00$140.00
Autocomplete Requests20,00010,00010,000$2.83$28.30
Geocoding5,00010,0000$5.00$0.00
Compute Routes Essentials3,00010,0000$5.00$0.00
Total$168.30/month
List prices from the Google Maps Platform pricing list, checked 22 October 2026, before taxes and any discounts.

Two assumptions matter here. First, the autocomplete calls are billed as Autocomplete Requests; sessions that end in a Place Details call are billed differently, as described on the pricing list. Second, Dynamic Maps is billed per "successful map load" (SKU details), so the map line follows the number of map loads, here one per page view.

One month of a store locator with 30,000 map views, 20,000 autocomplete requests, 5,000 geocoding requests and 3,000 routes, shown in two billing models: Google Maps Platform pay as you go totals $168.30 a month, and Geoapify daily credits total 73,000 credits (about 2,430 a day, Free plan) or 118,000 credits with panning and zooming (about 3,930 a day, API 10 plan at $59 a month)
The same workload in two billing models: a monthly free amount per SKU with pay-as-you-go pricing, and daily credits with plans. The Geoapify side is explained further down in the same store locator on Geoapify. Assumptions: list prices before taxes and discounts, usage spread evenly over 30 days, about 6 vector tiles per map view; checked 22 October 2026.

How Do You Get a Google Maps API Key?

You get a Google Maps API key by creating a Google Cloud project with billing, enabling the APIs you need and creating a key in the console. The steps from Google's Get started page (last updated 2026-10-21):

  1. Create a Cloud project with billing. Google states that you "must set up a billing account" to set up a Cloud project.
  2. Enable the APIs or SDKs you need, for example Maps JavaScript API, Geocoding API or Routes API, in the Maps API Library, or with gcloud services enable.
  3. Create an API key in Credentials → Create credentials → API key, or with gcloud services api-keys create.
  4. Restrict the key before production: limit it to your websites or apps and to the APIs it calls, as described in Google's API security best practices.

Prototyping without billing: the Maps Demo Key

If you only want to try the APIs, Google offers a Maps Demo Key (page last updated 2026-05-21). It is a no-cost key that needs no billing account, made for testing and prototyping and "not designed for production use":

  • Covers: Maps JavaScript API features and some web services, including Places API (New), Geocoding API v4, Compute Routes and Weather API.
  • Limit: a daily limit; when it is reached, usage pauses until the next day.

For a live site, you move to a regular key on a project with billing.

How Do You Keep Google Maps API Costs Under Control?

Google Maps Platform gives you several tools to keep spending predictable, and they do different things. The key distinction from Google's Manage costs page (last updated 2026-10-21): "Setting a budget does not automatically cap Google Cloud or Google Maps Platform usage or spending." Budgets inform you; quotas limit requests.

A short checklist:

  • Set budgets and alerts in Cloud Billing, so you get an email when spending reaches a threshold you choose.
  • Lower quota limits per API in the Cloud Console. Google describes quotas as "capping the number of requests" your project can make, which prevents unexpected charges.
  • Restrict every API key to your domains or apps and to the APIs it needs, so a copied key cannot run up usage elsewhere.
  • Request only the fields you need. In Places API (New) and Routes API, the requested fields decide which SKU a request is billed under, so fewer fields can mean Essentials instead of Pro pricing.
  • Watch usage reports in the Google Maps Platform section of the Cloud Console, per API and per SKU.

Quotas also explain one common error: when a request hits a limit, Google's web services can answer with OVER_QUERY_LIMIT. Our post on Google geocoding rate limits and OVER_QUERY_LIMIT covers the causes and how to pace requests.

Which Free Alternatives Are There, and How Open Are They?

Free alternatives to the Google Maps API differ in four ways: the unit (per day or per month, requests or credits), whether commercial use is allowed on the free plan, whether a card is needed, and the data behind them (open data such as OpenStreetMap, or the provider's own). They also behave differently at the limit: some bill, some pause, some contact you.

Commercial APIs with a free tier

These providers run paid APIs and include a free plan. All rows are from each provider's official pricing page, checked 22 October 2026:

ProviderDataFree tierCardCommercial use on freeMain restrictions
GeoapifyOpenStreetMap and other open data3,000 credits/day (≈ 90,000/month), shared by all APIsNoYes, with attributionUp to 5 requests/s; daily quota; soft limits: we contact you and ask for an upgrade; isochrones up to 15 min
MapboxCommercial APIPer month: 50,000 web map loads, 100,000 Temporary Geocoding requests, 100,000 Directions requests, 100,000 Matrix elements, 100,000 Isochrone requestsOptional; without a card the account is on demo access with lower capsYes; some use cases need a Commercial Application LicenseTemporary Geocoding results are not for storing; Permanent Geocoding has no free tier ($5.00 per 1,000)
MapTiler CloudOpenStreetMap data5,000 map sessions + 100,000 API requests/monthNoNo (testing, proof of concept, personal, non-commercial)MapTiler logo on the map; service pauses until next month
Stadia MapsOpen data200,000 credits/month; geocoding 20 credits per request (≈ 10,000 geocodes), autocomplete (v2) 1, routing 20, matrix 10 per elementNot statedNo ("Commercial use not allowed")No additional usage on Free
TomTomCommercial APIFree requests per API each month: 200,000 for tile APIs (e.g. vector tiles), 20,000 for Routing and other non-tile APIs (some APIs less)NoNot stated; check the termsMonthly limits per API
HERECommercial APIBase Plan includes free monthly transactions per serviceNot statedNot statedAmounts are shown in the pricing calculator on HERE's page; check them there
LocationIQGeocoding API5,000 requests/dayNot statedYes, with a prominent link back2 requests/s, 60/min
OpenCageGeocoding API, OpenStreetMap among its sourcesFree trial: 2,500 requests/dayNoTesting only; production needs a paid plan1 request/s; results may be stored permanently
Free tiers as published on each provider's official page, checked 22 October 2026. "Not stated" means the page does not say; check the provider's terms.

Each option has its own strengths. Mapbox has large monthly quotas and mature web and mobile SDKs. MapTiler and Stadia Maps build on open standards and work with open-source renderers such as MapLibre GL JS. TomTom and HERE offer a wide range of APIs with free monthly amounts per API or service. LocationIQ and OpenCage focus on geocoding, and OpenCage allows storing results permanently.

Public open-source servers

The OpenStreetMap ecosystem also runs public servers for open-source software. They have no fixed quota, but each has a usage policy that limits how you may use it:

ServiceWhat it doesFree useCommercial useMain restrictions
Nominatim public server (OSM Foundation)Geocoding on OpenStreetMapNo fixed quota, no keyGoverned by the usage policyMax 1 request/s; no client-side autocomplete; cache results; bulk geocoding not encouraged; valid User-Agent or Referer; attribution; access can be withdrawn
OSRM demo serverRouting on OpenStreetMapNo fixed quotaNo ("reasonable, non-commercial use-cases")Max 1 request/s; car, foot and bike profiles
openrouteservice (HeiGIT)Routing, isochrones and more on OpenStreetMapDefault limits: Directions 2,000 requests/day, 40/minuteNot statedDaily and per-minute limits per endpoint
OpenStreetMap tiles (tile.openstreetmap.org)Raster map tilesNo fixed quotaLight use onlyBest effort, no SLA; offline use not permitted; blocked if usage degrades the service
Usage policies of the public servers, checked 22 October 2026.

These servers are community and research infrastructure. They suit testing, light use and projects that respect the policy limits, for example a Nominatim request per user action, never per keystroke. For background, see our posts on the Nominatim geocoder and OpenStreetMap routing.

Self-hosting

The software behind the public servers is open source: Nominatim, OSRM, openrouteservice and tile servers can all run on your own hardware. On your own instance there are no per-request fees and the public servers' limits don't apply. Instead, you pay for servers, keep the OpenStreetMap data up to date and maintain the software, which makes self-hosting a good fit for high, steady volumes or offline setups.

What does the same store locator use on Geoapify?

To compare the models on the same workload, we can price the store locator from the worked example in Geoapify credits. Geoapify counts credits per day, and the costs per API come from the Pricing Details and the API docs:

  • Map tiles: 1 tile = 0.25 credits (maps pricing). An 800×600 vector map needs about 4–9 tiles per view; we use 6.
  • Geocoding, Reverse Geocoding, Address Autocomplete: 1 request = 1 credit.
  • Static Maps: 1 + map tiles / 4 + icons credits per image.
  • Routing: 1 credit per waypoint pair, with a surcharge for long routes (routing pricing). A 498,991 m route from Los Angeles to Prunedale, CA costs 1 credit; a 630,340 m route to Marin County costs 2. route_details and elevation each add 1 credit per pair.
  • Places: 1 credit per 20 places returned. Route Matrix with up to 10 locations: sources × targets. Isochrones: 1 credit per 5 minutes.

With these rules, the store locator looks like this. Routes are short (2 waypoints, under 500 km), and the map is counted once at about 6 tiles per view and once with users panning and zooming (activity coefficient 2):

ItemMonthly usageCredits/month (map viewed only)Credits/month (users pan and zoom)
Map views (vector tiles)30,000 views180,000 tiles × 0.25 = 45,000360,000 tiles × 0.25 = 90,000
Address Autocomplete20,000 requests20,00020,000
Geocoding5,000 requests5,0005,000
Routing3,000 routes3,0003,000
Total73,000 ≈ 2,430/day118,000 ≈ 3,930/day
PlanFree (3,000/day)API 10 (10,000/day, $59/month)
Credit costs from the Geoapify maps and routing pricing docs; plans from Geoapify pricing, checked 22 October 2026. Daily figures assume usage spread evenly over 30 days.

Two differences from the Google model follow from this. The quota is daily, so plan for your busiest day rather than the monthly average: a sale weekend can exceed 3,000 credits even when the month fits. And tile-based counting grows with interaction, while Dynamic Maps is billed per map load; a map that is only looked at uses few credits, and one that users explore uses more. The Credits Calculator does this conversion for your own numbers.

The geocoding step itself is a single REST request. Request (REST):

curl "https://api.geoapify.com/v1/geocode/search?text=1600%20Pennsylvania%20Avenue%20NW%2C%20Washington%2C%20DC&limit=1&format=json&apiKey=YOUR_API_KEY"

Simplified response (one result, selected fields):

{
  "results": [
    {
      "formatted": "White House, 1600 Pennsylvania Avenue Northwest, Washington, DC 20500, United States of America",
      "lat": 38.8976387,
      "lon": -77.0365528,
      "result_type": "amenity",
      "rank": { "confidence": 1 }
    }
  ]
}

One request, one credit. See the Geocoding API, Address Autocomplete, Routing API and Map Tiles pages for the full feature lists.

If usage grows past the Free plan, the next step is a daily credit plan. These are the plans on the pricing page, checked 22 October 2026, monthly billing in USD:

PlanCredits per dayPrice per monthRate limit
Free3,000$05 requests/s
API 1010,000$5912 requests/s
API 2525,000$10915 requests/s
API 5050,000$17920 requests/s
API 100100,000$29925 requests/s
API 250250,000$60930 requests/s
CustomUnmeteredfrom $860Unmetered, dedicated endpoint
Geoapify plans from geoapify.com/pricing, checked 22 October 2026.

The Free plan needs no credit card. It may be used in production for commercial sites and apps within its quota, rate limit and feature limits (isochrones up to 15 minutes, isodistances up to 10 km), with a "Powered by Geoapify" link and the data attribution; see commercial use.

Which Option Fits Your Project?

The right choice depends less on the headline free number than on your situation: where your stack runs, whether the project is commercial, and how much volume you expect.

  • Already on Google Cloud, or you need Street View or Google's place content: the Google free amounts may cover a small project. Set quota limits and budget alerts from the start.
  • Commercial project, small budget, no card: Geoapify Free (3,000 credits a day, with attribution) or LocationIQ (5,000 requests a day, with a prominent link back).
  • Testing or a proof of concept: OpenCage's free trial, the MapTiler or Stadia Maps free plans, or the Google Maps Demo Key.
  • Low-volume, non-commercial or hobby projects with OpenStreetMap: the public OSM servers, within their usage policies.
  • High volume or offline use: self-host the open-source servers, or use a custom plan with dedicated resources.

For a task-by-task mapping of Google Maps APIs to Geoapify APIs, see the Google Maps API alternative page. If you only need map display, our free maps API comparison converts each free tier into map views. To start, get a free Geoapify API key and compare plans on the pricing page.

Frequently Asked Questions

Is the Google Maps API free?

Partly. Each SKU has a free monthly amount: 10,000 events for Essentials SKUs, 5,000 for Pro and 1,000 for Enterprise; above that, usage is billed per 1,000 events. A billing account is required. See the Google Maps Platform pricing list (checked 22 October 2026).

Does Google still give a $200 monthly credit?

No. On 1 March 2025, Google replaced the $200 monthly recurring credit with a free monthly usage threshold for each SKU. See Google's March 2025 changes. New Google Cloud customers can still use the $300 trial credit on Maps Platform.

Do I need a credit card for a Google Maps API key?

For a regular API key, yes: Google requires a billing account on the Cloud project. For testing and prototyping without billing, Google offers the Maps Demo Key, which has a daily limit and is not designed for production use.

How much does the Google Maps API cost per 1,000 requests?

It depends on the SKU. In the first paid tier: Dynamic Maps $7.00, Static Maps $2.00, Geocoding $5.00, Autocomplete Requests $2.83, Place Details Pro $17.00, Text Search Pro $32.00 and Compute Routes Essentials $5.00 per 1,000. Higher volumes cost less per 1,000. See the pricing list (checked 22 October 2026).

Can I cap Google Maps API spending?

Yes, with quota limits: Google describes them as capping the number of requests a project can make, and you can lower them for each API. Budgets and alerts only notify you; Google states that a budget does not cap usage or spending. See Manage costs.

Is there a free Google Maps API alternative for commercial use?

Yes. Geoapify's Free plan allows commercial use with attribution (3,000 credits a day, no card; see commercial use). LocationIQ allows it with a prominent link back, and Mapbox's free tier allows it, with a Commercial Application License for some use cases. MapTiler, Stadia Maps and OpenCage limit their free plans to non-commercial use or testing.