Map Tiles API Policies  |  Google Maps Tile API  |  Google for Developers (2023)

This document lists requirements for applications developed with the Map Tiles API. Note that use of the Map Tiles API is governed by your Agreement with Google.

Providing terms of use and privacy policy

If you develop a Map Tiles API application, you must make available the Terms of Use and a Privacy Policy with your application which meets the guidelines outlined in your Agreement with Google:

• The Terms of Use and Privacy Policy must be publicly available.
• You must explicitly state in your application's Terms of Use that by using your application, users are bound by Google’s Terms of Service.
• You must notify users in your Privacy Policy that you are using the Google Maps API(s) and incorporate by reference the Google Privacy Policy.

The recommended place to make available your Terms of Use and Privacy Policy depends upon your application's platform.

Mobile applications

If developing a mobile app it is recommended that you provide a link to the Terms of Use and Privacy Policy on your application's download page in the relevant application store and in an application settings menu.

Web applications

If developing a web application it is recommended that you provide a link to the Terms of Use and Privacy Policy in the footer of your website.

Pre-Fetching, Caching, or Storage of Content

Applications using the Map Tiles API are bound by the terms of yourAgreement with Google. Subject to the terms of your Agreement, you must notpre-fetch, index, store, or cache any Content except under the limitedconditions stated in the terms.

Specifically, applications should use Map Tiles API for map visualizations.You may not use Map Tiles API for any non-visualization use cases, such as:

• Image analysis
• Machine interpretation
• Object detection/identification
• Geodata extraction or resale
• Offline uses, including for any of the above

Map Tiles API responses may include Cache-Control headers which should beimplemented according to theHTTP protocol documentation.As an example, your client must respect the max-age value, thestale-while-revalidate value, the must-revalidate directive, and theprivate directive when they are passed in the response.

Map Tiles API responses may also include an ETag header which should alsobe implemented according to the HTTP protocol documentation when requesting withrevalidation.

Displaying the Google logo

When you use the Map Tiles API to display a Google Map, you must alsodisplay the Google logo on the map, and you must not alter it in any way. Youshould place the Google logo in the bottom left-hand corner of the map, and youshould place the attribution information in the right-hand corner of the map.

The following map example shows the Google logo in the lower left of the map,and the attribution in the lower right.

For use on a light background	For use on a dark background

The following zip file contains the Google logo in the correct sizes for desktop, Android, and iOS applications. You may not resize or modify these logos in any way.

Download: google_logo.zip

Don't modify the attribution. Don't remove, obscure, or crop out the attributioninformation. You cannot use Google logos inline (for example, "These maps arefrom [Google_logo]").

Keep the attribution close. If using screenshots of Google imagery outside of direct embeds, include the standard attribution as it appears in the image. If necessary, you may customize the style and placement of the attribution text, so long as the text is within close proximity of the content and legible to the average viewer or reader. You may not move the attribution away from the content, such as to the end of your book, the credits of your files or show, or the footer of your website.

Include third-party data providers. Some of the data and images on our mapping products come from providers other than Google. If using such imagery, the text of your attribution must say the name "Google" and the relevant data provider(s), such as "Map data: Google, Maxar Technologies." When there are third-party data providers cited with the imagery, only including "Google" or the Google logo is not proper attribution.

If you're using Google Maps Platform on a device where the attribution display is not practical, please contact the Google sales team to discuss licenses appropriate to your use case.

Map Tiles API

Data returned from the Map Tiles API requires the display of attributionand copyright information from the appropriate metadata or viewport informationrequests. You should display this information in the appropriate location,usually the bottom right corner of the displayed set of tiles, or in the 3Drenderer view.

Get attribution and copyright information from the copyright fieldin the responses of the following API calls, depending on the service you'reusing:

• Map Tiles
• Street View Tiles
• Photorealistic 3D Tiles

2D tiles

Basemap, Satellite and Terrain tiles

Copyright and attribution information is available from the viewport informationresponse, as shown in the following example.

{ "copyright": "Map data ©2023", "maxZoomRects": [ { "maxZoom": 19, "north": 90, "south": -90, "east": 180, "west": -180 }, ... ]}

Street View Tiles

Copyright and attribution information is available from the Street View metadataresponse. For example:

{ "panoId": "Zzl28rqGJgaL2IdkUleP8A", "lat": 50.059138596550696, "imageHeight": 6656, "imageWidth": 13312, "tileHeight": 512, "tileWidth": 512, "copyright": "From the Owner, Photo by: Google", …}

The panorama ID, which is used to uniquely identify a Street View panorama, isexempt from the caching restriction. Therefore, you can store panorama ID valuesindefinitely. Panorama ID values are returned in the panoId field in StreetView Static API responses.

Photorealistic 3D Tiles

For Photorealistic 3D Tiles, attribution data is returned in each tile request.You must aggregate, sort, and display in a line, all attributions for displayedtiles; usually along the bottom of the rendering. For example, you can find thedata attributions in aglTF tile by looking under asset, copyright.

{ "asset": { "version": "2.0", "generator": "draco_decoder", "copyright": "Data SIO, NOAA, U.S. Navy, NGA, GEBCO;Landsat / Copernicus" }}

CesiumJS

If you're using CesiumJS as your 3D Tiles renderer, then to display attributions,you need to enable showCreditsOnScreen in your rendering HTML.

// Add 3D Tiles tileset. const tileset = viewer.scene.primitives.add(new Cesium.Cesium3DTileset({ url: "https://tile.googleapis.com/v1/3dtiles/root.json?key=YOUR_API_KEY", // This property is needed to appropriately display attributions // as required. showCreditsOnScreen: true, }));

Cesium for Unreal

If you're using Cesium for Unreal as your 3D Tiles renderer, then to displayattributions, you need to enable the Show Credits On Screen field in theWorld Outliner.

Cesium for Unity

If you're using Cesium for Unity as your 3D Tiles renderer, then to displayattributions, you need to enable the Show Credits On Screen field in theInspector console.

Style guidelines for Google attribution

Following are style guidelines for Google attributions in CSS and HTML if you're not able to usethe downloadable Google logo.

Clear space

The amount of clear space around the lockup should be equal to or greater than the heightof the "G" in Google.

The space between the attribution copy and the Google logo should be half the width ofthe "G".

Legibility

The byline should always be clear, legible, and appear in the right color variation for agiven background. Always be sure to provide enough contrast for the logo variation that youselect.

Color

Use Google Material Gray 700 text on a white or light background that uses a range of 0%–40%maximum tint of black.

Google

#5F6368RGB 95 99 104HSL 213 5 39HSB 213 9 41

On darker backgrounds, and over photography or non-busy patterns, use white text for byline andattribution.

Google

#FFFFFFRGB 255 255 255HSL 0 0 100HSB 0 0 100

Font

Use the Roboto font.

Example CSS

The following CSS, when applied to the text "Google," would render "Google" with the appropriate font, color, and spacing on a white or light background.

font-family: Roboto;font-style: normal;font-weight: 500;font-size: 16px;line-height: 16px;padding: 16px;letter-spacing: 0.0575em; /* 0.69px */color: #5F6368;