- Step 1: Access your invoices page
- Step 2: Open an invoice and review details of charges
- Step 3: Use the pricing calculator that matches each line item on your invoices
- Step 4: Follow the same process for any other products you see on your invoices
- Next steps
- Use the latest version of Mapbox GL JS (or at least v1.0.0)
- Use the Static Tiles API instead of the Raster Tiles API with Mapbox.js, Leaflet, and other applications
Estimating your future invoices on new pricing.
This guide outlines how to use the correct pricing calculators on the pricing page to estimate the costs of your invoices under Mapbox’s new pricing model. This guide will only help if you have not already upgraded to the new pricing model.
Every invoice will include details of charges, which list distinct line items for each product you were billed for in a single billing period. Each line item contains the following information (product, quantity, unit, and costs):
Identifying which products your account has been billed for is the first step to understanding current costs and projecting future expenses. Note that it's possible that your account has used some products during a billing period that did not exceed the free tier for that product and were not billed. To review usage volumes for all products within a billing period, input the dates from your invoices into the Statistics page.
The following example invoice was charged for use of the Raster Tiles API and Vector Tiles API independently. Each product is listed as separate line items:
There is a pricing calculator for each product on the Mapbox pricing page. Input your usage volumes to the corresponding pricing calculator for that product. For the most accurate estimations, use the calculator that matches the line items on your invoice.
Input the values for each product in the corresponding calculator on the pricing page.
- Find the Raster Tiles API section on the pricing page.
- Click the Show pricing calculator button.
- In the text input box, enter the value that appears on your invoice next to "Raster Tiles API:" (in the example below, this is represented by Y,YYY,YYY).
- The new estimated monthly cost will appear to the left.
- Find the Vector Tiles API section on the pricing page.
- Click the Show pricing calculator button.
- In the text input box, enter the value that appears on your invoice next to "Raster Tiles API:" (in the example below, this is represented by X,XXX,XXX).
The new estimated monthly cost will appear to the left.
You may see line items for several different products on your invoices. These correspond to the products that your mapping implementations are utilizing (for example: Static Images API, Temporary Geocoding API, Directions API, etc).
It’s important to match the product on your invoice line items to the correct product on the pricing page so the pricing calculator accurately matches to your projected costs.
Once you have used the pricing calculators for each product found on your invoices, add the costs to see what that invoice would have cost under the new pricing model.
There are actions you can take before December 1, 2019 to optimize your implementations and reduce costs.
If you are using a product that is charged by tile requests, such as a version of Mapbox GL JS below v1.0.0, Mapbox.js, Leaflet, or another service with Mapbox-hosted tiles, there are actions you can take to reduce your bill.
The latest versions of Mapbox GL JS are billed by map loads instead of by tile requests. A map load occurs whenever a Mapbox GL JS Map object is initialized on a webpage and a Mapbox-hosted map tile is requested. 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.
If you’re already using GL JS, you can review the GL JS changelog to learn more about how to upgrade to v1.0.0 (or greater). For the vast majority of users, there's likely not much work required to update the GL JS version number to v1.0.0 or greater in your web app or webpage since there have been no real major breaking changes apart from new pricing. If you run into any particular issues upgrading, you can reach out to us for technical help through the support form.
Use the Static Tiles API instead of the Raster Tiles API with Mapbox.js, Leaflet, and other applications
If your invoice includes requests to the Raster Tiles API and you are using Mapbox.js or Leaflet, you can either read this guide to learn how to upgrade to GL JS, or, if upgrading to GL JS is not an option, you can use the Static Tiles API instead of the Raster Tiles API with your Mapbox.js or Leaflet implementation. The process of switching from Raster Tiles to Static Tiles depends on the tools you are using:
|Implementation||Old Method||New Method|
|Other applications (Static Tiles API request)|
Read more about using the Static Tiles API versus Raster Tiles API in web apps.
Still have questions? Let us know. Our billing support team is standing by to help.