Pricing overview

Mapbox employs a pay-as-you-go pricing model for its mapping platform, meaning users are charged based on their actual consumption of services. This model includes a generous free tier designed to accommodate initial development and moderate usage. Beyond the free tier, costs are accrued incrementally based on specific usage metrics associated with each Mapbox API and service.

The primary components that contribute to Mapbox costs include:

  • Map loads: Each time a map is displayed to a user, it counts as a map load. This includes interactive maps rendered using SDKs like Web GL JS, iOS, or Android, as well as static map images. Different types of map loads (e.g., interactive vs. static) may have distinct pricing tiers after the free limits are exceeded, which can be reviewed on the Mapbox pricing page.
  • API requests: Services such as the Geocoding API, Navigation API, and Search Box API are billed per request. Each call to these API endpoints counts towards usage. For example, converting an address string to coordinates using the Geocoding API or calculating a route with the Navigation API consumes one request.
  • Data storage and processing: Specialized services, such as Mapbox Movement Data or custom tile set hosting, may incur charges based on data volume, storage duration, or processing operations. Pricing for these advanced features is typically detailed separately.

Mapbox's pricing structure aims for transparency, allowing developers to scale their applications without large upfront commitments. Customers can monitor their usage through the Mapbox account dashboard to manage costs effectively. For applications with very high volumes, Mapbox offers custom enterprise plans, which may include discounted rates or dedicated support options that are not publicly listed on their standard pricing pages.

Plans and tiers

Mapbox primarily offers a single pay-as-you-go plan, which applies to all users after their free tier limits are exceeded. There are no fixed monthly subscription tiers like 'Basic,' 'Pro,' or 'Enterprise' for general API usage, however, custom pricing and support options are available for high-volume users. The pricing structure is organized by product component, with different per-unit rates for maps, geocoding, navigation, and other services.

The core concept is that all users start on the same free tier, and once they exceed those limits, they automatically transition to the pay-as-you-go rates. This means developers only pay for what they use beyond the specified free thresholds. For instance, if an application exceeds its free map loads in a month but stays within its free geocoding requests, it will only be charged for the additional map loads.

While there isn't a formal tiered plan structure for the API services themselves, Mapbox does differentiate pricing based on the complexity or type of service. For example, turn-by-turn navigation requests often have a higher per-unit cost than basic geocoding requests due to the computational resources involved. Developers should consult the Mapbox product pricing details for specific rates.

For organizations requiring extensive support, dedicated account management, or custom feature development, Mapbox provides options for direct engagement to establish a custom agreement. These enterprise agreements are tailored to specific needs and usage patterns, often involving volume discounts or specialized service level agreements (SLAs).

Mapbox Pay-as-You-Go Plan Overview
Plan Name Price Model Key Limits (beyond free tier) Best For
Pay-as-you-go Usage-based
  • Map Loads: Starts at $5 per 1,000
  • Geocoding: Starts at $0.0005 per request
  • Navigation: Starts at $0.001 per request
  • Static Images: Starts at $5 per 1,000 requests
 All developers and businesses, from startups to large enterprises, before custom agreements. Ideal for flexible scaling.
Custom Enterprise Negotiated Volume-based discounts, custom SLAs, dedicated support. Specific limits are not publicly disclosed. Large organizations with high-volume usage, specific performance requirements, or complex custom needs.

Free tier and limits

Mapbox offers a substantial free tier that allows developers to build and deploy applications without incurring costs up to certain usage thresholds. This free tier resets monthly, providing consistent access to core services for low-to-medium usage applications or during the development phase.

The key components of the Mapbox free tier include:

  • Map Loads: Up to 50,000 map loads per month. This covers instances where interactive maps are displayed in web or mobile applications using Mapbox GL JS, iOS SDK, or Android SDK. Each time a map view is initialized and displayed to a user, it counts towards this limit.
  • Geocoding Requests: Up to 100,000 geocoding requests per month. This allows for converting addresses to geographic coordinates (forward geocoding) or coordinates to human-readable addresses (reverse geocoding) using the Mapbox Geocoding API.
  • Navigation Requests: Up to 100,000 navigation requests per month. This includes calls to the Mapbox Navigation API for calculating routes, estimating travel times, and retrieving turn-by-turn instructions.
  • Static Images: A specific number of static image requests, typically aligning with the map loads, allowing for the generation of non-interactive map images for embed or display.

It is important to note that different Mapbox services, such as Mapbox Studio (for map style editing), Mapbox GL JS (for web maps), and the various API endpoints (Geocoding, Navigation, Search), each have their own specific free tier allowances. For a comprehensive breakdown of all free tier limits across Mapbox's product suite, developers should refer to the Mapbox free tier details page. Exceeding any of these limits for a given service in a month will result in charges only for the overage of that specific service, at the published pay-as-you-go rates.

