Pricing by products

Web maps

Pricing for web map usage is based on API requests (i.e. tile requests), sessions (i.e. map loads) or monthly users (i.e. seats). The pricing method that applies to your application depends on which product you are using, and in some cases, which version of that product. These are the libraries, tools, and versions that are included in this section:

• Mapbox GL JS v1.0.0 and higher
• Mapbox GL JS < v1.0.0
• Mapbox.js or Leaflet
• Third-party tools

For an overview of how to manage your costs for common interactive, non-interactive, and hybrid web map implementations, see the Manage your web map costs troubleshooting guide.

Mapbox GL JS v1.0.0 and higher

Web maps using Mapbox GL JS v1.0.0 and higher are billed by map loads. Beginning with Mapbox GL JS v2.0.0, a map load occurs whenever a Mapbox GL JS Map object is initialized. Measuring usage by map loads means that users interacting with your web map can toggle layers from non-composited sources on and off, zoom and pan around the map, and toggle between styles without affecting your usage. You can also add non-composited vector or raster sources to your map at runtime without incurring additional charges. The maximum session length for a map load is 12 hours. If a user has the same map open after 12 hours, Mapbox will count that as a new map load session.

Web maps using Mapbox GL JS Seats are billed by seats. A seat consists of a single user who uses Mapbox services within your web application during your month-long billing period. Each user can use unlimited Vector Tiles API and Raster Tiles API requests per month.

Mapbox GL JS < v1.0.0

Web maps using any version of Mapbox GL JS before v1.0.0 are billed by tile requests. There are two different types of tile requests that can be made by Mapbox GL JS:

• Vector Tiles API requests for any tiles from vector tilesets including Mapbox-maintained tilesets like Mapbox Streets or any custom vector tileset uploaded to your Mapbox account.
• Raster Tiles API requests for any tiles from raster tilesets including Mapbox-maintained tilesets like Mapbox Satellite or any custom raster tileset uploaded to your Mapbox account.

There are a few key differences between this tile-based pricing and the map load pricing described above, including:

• Map interaction: The more the user interacts with the map, the more tiles are requested. Interact with the map in the demo below to see the relationship between user interaction and the number of tiles requested. (In map load based pricing, it counts as one map load regardless of how much the user interacts with the map.)
• Composite sources vs. non-composite sources: You can combine any Mapbox style with a Mapbox-maintained tileset, like Terrain v2 or Traffic v1, or tilesets that you upload to Mapbox Studio. Sources added on the client will not be composited so every tile from each vector source will be requested separately, counting toward total tile requests. You can composite vector tile sources in Mapbox Studio to reduce the number of tiles that are requested.
• Vector tiles vs. raster tiles: As described above, vector tiles and raster tiles are counted and billed separately.

Mapbox.js or Leaflet

If you are using Mapbox.js or Leaflet with Mapbox-hosted map tiles, usage is determined by tile requests. Mapbox.js and Leaflet applications display raster tiles, however there are two different kinds of tile requests you may be making: Static Tiles API requests or Raster Tiles API requests.

Raster tiles from Mapbox GL styles

If you are using a Mapbox GL map style (using a style URL) via L.mapbox.styleLayer, you are requesting map tiles from the Static Tiles API, which takes GL-based styles and renders raster tiles.

The example below uses a GL-based style, mapbox://styles/mapbox/streets-v11, with Mapbox.js. Each tile has a red border to help you see how many are required to display the map you see on the screen.

L.map('map')
  .setView([38.8929, -77.0252], 14)
  .addLayer(L.mapbox.styleLayer('mapbox://styles/mapbox/streets-v11'));

Raster tiles from raster tilesets

If you are setting the map style via a raster tileset's tileset ID, you are requesting map tiles from the Raster Tiles API. Raster tiles can be satellite imagery, another raster data source, or a classic style.

The example below uses the raster tileset, mapbox.satellite, with Mapbox.js. Each tile has a red border to help you see how many are required to display the map you see on the screen.

