Google Maps Platform: Complete APIs, Places & Routes Guide
Google Maps Platform is Google's developer platform for building maps, place discovery, address search, routing, geocoding and other location-based functionality into websites and applications. It is different from simply using the consumer Google Maps app. This guide forms part of our wider Google playbook and connects closely with Google Cloud Console for projects, credentials, billing and quota management.
What Is Google Maps Platform?
Google Maps Platform provides developer services for embedding geographic experiences, finding places, converting addresses, calculating routes and building location-aware applications.
Build Map Experiences
Add interactive maps, markers, map styling and location-based interfaces to websites and applications.
Work With Places
Search for businesses and locations, provide autocomplete and retrieve specific information about recognised places.
Calculate Journeys
Calculate routes, travel durations and route matrices for delivery, mobility, field-service and location-based applications.
Google Maps vs Google Maps Platform
The ordinary Maps product helps people navigate and discover places. Maps Platform lets developers build location functionality into their own products.
Google Maps
The consumer product is designed for people who want to find places, navigate, explore areas and obtain journey information directly through Google's own interface.
- Search for places
- View businesses
- Get directions
- Explore areas
- Navigate journeys
Google Maps Platform
The developer platform gives websites and applications programmatic access to selected Maps, Places, Routes and geospatial functionality.
- Build custom map interfaces
- Add address autocomplete
- Retrieve Place Details
- Calculate routes
- Geocode addresses
- Create location-powered products
Four Core APIs to Understand First
Maps Platform includes many products, but these four services cover a large share of common website and application location workflows.
Maps JavaScript API
Create interactive web maps, markers, custom map experiences, Places-powered features and supported 2D or 3D interfaces.
Places API (New)
Search for places, retrieve detailed place information and power location autocomplete and discovery experiences.
Routes API
Calculate a route between locations or compare distances and journey times between multiple origins and destinations.
Geocoding API
Convert addresses into coordinates and convert geographic coordinates or Place IDs back into human-readable addresses.
The Typical Maps Platform Setup Workflow
Maps Platform is normally configured through a Google Cloud project with the required APIs, authentication, billing and usage controls.
Create Project
Use a dedicated or appropriate existing Google Cloud project.
Enable Billing
Link the project to the required Cloud Billing account.
Enable APIs
Enable only the Maps Platform services the application needs.
Create Credentials
Generate the appropriate API key or other supported authentication.
Restrict Credentials
Limit where the key can be used and which APIs it may call.
Monitor Usage
Watch API requests, cost, errors, quotas and application behaviour.
Need the Cloud Infrastructure Layer?
Our Google Cloud Console guide covers projects, API enablement, credentials, IAM, billing, quotas and logs in more depth.
Build an Interactive Map Rather Than a Static Location Box
The Maps JavaScript API is designed for richer web applications where the map needs custom behaviour, styling, data or interaction.
Maps Become Part of the Application
The JavaScript API lets developers control the map interface and integrate additional Maps Platform capabilities around it.
Current Maps JavaScript capabilities include interactive 2D and 3D experiences, Advanced Markers, custom data, Places integration and cloud-based map styling.
A map can therefore become part of a store locator, property platform, delivery system or location-search interface rather than simply displaying a single pin.
Maps Embed API vs Maps JavaScript API
A business website that only needs to show a location does not automatically need a custom JavaScript Maps implementation.
Search, Discover and Retrieve Information About Places
Places API is the location-data layer behind many search, autocomplete and business-discovery experiences.
Autocomplete
Provide place and query predictions as a user types an address, business name or location-related search.
Text Search
Search for places using a natural text query when the application knows what the user wants but not the exact Place ID.
Nearby Search
Find matching places within a defined geographic area using supported place types and search parameters.
Place Details
Retrieve selected information for a specific recognised place using its Place ID.
Autocomplete → Place ID → Place Details
Place IDs create a cleaner application workflow than repeatedly trying to match unrestricted free-text addresses.
User Types
The user begins entering an address, business or destination.
Autocomplete Predicts
The application presents supported matching place predictions.
User Selects Place
The chosen result provides a recognised Google Place ID.
Retrieve Details
Use that identifier in Place Details or other compatible Maps Platform workflows.
Use a Place Identifier When the Application Needs a Recognised Place
A Place ID uniquely identifies a place within Google's Places and Maps ecosystem and can be passed between compatible APIs.
Stable Application Reference
Use the Place ID as the recognised location identifier rather than treating a human-entered address string as the only identity.
Retrieve Details
The Place ID can be used to request selected information about the recognised location through compatible APIs.
Use Across Workflows
Place IDs can participate in geocoding, route and other supported Maps Platform operations.
Request the Data You Need — Not Every Available Place Field
Places API (New) requires field masks for applicable requests, and requested fields can influence the SKU and therefore cost.
Poor Production Habit
Requesting every available place field simply because it is convenient can return unnecessary data and can trigger a more expensive pricing tier than the application actually needs.
FieldMask: *
Better Field Selection
Define the minimum useful fields for the product experience and request additional information only when it is genuinely required.
displayName
formattedAddress
location
Field selection is both a response-design decision and a cost-control decision.
New Projects Should Evaluate Places API (New), Not Start With Legacy Tutorials
Google now distinguishes the current Places API (New) from the older legacy Places service. Google also keeps separate migration guidance for applications that already rely on the legacy implementation.
A legacy application does not necessarily need an immediate blind rewrite, but new development should not begin simply by copying an old tutorial that assumes legacy endpoints and request patterns.
Places API Is Expanding Beyond Raw Location Fields
Selected Places API experiences now include AI-generated place or area summaries for supported locations and use cases.
Traditional Place Data
Applications can request structured information such as name, address, coordinates and other eligible place fields.
Place Summaries
Supported Places API functionality can provide AI-generated high-level descriptions for eligible places.
Area Summaries
Google also provides supported AI-generated summaries for certain area-level location use cases.
Compute One Route or Compare Many Origin–Destination Pairs
Routes API separates ordinary route calculation from matrix calculations across multiple origins and destinations.
Compute Routes
Use Compute Routes when the application needs an appropriate route between an origin and destination.
Warehouse
↓
Customer
↓
route
distance
duration
polyline
Depending on the request, applications can use supported options involving travel mode, traffic, alternatives, toll-related information, feature avoidance and waypoint behaviour.
Compute Route Matrix
Use a route matrix when you need distances or travel times across several origins and destinations.
3 warehouses
×
20 destinations
↓
route matrix
↓
compare duration / distance
This can support dispatching, delivery allocation and other operational comparisons without pretending that the API is automatically a complete fleet-optimisation system.
Directions API and Distance Matrix API Are Legacy Services
Google now places the older Directions API and Distance Matrix API in legacy mode and provides migration guidance towards Routes API equivalents.
For new development, evaluate Compute Routes and Compute Route Matrix rather than beginning with an old Directions or Distance Matrix tutorial.
Route Matrix Usage Grows by Origins × Destinations
Compute Route Matrix pricing and capacity are based on matrix elements. If you request two origins against three destinations, the matrix contains six origin–destination elements.
This is important when designing large allocation systems because increasing both sides of the matrix can increase billable usage far more quickly than the raw number of API requests suggests.
Address → Coordinates and Coordinates → Address
Geocoding converts location representations. It should not be confused with searching Google's database for nearby businesses or broad place discovery.
Forward Geocoding
Convert a human-readable address into geographic coordinates and other supported geocoding information.
10 Downing Street, London
↓
latitude
longitude
Place ID
Useful when an application receives an address but needs coordinates for map positioning or further location calculations.
Reverse Geocoding
Convert coordinates or a Place ID into a human-readable address.
51.5034, -0.1276
↓
human-readable address
Useful for pickup locations, map selections and applications that begin with geographic coordinates rather than an entered address.
Geocoding Is Not the Same as Places Search
Choosing an API by the business question produces cleaner implementation than trying to use one endpoint for every location task.
“I Have an Address”
Use geocoding when the task is primarily to convert a known address into coordinates or related geographic information.
“I Need to Find a Business”
Use Places search when the task is to discover recognised places matching a query or geographic condition.
“I Know the Place ID”
Use Place Details or another compatible Place-ID workflow when the application already knows the recognised place.
Browser Keys and Server Keys Need Different Restrictions
Google recommends restricting Maps Platform API keys by both the application environment and the APIs the credential is allowed to call.
Browser / Website Key
A browser-facing implementation can use suitable website restrictions so the key is accepted only from authorised web origins.
Application restriction:
approved websites
+
API restriction:
Maps JavaScript API
The key may still be visible in browser-side implementation, which is why correct restrictions are essential.
Server-Side Key
Server-side web-service requests should use suitable server restrictions, with Google recommending IP-address restrictions for API-key-based server applications.
Application restriction:
authorised server IP
+
API restriction:
Places API / Routes API
Avoid trying to use one key across browser, mobile and server environments when those environments require different restriction types.
Do Not Use One Unrestricted Google Maps API Key Everywhere
Restrict each production key to its intended application environment and the specific APIs or SDKs it needs. If different application types require different restriction methods, use separate credentials rather than weakening one shared key.
If a key is exposed or abused, rotate it carefully, confirm that the replacement works and remove the compromised credential.
Understand the SKU Behind the Request
Current Google Maps Platform pricing is based on pay-as-you-go billable events, with different services and feature levels mapped to different SKUs and usage tiers.
API Operation
Your application loads a map, performs a search, gets place data or computes a route.
SKU
The operation and requested feature level map to a specific billable SKU.
Billable Event
The Maps Platform pricing model counts eligible requests, loads or elements according to that SKU.
Usage Tier
Current pricing varies with the service, SKU and monthly usage volume.
Do Not Base 2026 Cost Planning on the Old $200 Monthly Credit Model
Google changed Maps Platform pricing and free-usage arrangements in 2025. Use the current Maps Platform SKU pricing table and your Cloud Billing data instead of copying cost assumptions from older tutorials.
Control Usage Before the Monthly Bill Arrives
Good Maps Platform cost management starts with API design, key security and usage monitoring rather than relying on billing alerts alone.
Use Precise Field Masks
Request only the Places information required by the interface instead of using expensive broad field selections.
Restrict API Keys
Prevent unintended third parties from using your credential and generating billable Maps Platform traffic.
Set Appropriate Quotas
Use service quotas to create operational limits that reflect expected application traffic.
Use Budgets & Alerts
Configure Cloud Billing monitoring so unusual spend is surfaced before the end of the billing period.
Avoid Duplicate Requests
Do not repeatedly call a paid service simply because the front end was implemented inefficiently.
Understand Feature Pricing
Some richer data fields and route features can map to higher-value SKUs than basic requests.
Monitor API Usage
Track which APIs and operations are generating traffic rather than looking only at one total Cloud bill.
Respect Caching Rules
Do not assume Maps Platform data can be stored indefinitely merely to reduce requests. Follow the service's applicable caching and licence rules.
Billing and Quota Are Different Controls
An active billing account means eligible usage can be charged. It does not mean the API has unlimited capacity.
Billing
Determines how eligible Google Maps Platform usage is charged to the linked Cloud Billing account.
Quota
Controls service consumption and request volume according to the API's quota model and project settings.
Capacity Planning
Check the live quota documentation for the exact API and design traffic, retry and scaling behaviour around the limits that apply to your project.
Maps JavaScript Drawing Library Is No Longer Available
Google deprecated the Drawing Library in August 2025 and removed support in May 2026. Applications that relied on the old library for drawing markers, polygons, polylines, rectangles or circles need an alternative approach.
This matters because older tutorials can still tell developers to load the drawing library even though that implementation is no longer supported.
Prefer Advanced Markers for New Maps JavaScript Work
Google's older Marker class is deprecated. Current Maps JavaScript development should evaluate AdvancedMarkerElement instead.
Legacy Marker
The older Marker class remains visible in many tutorials but is deprecated for new development.
AdvancedMarkerElement
Google's modern marker implementation supports richer styling and current Maps JavaScript development patterns.
Check Requirements
Review the current Advanced Markers documentation and map-ID requirements rather than translating old Marker code one line at a time.
EEA Billing Accounts Can Have Different Maps Platform Conditions
Google introduced EEA-specific Maps Platform terms effective 8 July 2025, and service functionality can vary by region.
Check the Billing Location Before Reusing Old Implementation Advice
If a Maps Platform project is linked to a billing account with an EEA billing address, review Google's current EEA terms and the service-specific adjustments relevant to that project.
This is particularly important for organisations building location experiences across several countries or copying an implementation designed under a different regional contract.
This section is a platform reminder rather than legal advice; the applicable Google Maps Platform agreement remains the controlling source.
Six Useful Google Maps Platform Application Patterns
The best API choice becomes clearer when you start from the business workflow rather than from the service name.
Store Locator
Help users discover branches and inspect relevant information on an interactive map.
Address Autocomplete
Replace uncontrolled address entry with assisted place selection.
Delivery Estimator
Calculate route information before applying your own commercial delivery rules.
Multi-Depot Assignment
Compare several starting points against multiple customer destinations.
Service-Area Checker
Convert a customer's address into geographic information and apply your own service-area logic.
Local Business Discovery
Find relevant recognised places around a user-selected geographic area.
Maps Platform vs Google Business Profile
Businesses often confuse these because both involve Maps, but they serve different purposes.
Google Maps Platform
A developer platform used to build custom map, place, route, geocoding and location-data functionality into your own website or application.
- Developer APIs
- API keys
- Billing
- Places data
- Routes
- Application logic
Google Business Profile
A business-management product used to manage an eligible organisation's presence across Google Search and Maps.
- Business information
- Categories
- Hours
- Reviews
- Photos
- Local visibility
See our Google Business Profile guide.
Measure What Users Do Around the Map Experience
Maps Platform builds the geographic functionality. Analytics and tagging tools can measure how people interact with the wider website or application.
Maps Platform
Build the location interface and retrieve the Maps Platform data required by the product.
Google Tag Manager
Use Google Tag Manager to implement appropriate measurement events around website interactions.
Google Analytics
Use Google Analytics to analyse measured interactions and business outcomes.
Location Data Can Become One Input to a Wider AI Application
Maps Platform provides structured location functionality. Gemini can provide a separate reasoning or conversational layer around your own controlled application.
Maps Data
Use Places, Routes or geocoding to retrieve the geographic information your application actually needs.
Application Logic
Validate and process that information using your own business rules and permission model.
Gemini Layer
For AI application development, continue with our Google AI Studio and Google Gemini guides.
Common Google Maps Platform Mistakes
Most Maps Platform problems come from old tutorials, insecure credentials, wrong service selection or poor understanding of billing and field usage.
Leaving API Keys Unrestricted
Production keys should be limited to the intended platform and permitted Maps APIs.
Using One Key Everywhere
Browser and server environments often require different application restrictions, so separate keys can be safer and clearer.
Requesting Every Place Field
Broad field masks can return unnecessary information and may move the request into a higher-cost Places SKU.
Starting With Legacy APIs
New development should not automatically begin with old Places, Directions or Distance Matrix tutorials.
Using the Removed Drawing Library
The Maps JavaScript Drawing Library became unavailable in May 2026.
Building New Code Around Legacy Marker
Evaluate AdvancedMarkerElement rather than beginning a new Maps JavaScript implementation around the deprecated Marker class.
Using Old Pricing Advice
Maps Platform pricing has changed. Check the live SKU table rather than assuming historic monthly-credit rules still apply.
Using Geocoding as Place Search
Geocoding converts location representations; Places handles discovery and recognised place information.
Ignoring EEA Terms
Projects linked to EEA billing accounts should review Google's current regional Maps Platform requirements and functionality.
Common Questions About Google Maps Platform
Quick answers covering Maps APIs, Places, Routes, Geocoding, API keys, billing and developer setup.
01 What is Google Maps Platform?
Google Maps Platform is Google's developer platform for adding maps, place search, location information, routing, geocoding and other geographic functionality to websites and applications.
02 Is Google Maps Platform the same as Google Maps?
No. Google Maps is primarily a consumer product for finding places and navigating. Maps Platform provides APIs and SDKs for developers building their own location-powered products.
03 What is the Maps JavaScript API?
The Maps JavaScript API lets developers create interactive web maps and add features such as Advanced Markers, Places integration, custom data and cloud-based map styling.
04 What is Places API?
Places API provides place discovery and information through capabilities such as Autocomplete, Text Search, Nearby Search and Place Details.
05 What is a Google Place ID?
A Place ID is an identifier for a recognised place in Google's Places and Maps ecosystem. It can be used with compatible APIs such as Place Details and geocoding workflows.
06 What is a Places field mask?
A field mask specifies which Place data fields a request should return. Places API (New) requires field selection for applicable methods, and the fields requested can influence the billed SKU.
07 What is the Routes API?
Routes API provides Compute Routes for calculating an appropriate route between locations and Compute Route Matrix for comparing distances and journey times across multiple origins and destinations.
08 Are Directions API and Distance Matrix API still current?
Google places both services in legacy mode. New development should evaluate Routes API, with Compute Routes replacing many Directions use cases and Compute Route Matrix replacing many Distance Matrix workflows.
09 What does the Geocoding API do?
Geocoding converts human-readable addresses into geographic coordinates. Reverse geocoding converts coordinates or supported Place IDs into human-readable address information.
10 Should Google Maps API keys be restricted?
Yes. Google recommends using application restrictions and API restrictions. For example, website keys can use approved website restrictions, while server-side keys commonly use authorised IP-address restrictions.
11 Is Google Maps Platform free?
Maps Platform uses a pay-as-you-go model for its core services, with service-specific free usage caps and volume pricing depending on the SKU. Some individual products, such as eligible Maps Embed API use, can have different pricing arrangements. Always check the live pricing table.
12 Is Google Maps Platform the same as Google Business Profile?
No. Maps Platform is a developer API platform. Google Business Profile is used to manage an eligible business's presence on Google Search and Maps. See our Google Business Profile guide.
Continue Through the Google Ecosystem
Connect Maps Platform with Google's Cloud, local business, analytics and AI products.
Choose the Location Service First — Then Build the Map Experience
Google Maps Platform works best when each service has a defined job. Use Maps JavaScript API when the website needs a genuinely interactive map rather than a simple embed. Use Places API when users need to search for recognised locations, obtain autocomplete predictions or retrieve selected Place Details. Use Routes API for route and matrix calculations, and use Geocoding when the problem is converting between addresses, coordinates and Place IDs. Restrict every API key, request only the Places fields the product needs, understand the SKU behind each billable operation, monitor quota and cost, and avoid building new applications from legacy Directions, Distance Matrix, Places or Drawing Library tutorials. A successful location product is not the one with the most Google APIs enabled — it is the one that uses the smallest correct set of services securely and predictably.
