Back to Blog

Google Places API Pricing 2026: Free Tier, Costs and Calculator

Ilyas Yıldırım
14 min read

Google Places API (New) bills each request at a price set by the endpoint and by the most expensive field you ask for. Text Search with phone and website fields is billed as Enterprise: $35 per 1,000 requests after 1,000 free requests a month. One request returns up to 20 places, so a full page costs about $1.75 per 1,000 places before volume discounts.

This guide uses Google's global price list, which Google last updated on November 17, 2026. We checked it on November 20, 2026. Prices and terms can differ by region, and the European Economic Area has its own terms. Confirm the figures on the official Google Maps Platform pricing page before you approve a budget.

The short version

Three things set the bill:

  1. The endpoint. Place Details returns data about one known place. Text Search finds places that match a text query. Nearby Search finds places around a point.
  2. The field mask. Every request must list the fields it wants. The most expensive field sets the SKU for the whole request.
  3. Monthly volume. Each SKU has a free monthly cap. Above it, Google bills per 1,000 requests in graduated bands, and the rate falls above 100,000 requests a month.

Counting requests alone is not enough. A search that returns only place IDs is free. The same search with phone numbers costs $35 per 1,000 requests.

Places API cost calculator

Pick the endpoint and the data you need, then enter how many places you want a month. The calculator applies the free cap and every volume band, then prices the same volume on BasedOnBusiness from our current plans.

Google Places API cost calculator

Adds phone, website, rating, review count and opening hours.

Up to 1,000,000 places.

A search page returns up to 20 places, and one query stops at 60. Overlapping searches return places you already have, so the real number is often lower.

Billable requests
500 (500 free)
Google bill per month
$0
Cost per 1,000 places
$0
Email addresses
Not available. The Places API has no email field.

The same 10,000 places on BasedOnB

Solo plan: $19 a month

$1.90 per 1,000 places. Includes emails published on the businesses' websites, when we find them.

Global pay-as-you-go prices from Google's price list, checked on November 20, 2026. Assumes no other use of this SKU on your billing account. Taxes, regional terms and subscription plans are not included.

The estimate is a best case. It assumes every request returns new places and that nothing else on your billing account uses the same SKU. Retries, test traffic and scheduled refreshes add requests.

Google Places API prices checked on November 20, 2026

Prices are in US dollars per 1,000 billable events, after the free monthly cap. Billing is graduated: each rate applies only to the requests inside its band. "To 100k" covers the requests after the free cap up to 100,000. The next columns cover 100,001 to 500,000, 500,001 to 1,000,000, 1,000,001 to 5,000,000 and everything above.

Place Details (New)

SKUFree a monthTo 100kTo 500kTo 1MTo 5MOver 5M
Essentials (IDs Only)Unlimited$0$0$0$0$0
Essentials10,000$5$4$3$1.50$0.38
Pro5,000$17$13.60$10.20$5.10$1.28
Enterprise1,000$20$16$12$6$1.51
Enterprise + Atmosphere1,000$25$20$15$7.50$2.28

Text Search (New)

SKUFree a monthTo 100kTo 500kTo 1MTo 5MOver 5M
Essentials (IDs Only)Unlimited$0$0$0$0$0
Pro5,000$32$25.60$19.20$9.60$2.40
Enterprise1,000$35$28$21$10.50$2.63
Enterprise + Atmosphere1,000$40$32$24$12$3.40

Nearby Search (New)

SKUFree a monthTo 100kTo 500kTo 1MTo 5MOver 5M
Pro5,000$32$25.60$19.20$9.60$2.40
Enterprise1,000$35$28$21$10.50$2.63
Enterprise + Atmosphere1,000$40$32$24$12$3.40

Google adds up usage across all projects on the same billing account. A second project does not create a second free allowance.

From requests to places: cost per 1,000 places

Google bills requests, but a lead list is counted in places. The Text Search (New) documentation sets two limits that connect them:

  • One page returns up to 20 places. The next page is a new request with the nextPageToken, and it is billed again.
  • One query returns at most 60 places across all its pages.

With full pages, the first paid band works out like this:

ApproachCost per 1,000 places
Text Search Pro (name, address)$1.60
Text Search Enterprise (adds phone, website, rating)$1.75
Text Search Enterprise + Atmosphere (adds reviews)$2.00
Text Search IDs only, then Place Details Pro for each place$17
Text Search IDs only, then Place Details Enterprise for each place$20

Two lessons follow. First, asking for contact fields in the search itself is more than ten times cheaper per place than a free ID search followed by a Details call for each result. Second, full pages are the best case. The 60-result cap means a whole city needs many smaller searches, for example one per neighborhood or grid cell. Those areas overlap, so a share of every page repeats places you already have, and the real cost per new place goes up.

