Mapbox GL JS Pricing: Usage-Based Costs (2026)

Pricing overview

Mapbox GL JS, a client-side JavaScript library for interactive web maps, operates under a usage-based pricing structure provided by Mapbox. This model charges based on the consumption of various Mapbox services that Mapbox GL JS integrates with, rather than a flat license fee for the library itself. The primary cost drivers for Mapbox GL JS implementations are map loads and active users, particularly for raster and vector base maps. Additional services, such as geocoding, directions, and static images, are priced independently and contribute to the overall cost when utilized within a Mapbox GL JS application.

The Mapbox pricing model is designed with tiers, where the per-unit cost decreases as usage volume increases. This approach aims to accommodate projects ranging from small-scale applications within the free tier to large-scale enterprise deployments requiring millions of map interactions. Developers can monitor their usage through the Mapbox dashboard to manage costs effectively. Understanding the distinction between map loads (each time a map is displayed) and active users (unique users interacting with a map within a billing period) is crucial for accurate cost estimation, as detailed in the official Mapbox pricing breakdown.

Plans and tiers

Mapbox GL JS itself is an open-source library, but its utility relies on accessing Mapbox's hosted services, which are subject to a tiered pricing structure. The pricing is divided into several categories, with 'Maps' being the most relevant for Mapbox GL JS users. This category includes charges for 'Map Loads' and 'Active Users'.

Map Loads: A map load is counted each time a map initialized with Mapbox GL JS is displayed to a user. This metric applies to both vector and raster maps. The cost per map load decreases as the total number of map loads increases beyond specific thresholds.

Active Users (for base maps): An active user is defined as a unique individual who interacts with a map within a billing month. This metric is primarily associated with base map usage and helps differentiate between automated map displays and interactive user sessions.

Beyond the core map display, Mapbox offers various APIs and services that can be integrated with Mapbox GL JS, each with its own pricing tiers:

• Geocoding API: For converting addresses to coordinates and vice versa. Priced per request.
• Directions API: For calculating routes. Priced per request.
• Tilesets API: For creating and managing custom vector tilesets. Priced based on tile updates and hosting.
• Static Images API: For generating non-interactive map images. Priced per request.

The following table summarizes the key pricing tiers for Mapbox GL JS's core 'Maps' services as of May 2026. Note that specific pricing points are subject to change and should be verified on the official Mapbox pricing page.

Mapbox also offers custom enterprise plans for very high-volume usage or specific requirements, which include dedicated support and tailored pricing structures. These plans are negotiated directly with Mapbox sales teams.

Free tier and limits

Mapbox GL JS applications benefit from a substantial free tier provided by Mapbox, which allows developers to build and deploy applications without incurring costs for initial usage. The free tier primarily covers the 'Maps' service, which includes Map loads and Active users.

• Map Loads: Up to 50,000 map loads per month are included in the free tier. This means an application can display a map 50,000 times within a billing cycle before paid rates apply.
• Active Users: Up to 50,000 active users per month for base maps are also part of the free tier. An active user is generally defined as a unique user who engages with a map during a month.

Beyond 'Maps', the free tier also extends to other Mapbox services that can be integrated with Mapbox GL JS:

• Geocoding: 100,000 requests per month.
• Directions: 25,000 requests per month.
• Mapbox Studio (Tilesets API): 500 MB of tile hosting and 250 MB of data uploads per month.

These limits are generous for development, testing, and even for small-scale production applications with limited traffic. Developers should monitor their usage closely through the Mapbox account dashboard to avoid unexpected charges once the free tier limits are approached or exceeded. Detailed free tier breakdowns are consistently updated on the Mapbox pricing documentation.

Real-world cost examples

To illustrate the Mapbox GL JS pricing model, consider a few hypothetical scenarios:

Scenario 1: Small Blog with Interactive Map

• Usage: A blog post includes a single interactive Mapbox GL JS map to show event locations. The blog receives approximately 40,000 unique visitors per month, each viewing the map once.
• Map Loads: 40,000/month (each visitor views the map).
• Active Users: 40,000/month (assuming each visitor is a unique active user).
• Additional Services: No geocoding or directions used.
• Cost: Both map loads and active users fall within the 50,000 free tier limit. Therefore, the estimated cost for this scenario would be $0 per month.