L.mapbox.map('map', 'mapbox.satellite')
  .setView([38.8929, -77.0252], 14);

Third-party tools

Web maps that rely on Mapbox-hosted tiles, but are not served via Mapbox GL JS are billed by tile requests. This includes vector tiles from vector tilesets, GL-based styles rendered as raster tiles, and raster tiles from raster tilesets. The table below includes some popular third-party integrations. Not all possible third-party tools are included.

Mobile applications

Pricing for mobile applications is either based on monthly active users (MAUs) or tile requests. The pricing method that applies to your application depends on which product you are using, and in some cases, the version of that product.

MAUs are users that accessed Mapbox services within your applications during a given month. The month-long period aligns with your billing period, which is likely not aligned with calendar months.

This guide does not include the number of units included in the free tier, the exact cost per billable unit, or volume-based discounts for each service. For this information, see the pricing page.

These are the SDKs and versions that are included in this section:

• Maps SDK for iOS and Android
• Navigation SDK for iOS and Android
• Vision SDK for iOS and Android
• Maps SDK for Unity
• Hybrid apps
• Offline maps

Maps SDK for iOS and Android

Applications built with the Mapbox Maps SDK for iOS and the Mapbox Maps SDK for Android are billed based on monthly active users.

The line item shown in your invoice will vary based on the version of the Maps SDK you are using. You will either see Maps SDKs for mobile MAUs or Legacy SDKs for mobile MAUs.

Below is a breakdown of what you can expect to see on your invoice:

Navigation SDK for iOS and Android

The monthly active user (MAU) line item shown in your invoice will vary based on the version of the Navigation SDK you are using. You will see Navigation SDK MAUs, Maps SDKs for mobile MAUs, or Legacy SDKs for mobile MAUs.

Navigation SDKs MAUs

Applies to:

• Android: 1.0.0 and higher
• iOS: 1.0.0 and higher

Applications built with these versions are billed based only on monthly active users, specifically "Navigation SDKs" MAUs. Navigation SDK MAUs include Directions API, Vector Tiles API, and Raster Tiles API requests with no upfront commitments or annual contracts. A Navigation SDK MAU becomes a billable event only once a user utilizes the Navigation SDK for turn-by-turn directions or for free-drive.

A single user is billed as one MAU across app upgrades as long as the app is not deleted. Deleting and re-installing an app that uses the Navigation SDK would result in an additional MAU. This happens because the SDK does not store personally identifying information.

To see the number of Navigation SDKs MAUs included in the free tier and the cost per Navigation SDKs MAU beyond the free tier, see the Navigation SDKs section of our pricing page.

Maps SDKs for mobile MAUs + Directions API requests

Applies to:

• Android: 0.41.0 to 0.42.x
• iOS: 0.36.0 to 0.40.x

Applications built with these versions are billed based on a combination of monthly active users (specifically "Maps SDKs for mobile" MAUs) and Directions API requests. Maps SDKs for mobile MAUs include Vector Tiles API and Raster Tiles API requests. Directions API requests will appear as a separate line item in your monthly invoice.

To see the number of MAUs and requests included in the free tier and the cost per MAU or request beyond the free tier, see:

• Maps SDKs for mobile section of our pricing page
• Directions API section of our pricing page

Legacy SDKs for mobile MAUs + Directions API requests

Applies to:

• Android: less than 0.41.0
• iOS: less than 0.36.0

Applications built with these versions are billed based on a combination of monthly active users (specifically "Legacy SDKs for mobile" MAUs) and Directions API requests. Legacy SDKs for mobile MAUs include Vector Tiles API and Raster Tiles API requests. Directions API requests will appear as a separate line item in your monthly invoice.

To see the number of MAUs and requests included in the free tier and the cost per MAU or request beyond the free tier, see:

• Maps SDKs for mobile section of our pricing page (equivalent to Legacy SDK for mobile rates and tiers)
• Directions API section of our pricing page