Free usage: caps and the $300 credit

Every SKU except the IDs-only ones has a free monthly cap: 10,000 requests for Place Details Essentials, 5,000 for the Pro SKUs and 1,000 for the Enterprise SKUs. The IDs-only SKUs have no cap and no charge.

For a small project, the caps go a long way. At 20 places per request, the 1,000 free Text Search Enterprise requests cover up to about 20,000 places a month with phone and website. Google's pricing page also offers new customers a $300 credit.

Subscription plans

Google also sells monthly subscription plans as an alternative to pay-as-you-go. Each plan covers a fixed list of products and a monthly number of calls:

PlanPrice a monthCalls a monthPlaces API search and details SKUs included
Starter$10050,000None (Geocoding and Dynamic Maps)
Essentials$275100,000Place Details Essentials
Pro$1,200250,000Adds Text Search Pro, Nearby Search Pro and Place Details Pro
EnterpriseCustomCustomAdds the Enterprise and Enterprise + Atmosphere SKUs

Phone numbers, websites and ratings are Enterprise fields. A search that asks for them is therefore not covered by Starter, Essentials or Pro. Google says usage above a plan's calls is billed at pay-as-you-go rates.

Fields choose the SKU

The official place data field table maps every property to a SKU for Place Details, Text Search and Nearby Search. The mapping is endpoint-specific. A field can have one tier in Place Details and another in Search.

Useful examples make the rule clearer:

  • id and name qualify for IDs-only billing in Place Details and Text Search. Here, name is the resource name such as places/PLACE_ID, not the readable business name.
  • displayName gives the readable place name. For Text Search and Nearby Search, it triggers Pro.
  • formattedAddress is also Pro for Text Search and Nearby Search. In Place Details it is Essentials.
  • nationalPhoneNumber, internationalPhoneNumber, websiteUri, rating, userRatingCount and opening hours trigger Enterprise.
  • reviews triggers Enterprise + Atmosphere.

Suppose a Text Search request asks for places.id, places.displayName and places.rating. The ID is low tier, the display name is Pro and the rating is Enterprise. The request is billed as Text Search Enterprise because Enterprise is the highest tier present.

Removing rating leaves the same request at Text Search Pro. Removing displayName as well and asking only for IDs can qualify it for Text Search Essentials (IDs Only). The response contains less, but its billing is very different.

A field mask is a budget control

Places API (New) requires a response field mask. You can send it with the X-Goog-FieldMask header or a supported fields parameter. The field-mask guide recommends naming only the data your application needs.

For Text Search and Nearby Search, fields sit below the top-level places array. An IDs-only mask can look like this:

X-Goog-FieldMask: places.id,places.name

A search screen that needs a readable name and address might use:

X-Goog-FieldMask: places.id,places.displayName,places.formattedAddress

That mask reaches Pro for Text Search and Nearby Search. If the same response also needs phone and website, the mask becomes Enterprise:

X-Goog-FieldMask: places.id,places.displayName,places.formattedAddress,places.nationalPhoneNumber,places.websiteUri

Place Details returns one Place object, so its paths do not start with places.:

X-Goog-FieldMask: id,displayName,formattedAddress

Do not put spaces between field paths. Also avoid * in production. A wildcard asks for every field, including expensive ones the screen may never show, and it makes responses larger and slower. Use it briefly to inspect a development response, then replace it with an explicit list.

Worked examples

Each example assumes no other monthly usage of the same SKU and uses the prices above.

10,000 Text Search Pro requests

The free cap is 5,000, so 5,000 requests are billed.

(10,000 - 5,000) × $32 / 1,000 = $160

10,000 Text Search Enterprise requests

The free cap is 1,000, so 9,000 requests are billed.

(10,000 - 1,000) × $35 / 1,000 = $315

The request count is the same, but the Enterprise fields add $155.

200,000 Text Search Enterprise requests

This volume crosses into the second band, so two rates apply.

(100,000 - 1,000) × $35 / 1,000 = $3,465
(200,000 - 100,000) × $28 / 1,000 = $2,800
Total = $6,265

50,000 places with phone and website

With Text Search Enterprise and full pages of 20, 50,000 places need 2,500 requests.

(2,500 - 1,000) × $35 / 1,000 = $52.50

The same 50,000 places through free ID searches plus one Place Details Enterprise call per place cost far more:

(50,000 - 1,000) × $20 / 1,000 = $980

Build a realistic monthly forecast

Start with the product flow rather than a price table. Draw each user action and count every endpoint it can trigger.

