Skip to content
Plans from $19/month

Is Google Places API Free? 2026 Free Tier Limits & Real Costs

Tool ComparisonsBy LeadOutreach Editorial Team· 8 min read· Updated
Is Google Places API Free? 2026 Free Tier Limits & Real Costs

Key takeaways

  • There is no single Places API free tier. Each SKU has its own free monthly usage: the IDs-only Essentials tier is unlimited, Pro includes 5,000 free requests a month and Enterprise 1,000, as shown on Google's price list.
  • A billing account must be enabled on the project even if you never exceed the free usage. Free means no charge, not no card.
  • The fields in your field mask decide which tier you are billed at. Asking for a phone number or website moves a request from Pro to Enterprise.
  • Text Search returns at most 20 places per request and 60 per query, so 1,000 free Enterprise requests are at most 20,000 place records a month before duplicates.

The Google Places API free tier is not one allowance but a free monthly amount per SKU. Google's price list lists unlimited IDs-only requests for Text Search and Place Details, not a Nearby Search IDs-only tier. Text Search and Nearby Search Pro each include 5,000 free Pro requests, and 1,000 free Enterprise and 1,000 free Enterprise + Atmosphere requests a month; beyond that you pay $32, $35 and $40 per 1,000 requests at the entry band. A billing account with a payment method must be attached to the project even if you never exceed the free usage.

The endpoint and fields together determine the SKU; Text Search, Nearby Search and Place Details do not share one universal allowance. Name and address are Pro fields; phone number and website are Enterprise. This guide covers the free limits per SKU, how the field mask changes what you are billed, what 1,000 free Enterprise requests actually buy for a lead list, and when a hosted tool is the cheaper route.

What is the Google Places API free limit per month?

For Text Search and Nearby Search, the global monthly no-cost caps are 5,000 Pro requests and 1,000 Enterprise requests per SKU. Text Search IDs-only requests have no usage charge. Place Details is a separate lookup with its own caps and rates; do not apply the search table to every Places API call.

For example, 1,200 Text Search Enterprise requests in a month leave 200 above its 1,000-request free cap. At the entry rate of $35 per 1,000, that is $7 before taxes or other API usage. Each fetched page is a request, not each returned business. These are global pay-as-you-go figures checked 8 November 2026; regional or subscription pricing can differ.

Free usage is not a stop switch. Monitor usage by SKU and use request quotas as a control; a billing budget alert alone does not stop requests. See the official usage and billing guide.

Does using Google Places API cost money?

Google Places API has usage-based billing with no-cost allowances for particular SKUs; it is not an unlimited free business-data service. Billing must be enabled, and the endpoint, requested fields and volume determine the charge. Check the current official pricing list for the SKU you will actually call before running a batch.

Using the consumer Google Maps app to look up a place is a different activity from sending paid API requests. A free allowance is also different from a billing cap: review quotas, usage and budget settings rather than assuming that no-cost usage prevents all charges. The table below separates the request types.

Is Google Places API free or not? 2026 limits by SKU

Is the Google Places API free or not? Yes, Google gives every developer a monthly free tier allowance per SKU: Essentials (Place IDs only) is unlimited free, Pro includes 5,000 free monthly requests, and Enterprise includes 1,000 free requests. However, Google requires an active billing account with a credit card attached to your Google Cloud project before you can make any API calls.

TierFree usage per monthPrice per 1,000 requests after thatExample fields
Text Search IDs onlyUnlimitedNo chargePlace ID
Pro5,000 requests$32.00Name, address, location, business status, types
Enterprise1,000 requests$35.00Phone, website, rating, review count, opening hours
Enterprise + Atmosphere1,000 requests$40.00Reviews text, editorial summary, amenities

The IDs-only row applies to Text Search. Pro and Enterprise Text Search and Nearby Search figures come from Google's global price list, entry band (0 to 100,000 requests); volume discounts apply above that. Place Details has its own SKUs at different prices, including a non-IDs Essentials SKU with 10,000 free requests a month. Check Google's current price list before planning around these numbers.

