Google Places API Free Tier Limits in 2026

The Google Places API free tier sounds like a gift. A monthly credit applied automatically, no card friction for small projects, and access to the same dataset that powers Google Maps. Then you do the SKU math, and the picture changes. The credit is real, but it gets consumed faster than most teams expect — especially sales teams that need contact data, reviews, and photos for every record they pull.

This guide walks through what the free tier actually includes in 2026, which SKUs eat the credit fastest, how field masking can stretch it, and where it stops making sense for a prospecting workflow. We will keep the numbers directional, because Google adjusts pricing tiers and SKU definitions periodically — what matters is the shape of the bill, not a frozen quote.

What the Google Maps Platform free tier covers

The Google Maps Platform exposes its data through several APIs: Maps JavaScript, Geocoding, Directions, Distance Matrix, Roads, and the one this article is about, Places. Places itself is split into multiple endpoints — Text Search, Nearby Search, Place Details, Autocomplete, and Place Photos — and each endpoint has its own SKUs that bill independently.

The "free tier" is not a tier in the classic sense, like a free row count on a database. It is a recurring credit applied to your billing account every month. As long as your usage across all Maps Platform APIs stays under that credit, you pay nothing. Cross it, and every additional call is billed at the published per-thousand rate for whichever SKU you hit.

To use the API at all you still need a Google Cloud billing account with a valid card on file. The credit is not a free trial that expires after ninety days — it renews monthly — but it is also not a hard cap. If you forget to set quotas and your script loops, the credit will not save you from the overage.

The $200 monthly credit

Google has published a recurring monthly credit toward Maps Platform usage for several years, commonly cited at around $200. Treat the exact figure as something to confirm in your Cloud Console before you plan anything important — Google has revised this credit and the SKUs it applies to more than once, and 2026 is no exception. What you can rely on is the structure: a fixed monthly amount, applied automatically, that offsets billable Maps Platform calls.

The credit is account-wide. If you use Maps JavaScript on a marketing site, Geocoding in a backend job, and Places in a lead tool, all three draw from the same pool. Teams who run multiple Google Maps integrations often discover their Places budget is smaller than they thought because the rest of the stack already consumed half the credit before the lead script even ran.

For a deeper breakdown of how Maps pricing compares to alternative data acquisition methods, see our Google Maps API pricing vs scraping comparison.

SKUs that consume the credit fastest

Not all Places API calls are equal. The endpoint you hit and the fields you ask for determine which SKU you are billed under, and the prices between SKUs can differ by an order of magnitude.

The cheapest calls are usually basic Text Search or Nearby Search results returning ID, name, and location. The most expensive are Place Details requests that include contact data — phone numbers, websites, opening hours — or atmosphere data like reviews and ratings. Google split Place Details into multiple SKUs precisely because contact and atmosphere fields are the most commercially valuable and the most expensive to serve.

Photos are their own SKU again, billed per photo URL fetched, and they are easy to forget. A page that shows three thumbnails per business is three SKU charges per record, every time the page loads, unless you cache aggressively.

For a sales workflow the bill almost always looks like this: a moderate number of Search calls, a much larger number of Place Details calls with the Contact Data SKU enabled, and an optional Photo bill on top. The Search portion is small. The Contact Data portion is what ends the month early.

How fast you exhaust it with 500 leads

Walk through a small but realistic example. You want 500 dentists in a metro area with name, address, phone, website, rating, and review count. Here is what the API actually does on your behalf.

First, a series of Text Search or Nearby Search calls to enumerate the 500 places. Search returns paginated results, twenty per page, so you make roughly twenty-five paginated requests. Each page is one billable Search call. So far, the spend is small.

Second, for each of the 500 places, you call Place Details to get the phone, website, and hours. That is 500 Place Details calls, and because you asked for contact fields, every one of them is billed under the Contact Data SKU, which is meaningfully more expensive than basic details. If you also requested rating and review count, you tripped the atmosphere SKU as well, which is more expensive again.

Third, if you want a logo or a header image for each lead, you make 500 Photo calls, one per business, billed under the Photo SKU.

Add it up directionally and a single 500-lead pull can consume a noticeable fraction of the monthly credit — sometimes a single-digit percentage, sometimes much more, depending on which fields you asked for and whether you cached. Run the same query four times across iteration and testing and you have spent a real chunk of the month before you have one usable export.

This is the part teams underestimate. The credit is not 500-leads-per-month worth of headroom. It is "a few hundred to a few thousand enriched records, depending on how careful you are with field selection."

Field masking — how to stretch the free credit

Google introduced field masks on the new Places API specifically because customers were paying for fields they did not use. A field mask is an explicit list of the fields you want returned, sent as a header on the request. The SKU you are billed under is determined by the most expensive field in your mask, not by the endpoint name.

The practical impact: if you only need name and address, you ask for only name and address, and you are billed under the cheapest SKU. The moment you add formattedPhoneNumber or website to your mask, the entire response gets billed under Contact Data. The moment you add rating or reviews, you move up to atmosphere.

Two rules of thumb get most of the savings. First, never request a field you are not going to display or store — you are paying for it whether you use it or not. Second, split your enrichment into stages. Pull a cheap list first, qualify it (filter by category, ZIP, name pattern), and only run the expensive Contact Data fetch on the qualified subset. Doing the expensive call on the full list is the single most common reason teams blow through the credit.