Vision SDK for iOS and Android

Applications built with the Mapbox Vision SDK for iOS and the Mapbox Vision SDK for Android are billed based on monthly active users.

The line item shown in your invoice will vary based on the version of the Vision SDK you are using. You will either see Vision SDKs for mobile MAUs or Legacy SDKs for mobile MAUs.

Below is a breakdown of what you can expect to see on your invoice:

For Vision SDKs for mobile MAUs, a single monthly active user is a user of Mapbox vision services within your mobile app during your month-long billing period. Each user may make unlimited requests to APIs in the vision service via the Vision SDKs for iOS and Android. Usage of APIs and other Mapbox products outside the vision service are billed in addition to Vision SDK MAUs.

Maps SDK for Unity

Applications built with the Mapbox Maps SDK for Unity are billed based on monthly active users.

The line item shown in your invoice will vary based on the version of the Maps SDK you are using. Below is a breakdown of what you can expect to see on your invoice:

For Maps SDK for Unity MAUs, a single monthly active user may make unlimited Vector Tiles API, Raster Tiles API, and Static Tiles API requests per month. Usage of APIs and other Mapbox products outside the Vector Tiles API and Raster Tiles API are billed in addition to Maps SDK for Unity MAUs.

Hybrid apps

Third-party frameworks built from the native Mapbox Mobile SDKs are typically billed based on monthly active users. Apps built with other third-party frameworks are billed based on tile requests. Below are some examples of popular SDKs and frameworks and whether Mapbox tracks usage through mobile users or tile requests.

Offline maps

Offline maps usage in the Maps SDKs for Mobile are measured in tile requests. Resources downloaded for offline use are not included in MAU billing. There are two different types of tile requests that can be made:

• Vector Tiles API requests are made for offline regions that use vector tilesets including Mapbox-maintained tilesets like Mapbox Streets or any custom vector tileset uploaded to your Mapbox account.
• Raster Tiles API requests are made for offline regions that use raster tilesets including Mapbox-maintained tilesets like Mapbox Satellite or any custom raster tileset uploaded to your Mapbox account.

Developers are billed accordingly for each tile request beyond the free tier. The number of tiles that can be downloaded varies based on the version of the Maps SDK you are using. Below is a breakdown of what you can expect:

For the Maps SDK for iOS v5.3.0 and higher and the Maps SDK for Android v8.3.0 and higher, offline maps usage is shown on your Statistics page as Vector Tile or Raster Tile API requests.

Adjust the tile limit per user

For the Maps SDK for iOS v5.3.0 and higher and the Maps SDK for Android v8.3.0 and higher there are no hard limits to the number of tiles your users can download. But, because you are responsible for the cost of all tiles downloaded by your users, you may want to set an offline tile limit.

By default, the offline tile limit is set to 6,000, which means each of your users may download 6,000 tiles for offline use. Use the Mapbox offline tile count estimator to estimate how many tiles your users may need for their offline maps usage. To increase or decrease the number of offline tiles your users may download, change the offline tile limit:

• On Android, set the offline tile limit by calling -setOfflineMapboxTileCountLimit.
• On iOS, set the offline tile limit by calling -[MGLOfflineStorage setMaximumAllowedMapboxTiles:].

Tilesets

Mapbox offers two tools for creating tilesets: Mapbox Tiling Service (MTS), which can be used to create vector tilesets, and the Mapbox Uploads API, which can be used to create vector and raster tilesets. When you upload data to Mapbox Studio, it uses the Uploads API to create tilesets.

You can see your MTS and Uploads API usage statistics on your statistics dashboard, and your MTS and Uploads API costs are listed in your monthly invoices.

Mapbox Tiling Service (MTS)

Mapbox Tiling Service (MTS) is a tool for creating vector tilesets. With MTS, you use sets of configuration options (tileset recipes) to tell MTS how to process your geospatial data into vector tiles (a tiled, and efficient file delivery mechanism). The resulting tiles are hosted on Mapbox servers for use in map styles and your applications.