Use this checklist:

  1. List every Places endpoint in the flow.
  2. Write the exact field mask beside each endpoint.
  3. Find the highest SKU in each mask.
  4. Estimate monthly requests per SKU, including background jobs, retries and extra pages.
  5. Subtract that SKU's free cap once.
  6. Apply every volume band above 100,000 requests, not only the first rate.
  7. Set Cloud Billing budgets and alerts, then compare the first invoice with the model.

Review masks when a feature changes. Adding a rating to a search card looks like a small interface edit, but it moves every request for that card from Pro to Enterprise.

Can you store Places API data?

This question matters as much as the price. Google's Places API policies, updated on November 9, 2026, point to section 3.2.3 of the Google Maps Platform terms. In short, you may cache or store Google Maps Content only where the Service Specific Terms allow it, and you may not export it for use outside the Services. Google's own examples include not to "copy and save business names, addresses, or user reviews."

Place IDs are the main exception: Google says you can store them indefinitely and fetch fresh details when a user interacts with a place. Google also notes that its support engineers cannot give legal advice, so read the terms for your billing region, or ask counsel, before you plan a stored list on the API.

Places API or a business-data export tool?

The right choice follows the job.

Use the Places API when Google data is a live feature of your product: a store locator, place autocomplete or current opening hours shown to a user. At low volume it can also be the cheapest option, because the free caps cover a lot of light use.

Use an export tool when the result is a list you keep: a spreadsheet for market research, a CRM import or an outreach campaign. The calculator above prices the same volume on BasedOnBusiness from our current plans. The differences go beyond price:

  • Emails. The Places API has no email field. BasedOnBusiness reads the business websites and adds emails published there when it finds them.
  • No grid to build. You pick a category and a city, and BasedOnBusiness splits the area into searches itself. You do not code around the 60-result cap.
  • No code. Export to CSV or Excel, or run searches from the REST API or through MCP.

The source, allowed use and freshness of any dataset still deserve a review. Our guides on Places API versus scraping and on whether scraping Google Maps is legal cover those questions. To compare export tools with each other, see the Google Maps scraper pricing comparison.

FAQ

How much does the Google Places API cost?

It depends on the SKU. In Google's global price list checked on November 20, 2026, Text Search Pro costs $32 and Text Search Enterprise $35 per 1,000 requests after 5,000 and 1,000 free monthly requests. Place Details costs $5 to $25 per 1,000 requests. Lower rates apply above 100,000 requests a month.

Is the Google Places API free?

Partly. IDs-only Text Search and Place Details requests are free with no cap. Other SKUs include 1,000, 5,000 or 10,000 free requests a month, and Google's pricing page offers new customers a $300 credit. Every request above the free cap is billed.

How much does the Places API cost per 1,000 places?

Text Search returns up to 20 places per request, so Text Search Enterprise at $35 per 1,000 requests works out to about $1.75 per 1,000 places when every page is full. Calling Place Details Enterprise for each place costs $20 per 1,000 places. Overlapping searches raise the real figure.

How many results does a Text Search request return?

Up to 20 places per page, and at most 60 across all pages of one query, according to Google's Text Search (New) documentation. Each further page is a new request, and each request is billed.

Do field masks change the price of a Places API request?

Yes. A request is billed at the highest SKU tier triggered by any requested field. Phone, website, rating, review count and opening hours move a search to Enterprise. Reviews move it to Enterprise + Atmosphere.

Does the Places API return email addresses?

No. The Places API has no email field. Its contact data stops at phone numbers and website addresses, which are Enterprise fields.

Does Google offer subscription plans for the Places API?

Yes. Starter costs $100 a month for 50,000 calls, Essentials $275 for 100,000 calls and Pro $1,200 for 250,000 calls, each covering a fixed list of products. Text Search Pro is in the Pro plan. Enterprise search SKUs, which carry phone and website, are only in the custom Enterprise plan.

Can I store Places API results in a spreadsheet or CRM?

Google's Places API policies say to cache or store Google Maps Content only where the Service Specific Terms allow it, and not to export it for use outside the Services. Place IDs are exempt and can be stored indefinitely. Check the terms for your billing region before planning a stored list.

When should I use an export tool instead of the Places API?

Use the Places API for live features inside your application. An export tool fits a category-and-city list for a spreadsheet, a CRM or outreach, especially when you need email addresses or more than a few thousand places a month. Compare fields, volume, terms and the full monthly cost.

Getting started

Test a small export before you choose. Every BasedOnBusiness account gets 30 export credits a month with no card, enough to compare a real list with your API estimate. Create your account and run your first search.

Keep reading