Real-world cost examples

Understanding Mapbox pricing involves considering how various usage metrics combine. Here are a few real-world cost scenarios for an application using Mapbox services beyond the free tier, assuming typical pay-as-you-go rates:

Scenario 1: Small Business Directory App

  • Usage: 75,000 map loads/month (25,000 over free tier), 120,000 geocoding requests/month (20,000 over free tier).
  • Cost Calculation:
    • Map Loads: 25,000 overage × ($5/1,000) = $125
    • Geocoding: 20,000 overage × ($0.0005/request) = $10
    • Total Monthly Cost: $125 + $10 = $135
  • Justification: This app displays maps for business locations and uses geocoding to convert user-entered addresses. The free tier covers a significant portion, but moderate additional usage incurs charges primarily from map loads.

Scenario 2: Ride-Sharing Dispatch System

  • Usage: 200,000 map loads/month (150,000 over free tier), 200,000 geocoding requests/month (100,000 over free tier), 500,000 navigation requests/month (400,000 over free tier).
  • Cost Calculation:
    • Map Loads: 150,000 overage × ($5/1,000) = $750
    • Geocoding: 100,000 overage × ($0.0005/request) = $50
    • Navigation: 400,000 overage × ($0.001/request) = $400
    • Total Monthly Cost: $750 + $50 + $400 = $1,200
  • Justification: A ride-sharing app heavily uses maps for real-time tracking, geocoding for pickup/drop-off, and navigation for routing. Navigation requests typically represent a larger portion of the cost due to their higher per-unit rate and volume.

Scenario 3: Event Map for a Large Conference

  • Usage: 1,000,000 map loads over a 3-day period (950,000 over monthly free tier), 50,000 geocoding requests (within free tier).
  • Cost Calculation:
    • Map Loads: 950,000 overage × ($5/1,000) = $4,750
    • Geocoding: $0 (within free tier)
    • Total Monthly Cost: $4,750
  • Justification: A temporary event often sees a spike in map usage. Even if the event is short, the total map loads for the month can quickly exceed the free tier, leading to significant costs primarily from map rendering. This scenario highlights the importance of anticipating peak usage.

These examples illustrate that while the free tier is generous, high-traffic applications or those heavily reliant on specific API calls can accrue significant costs. Developers should utilize Mapbox's dashboard to monitor their usage and project costs based on anticipated user interactions.

How the pricing compares

Mapbox's pay-as-you-go pricing model is common among cloud-based mapping platforms, but specific rates and free tier allowances can vary significantly when compared to alternatives like Google Maps Platform and HERE Technologies.

Mapbox vs. Google Maps Platform:

  • Free Tier: Mapbox generally offers a larger free tier for certain services, particularly map loads and geocoding requests. Google Maps Platform's free tier, while present, is often perceived as smaller for developers new to the platform, typically defined by a $200 monthly credit that can be applied across various services. For example, Google Maps Platform's Dynamic Maps begin billing after 28,000 loads within the free credit, which is less than Mapbox's 50,000 free loads.
  • Per-Unit Costs: For comparable services beyond the free tier, Google Maps Platform can sometimes have higher per-unit costs for high-volume usage, especially for premium features like advanced routing or places details. Mapbox often provides more competitive rates for core map loads and basic geocoding, particularly as usage scales up.
  • Customization: Mapbox Studio provides extensive visual styling capabilities that can reduce development time for custom maps, potentially offsetting some API costs by enabling more efficient design workflows. Google Maps also offers robust styling tools, but Mapbox is often cited for its granular control over map appearance.

Mapbox vs. HERE Technologies:

  • Model: HERE Technologies also operates on a freemium model with various plans. Their pricing structure can be more complex, sometimes involving fixed monthly fees for certain service bundles in addition to usage-based billing. Mapbox's pure pay-as-you-go provides clearer, direct usage billing for most services.
  • Free Tier: HERE offers a free tier, often structured around a certain number of transactions or requests per month, similar to Mapbox. However, the exact limits for services like geocoding or routing can differ. Developers should refer to HERE's developer pricing for specific comparisons.
  • Specialization: HERE often emphasizes its strengths in automotive-grade navigation, logistics, and real-time traffic data, which can be reflected in its feature set and pricing for those specific-use cases. Mapbox is strong in developer experience and customization, appealing to a broader range of applications.

In summary, Mapbox's pricing strategy is competitive for developers seeking a flexible, usage-based model with a strong free tier. Its emphasis on developer tools and map customization often makes it an attractive option, especially for applications where visual distinctiveness and performance are priorities. While Google Maps Platform is ubiquitous, Mapbox often provides a more cost-effective alternative for certain usage patterns, especially when factoring in the free tier and per-unit rates beyond it. HERE Technologies competes closely, particularly in specialized areas like advanced navigation and location intelligence, but with a potentially different plan structure.