When you use MTS, you will see two different line items: tileset processing and tileset hosting. The cost of each will depend on the area of your tiled data and the precision level of your tileset.

MTS tileset processing

Each time you publish a tileset with MTS, you will see a one-time tileset processing charge. The total cost of tileset processing depends on two factors:

• Precision level, which is determined by the maxzoom used in the tileset recipe. Precision approximately describes the range of accuracy of tiled data relative to the real world.
• Area, in square kilometers (km²), of your tiled data. This area is the total area of all tiles that contact features from your data at your specified precision level. See the How area is calculated section for more details on how this value is determined.

There are four possible line items related to tileset processing, each associated with a different precision level and pricing. MTS supports four precision levels: 10 meter, 1 meter, 30 centimeter, and 1 centimeter. The line item you see on your invoice depends on the maxzoom value you use in your tileset recipe:

MTS tileset hosting

After you publish a tileset with MTS, you will begin to see a recurring tileset hosting charge for every day your tileset is hosted on Mapbox's servers. This charge covers the cost of storing your tiled and processed data on Mapbox servers and will depend on several factors:

• Precision level, which is determined by the maxzoom used in the tileset recipe. Precision approximately describes the range of accuracy of tiled data relative to the real world.
• Square kilometer days is equal to the area tiled multiplied by the number of days hosted. The maximum possible value for a tileset's square kilometer days is the area of the tileset multiplied by 30 (the total days in the billing period).
• Area tiled, in square kilometers (km²), of your tiled data. This area is the total area of all tiles that contact features from your data at your specified precision level. See the How area is calculated section for more details on how this value is determined.
• Days hosted in your account in a given month-long billing period.

There are four possible line items related to tileset hosting, each associated with a different precision level and pricing. MTS supports four precision levels: 10 meter, 1 meter, 30 centimeter, and 1 centimeter. The line item you see on your invoice depends on the maxzoom value you use in your tileset recipe:

For a tileset that has been published multiple times, hosting costs for a given day reflect the latest area of the tileset on that day. For example, a tileset that originally had an area of 10 square kilometers, but had an area of 5 square kilometers after an additional publish job will only incur tileset hosting costs for 5 square kilometers of data.

Mapbox Studio

Tilesets can be created in Mapbox Studio via the Mapbox Studio style editor, your tilesets page, or exported from a dataset using the dataset editor.

Mapbox Studio tileset processing

Tilesets uploaded in Mapbox Studio are free, and will not incur processing charges. Free uploads via Mapbox Studio are limited to 20 uploads per month, and 300 MB per upload.

Mapbox Studio tileset hosting

Tilesets uploaded in Mapbox Studio are free, and will not incur hosting charges. Free uploads via Mapbox Studio are limited to 20 uploads per month, and 300 MB per upload.

Uploads API

The Uploads API is a tool for uploading geospatial data and turning it into either raster or vector tiles. The Uploads API makes educated guesses about configuration options based on the data that you upload instead of using tileset recipes (the configuration options that Mapbox Tiling Service uses to process geospatial data into vector tiles).

When you use the Uploads API, you will see two different line items: tileset processing and tileset hosting. The cost of each will depend on the area of your tiled data and the precision level of your tileset.

Uploads API tileset processing

Each time you create an upload using the Uploads API, you will see a one-time tileset processing charge. A tileset processing cost includes both the cost of generating a tileset as well as the transfer costs associated with putting all tiles in that tileset onto Mapbox servers. (For example, if you upload MBTiles using the Uploads API, even though the tileset does not need to be generated, you will still see a tileset processing cost that reflects the transfer costs for moving the tileset to a Mapbox server.) The total cost of tileset processing depends on two factors:

