<br />

This page is updated with each product release. The changelog lists releases by
date and includes any new features, bug fixes, and significant performance
improvements.
You can also browse and filter all release notes for all products in the
[Google API Console](https://console.cloud.google.com/release-notes).

To subscribe to these release notes, add the [feed URL](https://developers.google.com/static/feeds/geocoding-api-release-notes.xml) of this page to your [RSS feed
reader](https://wikipedia.org/wiki/Comparison_of_feed_aggregators).
[![Subscribe](https://developers.google.com/static/maps/documentation/images/rss-icon.svg)](https://developers.google.com/static/feeds/geocoding-api-release-notes.xml)

See the [Overview](https://developers.google.com/maps/documentation/geocoding/release-notes/overview) documentation for information on how to get
started using the Geocoding API.

## November 02, 2026

Announcement **Experimental release of the `effort` parameter**

Announcing the [Experimental release](https://developers.google.com/maps/launch-stages.md.txt#experimental) of the
`effort` parameter for
[`GeocodeAddress`](https://developers.google.com/maps/documentation/geocoding/reference/rest/v4alpha/geocode.address/geocodeAddress.md.txt)
and
[`SearchDestinations`](https://developers.google.com/maps/documentation/geocoding/reference/rest/v4alpha/geocode.destinations/searchDestinations.md.txt).
The `effort` parameter (`LOW`, `MEDIUM`, `HIGH`) lets you control the trade-off
between response speed and address resolution accuracy for incomplete, informal,
or complex addresses. [See the
documentation](https://developers.google.com/maps/documentation/geocoding/geocoding-effort).

## October 13, 2026

Announcement **Entrance display names and Experimental parking facilities**

Announcing two updates for
[`SearchDestinations`](https://developers.google.com/maps/documentation/geocoding/reference/rest/v4/geocode.destinations/searchDestinations.md.txt):

- **Entrance display names.** The [`Entrance`](https://developers.google.com/maps/documentation/geocoding/reference/rest/v4/geocode.destinations/searchDestinations.md.txt#Entrance) object now includes a `displayName` field containing a human-readable name for the entrance (such as `"Gate B"` or `"South Entrance"`), when available. [See the documentation](https://developers.google.com/maps/documentation/geocoding/search-for-destinations.md.txt#entrances).
- **Parking facilities (Experimental).** In the [Experimental (`v4alpha`)](https://developers.google.com/maps/launch-stages.md.txt#experimental) channel, [`ParkingOptions`](https://developers.google.com/maps/documentation/geocoding/reference/rest/v4alpha/geocode.destinations/searchDestinations.md.txt#Destination.ParkingOptions) now includes a `parkingFacilities` field that returns details on individual parking lots and garages associated with the destination. [See the
  documentation](https://developers.google.com/maps/documentation/geocoding/parking-options).

## July 20, 2026

Announcement Announcing the new `addressComponents` field in the `PlaceView` of a
`Destination`. Now, the primary place, sub-destinations, containing places, and
landmarks will return address components, in addition to the postal
address.

## May 19, 2026

Announcement Announcing the [Experimental release](https://developers.google.com/maps/launch-stages.md.txt#experimental) of a new
`altitude_meters` field for [navigation
points](https://developers.google.com/maps/documentation/geocoding/reference/rest/v4alpha/geocode.destinations/searchDestinations#navigationpoint)
in the Destinations service. The `altitude_meters` field contains the altitude
of the navigation point in meters.

## April 22, 2026

Announcement **Experimental release of Street View imagery and parking information**

Announcing the [Experimental release](https://developers.google.com/maps/launch-stages.md.txt#experimental) of two
[`SearchDestinations`](https://developers.google.com/maps/documentation/geocoding/reference/rest/v4alpha/geocode.destinations/searchDestinations.md.txt)
response fields:

- **Imagery and annotations.** This field provides Street View imagery and annotations. [See the
  documentation](https://developers.google.com/maps/documentation/geocoding/imagery-annotations).
- **Parking information.** This field provides detailed parking information for destinations. [See the
  documentation](https://developers.google.com/maps/documentation/geocoding/parking-options).

## March 30, 2026

Announcement **Geocoding API v4 is now generally available.**

Announcing the [GA release](https://developers.google.com/maps/launch-stages.md.txt#ga) of the Geocoding API v4.

## February 16, 2026

Announcement **Navigation point tokens now available.**

You can now use the Destinations method of the Geocoding API v4 to allow your users
to select pickup and dropoff points, improving the consumer and driver
experience in situations like food delivery or rideshare. Use the navigation
point token from the selection to pass key this contextual information to the
[Navigation
SDK](https://developers.google.com/maps/documentation/navigation/android-sdk/routing-to-access-points#use_a_navigation_point_token)
for precise routing. [See the
documentation](https://developers.google.com/maps/documentation/geocoding/navigation-point-tokens).

## January 28, 2026

Announcement **Preview release of the `SearchDestinations` method of the Geocoding API v4.**

Announcing the [Preview](https://developers.google.com/maps/launch-stages.md.txt#preview) release of the `SearchDestinations` method of the
Geocoding API v4. This release includes these new features:

- **AI-powered summaries** to help users understand a destination. See
  [AI-powered summaries](https://developers.google.com/maps/documentation/geocoding/ai-powered-summaries.md.txt)
  for more information.

- **Relational descriptions of landmarks** . A new `relationalDescription`
  field helps users locate a destination. For example, "Around the corner from
  the Empire State Building." [See the API
  reference](https://developers.google.com/maps/documentation/geocoding/reference/rest/v4/geocode.destinations/searchDestinations#landmark).

- **Place filters** for `locationQuery`. The `placeFilter` object in
  `geocodeLocationQuery` lets you filter results by `structureType` and
  `addressability`.

- **Landmark distance details** . New fields `straightLineDistanceMeters` and
  `travelDistanceMeters` are available within landmark details to provide
  proximity information.

## August 13, 2025

Announcement **SearchDestinations method added to the Geocoding API v4 in experimental.**

Announcing the [Experimental](https://developers.google.com/maps/launch-stages.md.txt#experimental) release of the
[SearchDestinations](https://developers.google.com/maps/documentation/geocoding/reference/rest/v4alpha/geocode.destinations/searchDestinations.md.txt)
method of the Geocoding API v4. For more information, see
[Search for destinations](https://developers.google.com/maps/documentation/geocoding/search-for-destinations.md.txt).

With this release, the following experimental features are no longer supported
in the Geocoding API v3:

- Entrances
- Navigation points
- Building outlines
- Grounds

For continued use of these features, we recommend developers to use the
SearchDestinations method instead. For more information, see
[Migrate from v3 features to the SearchDestinations method](https://developers.google.com/maps/documentation/geocoding/destinations-migrate).

## May 13, 2025

Announcement **Enhancements to the building outlines and entrances Experimental release**

The [Experimental](https://developers.google.com/maps/launch-stages.md.txt#experimental) release of [Building outlines and entrances](https://developers.google.com/maps/documentation/geocoding/building-attributes) adds the following enhancements:

- Increases entrance coverage by returning all entrances on the same building as the geocoding result. In the previous release it only returned entrances that were for the geocoding result itself.
- A new response field, `entrance_tags[]`, is associated with each entrance to distinguish between entrances that are for the geocoding result and other entrances that are on the building. An entrance that has a value of `PREFERRED` in `entrance_tags[]` indicates that the entrance likely provides physical access to the geocoding result.
Announcement **Grounds Experimental release available**

Announcing the [Experimental](https://developers.google.com/maps/launch-stages.md.txt#experimental) release of [grounds](https://developers.google.com/maps/documentation/geocoding/grounds). The new `grounds` field in a Geocoding response contains a single grounds definition that, when populated, gives contextual information about the immediate territory that the geocoding result is on.

## April 30, 2025

Announcement **Geocoding API v4 is now in [Preview](https://developers.google.com/maps/launch-stages.md.txt#preview).**

Geocoding API v4 is implemented on the service infrastructure on Google Cloud which brings with it a more secure and trusted platform with enhanced security options like OAuth.

For more information and examples, see [Geocoding API v4 overview](https://developers.google.com/maps/documentation/geocoding/geocoding-v4-overview.md.txt).

## April 17, 2025

Announcement **Road name added to navigation points; Migration to new parameter and location fields required**

The new `road_name` response field contains the name of the road the navigation point is offset from. To return the `road_name` response field, and to continue receiving navigation points, you must include the following query parameter in the request:

`extra_computations=NAVIGATION_POINTS`

**Migration Notice:** Existing applications must be updated to include the `NAVIGATION_POINTS` parameter. Additionally, migrate to using `location.lat` and `location.lng` response fields instead of `location.latitude` and `location.longitude`. Future requests without this parameter will not return navigation points, and the older location fields will be removed. For more information, see [Navigation points](https://developers.google.com/maps/documentation/geocoding/navigation-points).

Navigation points and road names are [Experimental](https://developers.google.com/maps/launch-stages.md.txt#experimental) (pre-GA) features.

## March 25, 2025

Announcement **Address descriptors released for General Availability (GA) in India**

Address descriptors include additional information that help describe a location using landmarks and areas. For more information, see [Address descriptors request and response](https://developers.google.com/maps/documentation/geocoding/address-descriptors/requests-address-descriptors).

This feature is available in all regions and is in GA for India and in the pre-GA Experimental launch stage for all other regions. The use of address descriptors in India incurs no additional cost and usage is covered by the existing [Geocoding (India) Essentials SKU](https://developers.google.com/maps/billing-and-pricing/pricing-india.md.txt#places-pricing). For more information, see [coverage details](https://developers.google.com/maps/documentation/geocoding/address-descriptors/coverage).

## December 11, 2024

Feature Experimental navigation points added. Navigation points are a list of points that are useful for navigating to a place. For more information, see [navigation points](https://developers.google.com/maps/documentation/geocoding/requests-geocoding#navigation-points).

## October 18, 2024

Feature **Address descriptors added**

New Preview address descriptors added. Address descriptors include additional information that help describe a location using landmarks and areas. For more information, see [Address descriptors request and response](https://developers.google.com/maps/documentation/geocoding/address-descriptors/requests-address-descriptors).

This feature is available in all regions. For more information, see [coverage details](https://developers.google.com/maps/documentation/geocoding/address-descriptors/coverage).