Scenario 2: Medium-Sized Real Estate Listing Website

• Usage: A real estate website uses Mapbox GL JS to display property listings. It averages 80,000 map loads per month and has 60,000 unique active users interacting with the map features. The site also uses the Geocoding API for 5,000 searches per month.
• Map Loads: 80,000/month (exceeds free tier by 30,000).
• Active Users: 60,000/month (exceeds free tier by 10,000).
• Geocoding: 5,000 requests/month (within free tier of 100,000).
• Cost Calculation:
  • Map Loads: First 50,000 are free. Next 30,000 map loads in the 50,001-100,000 tier.
  • Active Users: First 50,000 are free. Next 10,000 active users in the 50,001-100,000 tier.
  • Geocoding: Free tier.
• Estimated Cost: Based on the Mapbox pricing page, the 50,001-100,000 tier for both map loads and active users starts at $50/month each. This implies a combined minimum cost of approximately $100 per month for exceeding both free tiers, potentially higher depending on exact per-unit pricing within that range.

Scenario 3: Large Fleet Management Application

• Usage: An application tracking a large fleet of vehicles uses Mapbox GL JS for real-time location display and routing. It generates 1,200,000 map loads per month, has 150,000 active users, and makes 200,000 Directions API requests monthly.
• Map Loads: 1,200,000/month.
• Active Users: 150,000/month.
• Directions API: 200,000 requests/month (exceeds free tier of 25,000).
• Cost Calculation: All services significantly exceed free tiers and fall into higher-volume discounted tiers. This scenario would involve complex calculations based on the detailed Mapbox pricing for each service, with per-unit costs decreasing at higher volumes.
• Estimated Cost: This level of usage would likely place the application into Mapbox's volume discount or custom enterprise tier. Without exact figures for higher tiers, a precise estimate is difficult, but it would involve several hundreds to thousands of dollars per month, depending on the exact pricing for each usage block. For comparison, similar high-volume usage on Google Maps Platform can incur costs upwards of $1,000-$5,000+ per month, indicating that Mapbox's per-unit costs for high volumes are competitive.

How the pricing compares

When evaluating Mapbox GL JS pricing, it's useful to compare it with other prominent mapping platforms and libraries:

• Google Maps Platform: Google Maps Platform also uses a pay-as-you-go model, with a significant free tier ($200 credit per month, covering approximately 28,000 dynamic map loads). After the free tier, Google's pricing can be higher per map load or API request compared to Mapbox's lower volume tiers. However, Google offers extensive global coverage and street view capabilities often at a premium. For high-volume usage, Google's pricing can scale rapidly, making direct cost comparisons complex without specific usage patterns.

• OpenLayers and Leaflet: These are open-source JavaScript libraries similar to Mapbox GL JS but do not provide hosted map tiles or services. They are free to use and do not have a direct pricing model. However, developers using OpenLayers or Leaflet typically need to source their map tiles (e.g., from OpenStreetMap, ArcGIS, or self-hosted tiles) and backend services (geocoding, routing) from other providers. These third-party services then introduce their own costs. For instance, using ArcGIS Platform's services with OpenLayers would incur ArcGIS-specific usage charges. Therefore, while the libraries themselves are free, the complete solution can still involve costs for data and services.

• Esri ArcGIS API for JavaScript: Esri's ArcGIS Platform, which includes the ArcGIS API for JavaScript, operates on a credit-based system. Users purchase credits that are consumed by various operations like geocoding, routing, and data storage. While the API itself is included with an ArcGIS subscription, the services consumed through it are metered. This model can be perceived as less transparent than direct usage-based pricing for some developers, but it provides an integrated ecosystem for GIS professionals. The ArcGIS Platform pricing is tailored to different user roles and organizational needs.

Mapbox GL JS generally offers competitive pricing, especially for projects that benefit from custom styling and vector tile performance. Its free tier is substantial for prototyping and smaller applications. For high-volume enterprise use cases, Mapbox's volume discounts and custom plans aim to compete with the total cost of ownership of other platforms, often requiring direct negotiation to find the most cost-effective solution.