• Precision level at which the Uploads API chooses to tile your data. Precision approximately describes the range of accuracy of tiled data relative to the real world.
• Area tiled, in square kilometers (km²), of your tiled data. This area is the total area of all tiles that contact features from your data at the precision level chosen by the Uploads API. See the How area is calculated section for more details on how this value is determined. On July 23rd, 2020 we improved the way we calculate area tiled for the Uploads API, which results in smaller area for many use cases and tilesets, so any area calculated before may vary.

There are four possible line items related to tileset processing, each associated with a different precision level and pricing. The Uploads API supports four precision levels: 10 meter, 1 meter, 30 centimeter, and 1 centimeter.

The line item you see on your invoice depends on the tileset's maxzoom value, which is determined automatically by the Uploads API. If you want more control over the precision level used for your vector tilesets, and ultimately the price you pay for them, use Mapbox Tiling Service (pricing described above).

To learn more about how to optimize your tilesets to reduce tileset processing costs, see our guide on managing your tileset processing and tileset hosting costs.

Uploads API tileset hosting

After you create an upload using the Uploads API, you will begin to see a recurring tileset hosting charge for every day your tileset is hosted on Mapbox's servers. This charge covers the cost of storing your tiled and processed data on Mapbox servers, and will depend on three factors:

• Precision level at which the Uploads API chooses to tile your data. Precision approximately describes the range of accuracy of tiled data relative to the real world.
• Square kilometer days is equal to the area tiled multiplied by the number of days hosted. The maximum possible value for a tileset's square kilometer days is the area of the tileset multiplied by 30 (the total days in the billing period).
• Area tiled, in square kilometers (km²), of your tiled data. This area is the total area of all tiles that contact features from your data at the precision level chosen by the Uploads API. See the How area is calculated section for more details on how this value is determined. On July 23rd, 2020 we improved the way we calculate area tiled for the Uploads API, which results in smaller area for many use cases and tilesets, so any area calculated before may vary.
• Days hosted in your account in a given month-long billing period.

There are four possible line items related to tileset hosting, each associated with a different precision level and pricing. The Uploads API supports four precision levels: 10 meter, 1 meter, 30 centimeter, and 1 centimeter. The line item you see on your invoice depends on the tileset's maxzoom value, which is determined automatically by the Uploads API.

How area is calculated for MTS and the Uploads API

When you upload a tileset using MTS or the Uploads API, Mapbox charges for the area of the tiles that contain features from that tileset, at the specified precision level. There is usually only one precision level per tileset unless it is a multi-layer tileset created using MTS.

For each precision level, area is always calculated at one zoom level:

Navigation-related APIs

Directions API, Optimization API, Map Matching API, Isochrone API

Usage of the Directions API, Optimization API, Map Matching API, and Isochrone API are all measured in API requests. The number of requests included in the free tier and the cost per request beyond what is included in the free tier are the same across APIs. A request that contains multiple waypoints - see the API documentation for service-specific details is billed as a single API request.

Matrix API

The Mapbox Matrix API is billed by elements rather than by requests, since this API handles requests of widely varying sizes. For instance, one request from the Matrix API can be many different origin and destination pairs, so one request from the Matrix API is equal to the number of sources multiplied by the number of destinations. The minimum number of elements included in a single request would be two (1 source x 2 destinations), while the maximum number of elements included in a single request would be 625 (25 sources x 25 destinations).

By default, the Mapbox Matrix API returns a symmetric matrix, using all input coordinates as both sources and destinations. In this case, the number of elements would be the number of coordinates². You may also generate an asymmetric matrix, with only some coordinates as sources or destinations. In that case, the number of elements per request would be the number of sources multiplied by the number of destinations.

Read more about how the Mapbox Matrix API works on our comprehensive How Directions Works guide.

For high volume use of the Mapbox Matrix API, contact our sales team for pricing.

Directions-related libraries and plugins

We have several tools across platforms that allow you to integrate Mapbox Directions-related APIs into your existing applications, including:

• Web: Mapbox GL Directions plugin for Mapbox GL JS and Mapbox-directions.js for Mapbox.js
• Android: Mapbox Java SDK
• iOS: MapboxDirections.swift

