How it works
Mapbox serves vector tiles built largely from OpenStreetMap plus its own data, and its libraries (Mapbox GL JS on the web, native SDKs for Android and iOS) draw them on the device with WebGL. Maps can rotate, tilt and zoom smoothly, show 3D buildings and terrain, and take on any look designed in Mapbox Studio, from brand colours to hiding every label except roads. Geocoding, search, directions, matrix and navigation APIs cover the rest.
Billing counts web map loads (each time a map starts up on a page) and monthly active users in mobile apps, with large free allowances. Since version 2, Mapbox GL JS has used a proprietary licence and needs a Mapbox account even when showing other tiles; the community fork MapLibre GL JS stays open source and works with any vector tile provider.
Mapbox pros and cons
Pros
- Complete control over the map's look in Mapbox Studio
- Smooth vector maps with 3D terrain and buildings
- A larger free web allowance than Google Maps
- Well suited to drawing large datasets on a map
Cons
- Places and business data is thinner than Google's
- The proprietary SDK licence ties maps to a Mapbox account
- Many separately priced APIs make bills harder to predict
When to use Mapbox
Pick it when
- Maps that must match a brand or product design
- Dashboards, fleet tracking and data layers on a map
- Mobile apps with offline maps or turn-by-turn navigation
Skip it when
- Searching local businesses and points of interest is the core feature
- The stack must be open source end to end (MapLibre fits that)
Mapbox pricing
Pay as you go
Free each month: 50,000 web map loads, 25,000 mobile users and 100,000 geocoding requests. Then about $5 per 1,000 map loads and $4 per 1,000 mobile users, falling with volume.
Mapbox pricing page (opens in a new tab)Approximate, checked September 2026.What the other tools cost
Mapbox vs the alternatives
Related terms
More in Maps and location
Map providers