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)

Public beta

Mapbox Tiling Service is in public beta and is subject to potential changes.

Overview
  • Billed by square kilometers for tileset processing and square kilometer days for tileset hosting
  • See rates and discounts per tileset processing and tileset hosting in the pricing page's Tilesets section

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:

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:

Tileset recipe's maxzoom valueLine itemNotes
0-5FreeAppropriate for low-resolution administrative boundaries like countries and states.
6-10Tileset Processing 10m
(cost per km2)
Appropriate for low-resolution administrative boundaries like countries and states.
11-13Tileset Processing 1m
(cost per km2)
Appropriate for high-resolution administrative boundaries like neighborhoods or census tracts.
14-16Tileset Processing 30cm
(cost per km2)
Appropriate for buildings, roads, and points of interest.
17-22Tileset Processing 1cm
(cost per km2)
Contact us to create a tileset with a maxzoom greater than 16.
Note

The most expensive tilesets to process are those that both cover a large area, like the entire world, and require high precision, for example a global road network. You can lower your costs by either reducing the area of your data or reducing the maxzoom level in your tileset recipe. If you want to reduce the area of your data, you can use bbox in your tileset recipe to tile your data to a specified bounding box. If you want to completely eliminate your tileset processing costs, you can use a maxzoom of less than 6 in your tileset recipe since tilesets created at that zoom level are free. 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.

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:

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:

Tileset recipe's maxzoom valueLine itemNotes
0-5FreeAppropriate for low-resolution administrative boundaries like countries and states.
6-10Tileset Hosting 10m
(cost per km2 per day)
Appropriate for low-resolution administrative boundaries like countries and states.
11-13Tileset Hosting 1m
(cost per km2 per day)
Appropriate for high-resolution administrative boundaries like neighborhoods or census tracts.
14-16Tileset Hosting 30cm
(cost per km2 per day)
Appropriate for buildings, roads, and points of interest.
17-22Tileset Hosting 1cm
(cost per km2 per day)
Contact us to host a tileset with a maxzoom greater than 16.

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.

Note

The most expensive tilesets to host are those that both cover a large area, like the entire world, and will require high precision, for example a global road network. You can lower your costs by reducing the area of your data, the maximum zoom level (using maxzoom) in your tileset recipe and deleting any tilesets you're no longer using. If you want to reduce the area of your data, you can use bbox in your tileset recipe to tile your data to a specified bounding box. If you want to completely eliminate your tileset hosting costs, you can use a maxzoom of less than 6 in your tileset recipe since tilesets created at that zoom level are free. To learn more about how to optimize your tilesets to reduce tileset hosting costs, see our guide on managing your tileset processing and tileset hosting costs.

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

Overview
  • Billed by square kilometers for tileset processing and tileset hosting
  • See rates and discounts per tileset processing and tileset hosting in the pricing page's Tilesets section

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.

Note

Mapbox Studio is powered by the Uploads API, but is subject to usage restrictions and alternative pricing. See the Mapbox Studio section for more details.

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:

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.

Vector and MBTiles tileset's maxzoom valueTiff tileset's maxzoom valueLine item
0-50-6Free
6-107-11Tileset Processing 10m (cost per km2)
11-1312-14Tileset Processing 1m (cost per km2)
14-1615-17Tileset Processing 30cm (cost per km2)
17+18+Tileset Processing 1cm (cost per km2)

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:

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.

Vector and MBTiles tileset's maxzoom valueTiff tileset's maxzoom valueLine item
0-50-6Free
6-107-11Tileset Hosting 10m (cost per km2 per day)
11-1312-14Tileset Hosting 1m (cost per km2 per day)
14-1615-17Tileset Hosting 30cm (cost per km2 per day)
17+18+Tileset Hosting 1cm (cost per km2 per day)
Note

The most expensive tilesets to host are those that both cover a large area, like the entire world, and will require high precision, for example a global road network. You can lower your costs by deleting any tilesets you're no longer using, which you can do using Mapbox Tiling Service (MTS) or Mapbox Studio. To learn more about how to optimize your tilesets to reduce tileset hosting costs, see our guide on managing your tileset processing and tileset hosting costs.

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:

Tileset maxzoomPrecisionZoom level at which area is calculated
0-5FreeN/A
6-1010m6
11-131m11
14-1630cm14
17-221cm17
The following example tiles a GeoJSON file that contains the rough outline of California. The area is being calculated at two precision levels: 10 meter and 1 meter.
10 meter precision: The area for 10 meter precision (maxzoom 6-10) is calculated at zoom 6. The tiles at zoom 6 are large, so the area per tile is also large, but there are very few tiles that contain features from the original GeoJSON (the outline of California) at this precision.
1 meter precision: The area for 1 meter precision (maxzoom 11-13) is calculated at zoom 11. At this precision, the number of tiles that contain features from the original dataset increase exponentially (each zoom level contains four times as many tiles as the previous zoom level), but the area per individual tile also decreases substantially: