**European Economic Area (EEA) developers**

> [!NOTE]
> If your billing address is in the European Economic Area, effective on 8 July 2025, the [Google Maps Platform EEA Terms of Service](https://cloud.google.com/terms/maps-platform/eea) will apply to your use of the Services. Functionality varies by region. [Learn more](https://developers.google.com/maps/comms/eea/faq.md.txt).

## Overview

Along with specifying the origin and destination, you can also use many of the options
available for routes to customize a route matrix. The following table lists the options
available for route matrix requests, and calls out any differences between the single-route
and matrix methods.

| Option | Description |
|---|---|
| [Travel mode](https://developers.google.com/maps/documentation/javascript/reference/directions.md.txt#TravelMode) | The mode of travel, such as drive, transit, walk, bicycling, or two-wheeled vehicle. > [!NOTE] > **Note:** Walking, bicycling, and two-wheeled vehicle routes are in beta and might sometimes be missing clear sidewalks, pedestrian paths, or bicycling paths. You must display this warning to the user for all walking, bicycling, and two-wheel routes that you display in your app. |
| [Specify how and if to include traffic data](https://developers.google.com/maps/documentation/javascript/reference/route-matrix.md.txt#ComputeRouteMatrixRequest.trafficModel) | Include traffic data for more accurate results, or exclude it for a faster response. Because the `computeRouteMatrix` processes many routes simultaneously, using the highest quality setting, `TRAFFIC_AWARE_OPTIMAL`, imposes a strict request limit on the total number of elements (origins × destinations) you can calculate in a single call. This limitation exists to prevent excessive latency. |
| [Calculate toll fees for a route matrix](https://developers.google.com/maps/documentation/javascript/routes/routes-tolls.md.txt) | When working with tolls in the `RouteMatrix`, the process is fundamentally the same as calculating tolls for a single route, but with one key difference in scope: the `computeRouteMatrix` method provides only the aggregated toll information for each complete Origin-Destination pair. Unlike the single `computeRoutes` method, which can return detailed toll information broken down by individual route legs (segments between waypoints), the route matrix response summarizes the total estimated toll cost for the entire trip between the origin and destination. You still enable toll calculation by setting `extraComputations` to `TOLLS` and defining vehicle and toll pass information by setting the origin's `routeModifiers`, but the resulting `travelAdvisory.tollInfo` applies to the full route, not its individual components. |
| [Request localized values](https://developers.google.com/maps/documentation/javascript/reference/route-matrix.md.txt#RouteMatrixItem.localizedValues) | You request localized text for your route matrix response in the same way as for a route, using a field mask. When requesting localized text for duration and distance, both the single-route and matrix methods support explicitly setting the `languageCode` and units (for example, `METRIC` or `IMPERIAL`). However, if these parameters are not set, the `computeRoutes` method attempts to infer the language and distance units directly from the origin waypoint's geographic location, whereas the `computeRouteMatrix` method defaults to English (`en-US`) for language and Metric (`METRIC`) for units, regardless of the origin's location. Therefore you must explicitly set the localization parameters when using `RouteMatrix` to override its default behavior. |
| [Available route matrix vehicle types](https://developers.google.com/maps/documentation/javascript/routes/route-matrix-vehicle-types.md.txt) | Additional options for selecting the type of vehicle for the route matrix. |
| **Additional options** | To specify additional options, such as the departure time, see [ComputeRouteMatrixRequest](https://developers.google.com/maps/documentation/javascript/reference/route-matrix.md.txt#ComputeRouteMatrixRequest). |