The free allowances are per SKU, so using 1,000 free Enterprise Text Search requests does not consume your Pro allowance, and Nearby Search has its own set (the two endpoints are compared in Nearby Search vs Text Search). Google's usage-and-billing page also notes that the older model, a $200 monthly credit applied across SKUs, ran until February 28, 2025. If you read an article that talks about the $200 credit, it describes the previous scheme.

Do I need a billing account for the Places API free tier?

Yes. Google's usage-and-billing page states that billing must be enabled on the project and that every request needs an API key or OAuth token. Free usage is applied as a discount against a bill that would otherwise exist. In practice this means:

  • You create a Google Cloud project, attach a billing account with a payment method, and enable the Places API (New) on it.
  • Requests within the free allowance appear on the bill at no charge; requests beyond it are charged at the tier price.
  • Nothing stops you exceeding the free usage by default. A budget alert in the Cloud console warns you; it does not cut you off. To cap spending, set a daily quota on the API itself and restrict the key so it cannot be used from anywhere else.

If you would rather not attach a card at all, the API is not the route. A hosted tool with a free plan is; more on that below.

Which fields push a request from Pro to Enterprise?

Every Places API (New) request must include a field mask listing the fields you want back; the Text Search page says that omitting it returns an error. The billing page then explains the rule that matters for cost: you are billed at the highest SKU applicable to your request. Its own example is that if you select fields in both Essentials and Pro, you are billed at Pro.

The Text Search documentation lists which fields sit in which tier. A few that matter for lead lists:

TierField mask entries (Text Search)
Essentials (IDs only)places.id, places.name, places.attributions, nextPageToken
Proplaces.displayName, places.formattedAddress, places.location, places.businessStatus, places.types, places.primaryType
Enterpriseplaces.nationalPhoneNumber, places.internationalPhoneNumber, places.websiteUri, places.rating, places.userRatingCount, places.regularOpeningHours
Enterprise + Atmosphereplaces.reviews, places.editorialSummary, places.parkingOptions, places.outdoorSeating

So a request for places.displayName,places.formattedAddress is a Pro request and draws on the 5,000 free. Add places.websiteUri and the same request becomes Enterprise, drawing on the 1,000 free and costing $35 per 1,000 afterwards. Add places.reviews and it is Enterprise + Atmosphere at $40 per 1,000. Nothing else about the request changed.

Two-step pattern

One way to stretch the free usage is to run Text Search at the Pro tier to find and deduplicate businesses, then request Enterprise fields only for the ones you keep. Whether that saves anything depends on your duplicate rate and how many results you discard; test it on one query before assuming.

How many businesses can the free Places API tier return?

The Text Search page says a request returns 20 results per page by default (the pageSize parameter accepts 1 to 20) and that Text Search (New) returns a maximum of 60 results across all pages, a limit it says is subject to change. Each page is fetched with a separate request using the pageToken from the previous response. The arithmetic follows:

  • 1,000 requests times at most 20 places each is at most 20,000 place records a month at no charge, if every page is full.
  • A query that goes to all three pages uses three requests for at most 60 places, so 1,000 requests is roughly 330 fully paged queries.
  • Queries that overlap return the same businesses, and in a dense city the 60-result ceiling means one query never covers a whole trade. Both push the number of unique businesses per request down.

For many freelancers and small agencies, 1,000 Enterprise requests a month is enough to build a working list in a few cities without paying Google anything. The costs that remain are the ones the API does not include: email addresses, verification, filters and your time. The worked examples for larger lists are in Google Places API pricing for lead lists, and the reason the 60-result ceiling matters so much is explained in the Google Maps search results limit. To put a value on a list of that size before you spend the requests, the cold email ROI calculator turns your reply and close rates into expected revenue.