When using a directions-related library or plugin with a Mapbox map, you will be billed for the number of directions-related requests made in addition to map loads, Maps MAUs, or tile requests (read the Web maps or Mobile applications section above to see which applies to your application).

Search-related APIs

Geocoding API

Usage of the Geocoding API is measured in API requests. Details about the number of requests included in the free tier and the cost per request beyond what is included in the free tier are available on the pricing page. You may only use responses from the Geocoding API ("Geocodes") in conjunction with a Mapbox map.

The Geocoding API's autocomplete parameter is enabled by default. The autocomplete parameter is ideal for applications in which you want to suggest search results while a user enters their query. If you are using the API with autocomplete enabled, you will likely accumulate one API request per keystroke. For example, if you have autocomplete turned on and you set up your application to make a Geocoding API request every time a user types a character into a search bar, then a user typing "coff" looking for "coffee shops" will be making four Geocoding API requests, one for each letter.

To reduce the number of requests made while autocomplete is enabled, you can wait to begin making API requests until a specific number of characters are entered. The Geocoding API doesn't have a parameter for limiting requests built in, but you can use the Mapbox GL Geocoder (discussed below in the Geocoding-related libraries and plugins section), which does have that option, or you can write it into your application directly.

Geocoding-related libraries and plugins

We have several tools across platforms that allow you to integrate the Mapbox Geocoding API into your existing applications, including:

• Web: Mapbox GL Geocoder for Mapbox GL JS and both geocoderControl and geocoder for Mapbox.js
• Android: Mapbox Java SDK
• iOS: MapboxGeocoder.swift

When using a search-related library or plugin with a Mapbox map, you will be billed for the number of search-related requests made in addition to Maps MAUs for mobile applications or map loads or tile requests for web maps (read the Web maps or Mobile applications section above to see which applies to your application).

For libraries and plugins that include autocomplete, searches are billed as one API call per keystroke. For example, if you have autocomplete turned on and a user types "coff" in your application looking for "coffee shops", you will see four Geocoding API requests reflected on your Statistics page for this interaction, one for each letter.

To reduce the total requests sent (and billed), you should configure your application to only call the API after a specific number of characters are typed — usually 1-3 characters is a good range to reduce requests with limited impact on user experience. If you are using the Mapbox GL Geocoder, you can set this preference using setMinLength.

Maps-related APIs

Usage of Maps-related APIs is measured in tile requests, processing and hosting events, or API requests.

For information on APIs measured in tile requests including the Vector Tiles API, Raster Tiles API, and Static Tiles API, see the Web maps section above.

For information on APIs measured in processing and hosting events including Mapbox Tiling Service (MTS) and the Uploads API, see the Tilesets section above.

For all other maps-related APIs measured in API requests, see below.

Tilequery API

Each query for geographic features in one or more Mapbox-hosted vector tilesets at a given latitude and longitude will be counted as one Tilequery API request. Details about the number of Tilequery API requests included in the free tier and the cost per request beyond what is included in the free tier are available on the pricing page.

Static Images API

Usage of the Static Images API is measured in API requests. Details about the number of requests included in the free tier and the cost per request beyond what is included in the free tier are available on the pricing page.

Static Tiles API

The Static Tiles API is measured in API requests and can be used in conjunction with any raster tile client such as Mapbox.js, Leaflet, OpenLayers, etc. These tiling clients are not actively maintained by Mapbox. The Static Tiles API is well-suited for maps with limited interactivity or use on devices which do not support WebGL.

Mapbox Studio prints

Mapbox Studio offers 100 high resolution image exports per account using the print panel. These 100 exports are free for all users. Usage of the Mapbox Studio print export option will not be reflected on your invoice. After 100 exports have been used on your account, you will no longer be able to access the print panel.

Mapbox customers with Enterprise plans have a higher number of allowed image exports. Contact Mapbox sales for more information about Enterprise accounts.