For a fuller treatment of quotas, throttling, and per-second limits that compound on top of the cost limits, see Google Maps API limits explained.

Common ways teams blow through the credit

A handful of patterns account for most overage bills.

Loose loops during development. A script that re-pulls the same 1,000 places every time you re-run it, with no cache, will torch the credit in an afternoon. Cache Place IDs locally and short-circuit lookups for IDs you already have.

Wide field masks. Asking for every field "just in case" pushes every call to the most expensive SKU, even if you only display three fields in the UI.

Photos in lists. Showing a thumbnail per result on a paginated dashboard means every page load fans out into N Photo SKU calls. Either cache the photo URLs aggressively or do not show photos in list views.

No daily quota cap. The Cloud Console lets you set per-day quotas per API. If you do not, a runaway loop can blow through the entire monthly credit in hours and start billing real money.

Multiple integrations on one billing account. The marketing site's embedded map and the backend's Geocoding job draw from the same credit your lead tool depends on. Either separate billing accounts or budget across the whole portfolio.

When the free tier is enough

The free tier works well in three scenarios. Hobby projects and prototypes that pull a few hundred records a month. Embedded maps on low-traffic sites that mostly hit cached tiles. Internal tools used by one or two people with disciplined caching.

If you are a developer building an MVP, prototyping a lookup feature, or running a quarterly research pull, the credit is genuinely useful and the SKU model rewards careful engineering. You can stay free indefinitely if you cache, mask aggressively, and keep volume modest.

When MapsLeads is cheaper than the free tier

The math flips when three things are true. You need contact data on most or all records, not just IDs and names. You run multiple searches per week, not per quarter. You want exports, deduplication, and review intelligence rather than raw API responses.

In that scenario the Contact Data SKU dominates your bill, the credit gets consumed in days, and the engineering time spent caching, retrying, and managing quotas is real money on top of the cloud spend. A flat-rate tool that bundles the search, the contact pull, the review analysis, and the export becomes both cheaper and faster.

For a side-by-side workflow comparison, MapsLeads vs Google Places API direct walks through the same 500-lead exercise on both stacks.

How MapsLeads' free trial works for sales teams

If you want to test whether a flat-rate workflow fits your team before committing, MapsLeads runs on a credit system with a free trial that lets you do a real prospecting run end-to-end — not a sandbox with fake data.

You sign up at /signup and your account is provisioned with starter credits, no card required for the trial. From the dashboard you run a real Search: pick a category and a location, and the system returns the businesses that match, the same way Google does, but with the contact, review, and photo enrichment already attached or available as add-on modules.

The credit model is straightforward. One credit covers the Base record — name, address, phone, website, category. Adding the Contact Pro module costs one extra credit and pulls deeper contact data including emails where available, decision-maker hints, and social profiles. The Reputation module costs one extra credit and analyzes reviews, sentiment, complaint patterns, and rating trajectory. The Photos module costs two extra credits and pulls the business' image set, useful for niches where visual qualification matters like restaurants, salons, or event venues.

The point of the trial is to compare on real work. Take the same query you would run against Google's API — say, 100 dentists in your city — and run it through MapsLeads. You see the Search results immediately, you decide which records justify Contact Pro and which do not, you run Reputation only on the ones that pass your filter, and you export the result as CSV for your CRM. The same exercise on Google's API would have already consumed a noticeable slice of your monthly credit, and you would still be writing the script.

Most teams use the trial credits to validate one specific list — their next outbound campaign, their territory expansion list, a competitor analysis — and they have a usable export within an hour. From there, the Pricing page lays out the monthly plans, which are predictable flat rates rather than per-SKU bills.

FAQ

Is the Google Places API free? Not exactly. There is a recurring monthly credit applied to your billing account, and usage under that credit costs nothing. A valid billing account with a card is still required, and any usage beyond the credit is billed per-thousand-calls at the SKU rate.

How much is the free credit? Google has published a monthly Maps Platform credit commonly cited around $200. Confirm the current figure in your Cloud Console — Google revises pricing tiers periodically.

How long does the credit last for a sales team? Directionally, a few hundred to a few thousand enriched records depending on which fields you request. A wide field mask on Place Details with Contact Data and Atmosphere SKUs enabled consumes the credit much faster than a basic Search-only workflow.

What is a free Places API alternative for prospecting? Tools like MapsLeads bundle Search, contact enrichment, review analysis, and exports into a flat-rate plan with a free trial that covers a real run end-to-end. The trade-off is less low-level control in exchange for predictable cost and no SKU management.

Does field masking really matter? Yes, materially. The SKU you are billed under is set by the most expensive field in your mask. Trimming unused fields is the single highest-leverage optimization on the Places API.

Can I cap my spend? Yes. Set per-API daily quotas in the Cloud Console so a runaway script cannot blow through the credit and start charging real money.

Conclusion

The Google Places API free tier is real and useful for the right workload — small volumes, careful field masking, and disciplined caching. For sales teams that need contact data on every record and run lists weekly, the Contact Data SKU eats the credit faster than the headline number suggests, and the engineering overhead of staying under it adds up.

If you want to compare the two workflows on a real list rather than a hypothetical, start a free MapsLeads trial at /signup and run the same query you would have run against Google's API. The export is yours either way.