Try it on your own search
Run the same trade and city in a hosted tool and compare the emails, filters and export with what the free API requests return.
Start the 7-day trial

Places API free tier vs a free plan on a hosted tool

Places API free usageLeadOutreach Free plan
Card requiredYes, billing account on the projectNo
What is freePer SKU per month: unlimited IDs, 5,000 Pro requests, 1,000 Enterprise requests100 leads a month, 2 saved searches, 10 enrichment credits, standard CSV export
Phone, website, ratingEnterprise tier fieldsIncluded in every lead
Emails from the business websiteNot available from the APIEnrichment credits, with basic email checks
Filters such as No websiteBuild them yourselfBuilt in
SetupCloud project, billing, key, codeSign up and search

LeadOutreach plans above Free are Starter at $19 a month for 1,000 leads, Pro at $39 for 3,000 and Agency at $99 for 10,000; see the pricing page for current limits.

Use the API when you are building software: you want structured data on demand, you can write and maintain the code, and you are comfortable with Google's rules on how long results may be stored (check the Places API policies before building a permanent database). Use a hosted tool when the goal is a list of businesses to contact this week, especially if you need emails, which the API never returns at any tier; how a Google Maps email extractor finds them explains the website-crawl step. The wider trade-offs are in Google Places API vs a Google Maps scraper. The Free plan on LeadOutreach is small, but it needs no card and returns the fields the Enterprise tier charges for; see the pricing page for current limits.

How to stay within the free usage

  1. Create a Cloud project, enable billing, enable Places API (New), and create an API key restricted to that API.
  2. Set a daily quota on Text Search requests low enough that a runaway script cannot pass the free allowance in a day.
  3. Set a budget alert on the billing account as a second warning.
  4. Write your first request with a Pro-only field mask (places.id,places.displayName,places.formattedAddress) and one page. Confirm what appears in the billing report.
  5. Add Enterprise fields only when you need them, and deduplicate by places.id so you never spend a request on a business you already have.
  6. Follow the code walk-through in Google Places API with Python for business leads for paging, storage and error handling.

Check the billing report after the first week. Google's report shows usage by SKU, which is the quickest way to see whether a stray field has been pushing your requests into a tier you did not intend.

Sources and further reading

Start finding verified leads today

Search Google Maps by niche and city and export verified emails, phone numbers, and marketing gap audit signals to CSV or your CRM. 7-day Starter trial, then plans from $19/month.

No credit card required. Free plan of 100 leads a month stays available.

Related articles

FAQ

Frequently asked questions

The no-cost usage caps in the global pay-as-you-go price list are monthly and specific to each SKU. API request quotas are separate rate or usage controls. Budget alerts are notifications, not automatic spending caps.

Partly. Google gives each pricing tier its own free monthly usage: unlimited IDs-only Text Search requests; Text Search and Nearby Search each have 5,000 free Pro requests and 1,000 free Enterprise requests a month, as shown on Google's price list. Beyond those amounts Text Search costs $32 (Pro), $35 (Enterprise) or $40 (Enterprise + Atmosphere) per 1,000 requests at the entry band. The old $200 monthly credit ended on February 28, 2025, and a billing account must be attached to the project.

Yes. Google's usage-and-billing page states that billing must be enabled on the project, so a payment method is required even if you stay within the free usage. The free allowance is applied as a discount against your usage rather than as a separate no-card tier.

Text Search returns at most 20 places per request and a maximum of 60 results per query across pages, so 1,000 free Enterprise requests are at most 20,000 place records a month, before duplicates. Overlapping queries and the 60-result ceiling reduce the number of unique businesses in practice.

Because at least one field in your field mask belongs to the Enterprise tier. Google bills each request at the highest SKU any requested field falls into. Phone number, website, rating and review count are all Enterprise fields; remove them and the request drops to Pro.

No. The Places API does not return email addresses at any tier. To get them you need to read each business's website separately, either with your own code or with a tool that does it for you and checks the addresses it finds.