Mapbox vs MapLibre Explained

This article continues the Web Mapping & Tile Systems sub-hub with critical developer context: the license-driven fork that reshaped the web-mapping ecosystem in late 2020.

The Mapbox era (2010–2020)

Mapbox was founded in 2010 by Eric Gundersen and Will White, originally as a tile-rendering service built on OpenStreetMap data. Through the 2010s the company:

• Released Mapbox Studio (style design), Mapbox Streets (vector tile schema), Mapbox Satellite (imagery), and various enterprise products.
• Open-sourced Mapbox GL JS in 2014 — the WebGL- based renderer that established client-side vector tile rendering as a viable production pattern.
• Open-sourced Mapbox GL Native for iOS and Android.
• Open-sourced the Mapbox Style Specification (the JSON-based style format).
• Published the Mapbox Vector Tile (MVT) spec as open source.

Through 2020, Mapbox GL JS versions 1.x were released under the BSD-3 Clause license — a permissive open-source license allowing free use, modification, and redistribution with attribution.

The library was the dominant choice for production web-mapping in the 2015–2020 era. Adoption included GitHub (used in profile views), Foursquare, Instagram, Snapchat, Pokemon Go, the New York Times, USA Today, and many others. The success of Mapbox GL JS proved that client-side vector rendering at scale was practical.

The license change (December 2020)

On December 7, 2020, Mapbox released Mapbox GL JS v2.0. The release notes announced a substantial license change: v2.0 and later are released under a proprietary license requiring a Mapbox account and API access token.

Specific changes:

• Required Mapbox account: applications using Mapbox GL JS 2.0+ must register with Mapbox and use an access token in every map initialization.
• Usage tracking: Mapbox can track and bill based on map loads via the token.
• Terms of Service: covered by Mapbox's TOS, which restricts certain uses (showing competitor data, certain enterprise applications).
• No source modification: clauses prevent forking and redistribution.

Mapbox stated the change was driven by the substantial investment in v2.0's new features (globe rendering, 3D terrain integration, performance improvements) and the need to capture revenue from that investment.

The community reaction was strongly negative. Mapbox GL JS had been a critical open-source dependency for many large-scale map services; overnight conversion to proprietary forced consumers to choose:

1. Accept the new TOS and pay Mapbox.
2. Stay on v1.x and forgo updates.
3. Switch to a different library (Leaflet, OpenLayers).
4. Fork v1.x and continue open development.

Option 4 became the basis for MapLibre.

The MapLibre fork (December 11, 2020)

Just four days after Mapbox v2.0's release, MapLibre GL JS launched on December 11, 2020. The key facts:

• Forked from Mapbox GL JS v1.13 — the last BSD-3 release.
• Continuing BSD-3 license for all future work.
• Initial contributors: MapTiler (the driving force), Microsoft, Stadia Maps, AWS, Apple, Esri, and many individual developers.
• Governance through OSGeo — the Open Source Geospatial Foundation, an established neutral home for open-source GIS projects.

The MapLibre branding emphasized open governance and vendor independence — a deliberate contrast to the perception of single-vendor lock-in that Mapbox v2 represented.

MapLibre's announcement was widely covered in technical media: TechCrunch, Hacker News (front page multiple times), industry blogs (Stamen Design, MapTiler, FOSSGIS). The fork was framed as a defensive response by the geospatial industry to vendor risk.

MapLibre's evolution

MapLibre has continued active development since 2021. Key releases:

MapLibre GL JS 1.x (2021)

The initial release: API-compatible drop-in replacement for Mapbox GL JS 1.x. Migration was a single import change for most projects.

MapLibre GL JS 2.x (2021–2022)

Modernized internal architecture; deprecated some legacy APIs; performance improvements.

MapLibre GL JS 3.x (2022–2023)

Added new features: 3D terrain (matching Mapbox v2 functionality), fog and atmospheric rendering, performance improvements for large feature counts.

MapLibre GL JS 4.x (2023–2024)

Modernized build system, TypeScript types, improved mobile performance. Stricter style-spec adherence.

MapLibre GL JS 5.x (2024–present)

Globe rendering added (matching the Mapbox v2.0 flagship feature). The library now supports both flat-Mercator and globe-orthographic views with seamless transitions.

The library is production-ready and is the de-facto standard for vector-tile rendering in open-source web mapping.

Backers and ecosystem

MapLibre has substantial industry backing:

Apple

Apple Maps Server contributed its MapLibre-based renderer in 2022. Apple uses MapLibre for some server-side rendering of Apple Maps content. Apple contributors have made substantial performance and feature contributions.

AWS

AWS Location Service is built on MapLibre. AWS has dedicated engineers contributing to the project since 2021. AWS's map products are MapLibre- compatible and integrate with the AWS billing ecosystem.

MapTiler

The most active commercial contributor. MapTiler has multiple full-time engineers on MapLibre and provides MapLibre-compatible tile services. The MapLibre browser sandbox and many examples are hosted by MapTiler.

Stadia Maps

A tile-service company specifically created to provide an open-source-friendly alternative to Mapbox. Active MapLibre contributor.

Microsoft

Bing Maps and Azure Maps have shifted toward MapLibre-compatible products. Microsoft contributors have added several features and bug fixes.

Esri

The ArcGIS company has open-source map-rendering products built on MapLibre. Esri provides enterprise GIS integrations.

Smaller contributors

Independent developers, smaller GIS companies, and academic researchers contribute regularly. The contributor base is broader than most open-source projects of similar scope.

OSGeo governance

Project governance is through the Open Source Geospatial Foundation. A steering committee (elected by contributors) makes architectural decisions; smaller technical decisions go through standard GitHub pull-request review. The neutral governance is a deliberate contrast to single-vendor control.

API compatibility

For most use cases, MapLibre GL JS is a drop-in replacement for Mapbox GL JS 1.x.

Migration steps

A typical migration is one import change:

- import mapboxgl from 'mapbox-gl';
+ import maplibregl from 'maplibre-gl';

- mapboxgl.accessToken = 'pk.abc123...';
- const map = new mapboxgl.Map({ ... });
+ const map = new maplibregl.Map({ ... });

The Map constructor, layer management, event handlers, and style spec are identical for Mapbox GL JS 1.x-equivalent functionality. No access token is needed (depending on the tile source — non-Mapbox tile services typically have their own authentication).

What doesn't transfer

• Mapbox-specific telemetry: Mapbox collected usage analytics; MapLibre doesn't.
• Mapbox-required access tokens: not needed with MapLibre + a non-Mapbox tile source.
• Mapbox v2.0+ features in their proprietary form: globe view (until MapLibre 5), some advanced 3D rendering, certain Mapbox-only style spec features.
• Mapbox API integration: Geocoding, Directions, Static Images, etc. — these are Mapbox-specific services. Replace with alternatives (Mapbox API → MapTiler / Stadia / Geoapify; Mapbox Tilesets API → self-hosted).

Style spec compatibility

Both libraries consume the Mapbox Style Specification (which remained open even after the v2.0 license change). A style JSON file works in either library. Some style-spec extensions are library-specific:

• Mapbox-specific layers (sky with v2 features, certain building-3d extensions): may not render identically in MapLibre.
• MapLibre extensions (newer projection support, some performance hints): not supported by Mapbox GL JS.

For maximum portability, stick to the documented common subset.

Mobile native libraries

Both projects have native (iOS / Android) renderers:

Mapbox Maps SDK

Proprietary, requires Mapbox account. Tight integration with Mapbox commercial services.

MapLibre GL Native

Open-source BSD-3 (forked from the older open-source Mapbox GL Native), maintained by the same MapLibre contributor community. Used by many open-source mobile apps.

Migration between the two on mobile is more complex than on web because Mapbox v2's native SDK has diverged more from the v1.x baseline. New mobile projects that want open-source default to MapLibre Native.

Trade-offs and choice

When to use MapLibre

• Open-source preferred (license, governance).
• Vendor-neutral tile source (MapTiler, self- hosted, OSM-based).
• Cost-sensitive projects (no per-map-load Mapbox billing).
• Indefinite maintenance horizon (BSD-3 ensures fork-ability if MapLibre ever goes away).
• Custom branding (no Mapbox attribution requirement; attribution still required for the tile data source).

When to use Mapbox v2+

• Already on Mapbox with significant integration investment.
• Need Mapbox-specific features (some advanced 3D, certain Mapbox commercial integrations).
• Mapbox commercial services dependency (Mapbox geocoding, directions).
• Want vendor support (Mapbox commercial support beats community-only).

What we use

Coordinately uses MapLibre (per CLAUDE.md §3), together with MapTiler tile sources. The choice reflects:

• Open-source license alignment with the project's open philosophy.
• No vendor lock-in risk.
• Active development trajectory.
• MapTiler tiles are MapLibre-compatible.

Notable migrations

Several major services switched from Mapbox to MapLibre after the 2020 license change:

• Apple Maps Server (2022).
• AWS Location Service (early 2021).
• Microsoft Azure Maps (gradual migration).
• DuckDuckGo Maps (uses Apple Maps internally with MapLibre).
• Wikimedia Maps (Wikipedia's map service).
• Snapchat (some endpoints).
• Many smaller services.

Mapbox retained customers who valued the v2+ features and were already invested. The market is now competitive between Mapbox (proprietary, feature-rich) and MapLibre (open, vendor-neutral).

Style spec governance

The Mapbox Style Specification is technically maintained by Mapbox but is functionally open:

• Published openly at docs.mapbox.com/style-spec.
• The reference implementation in Mapbox GL JS v2+ is proprietary; MapLibre GL JS's implementation is open.
• The spec is de-facto standard for vector-tile rendering across the industry.
• MapLibre extends the spec for its specific features (e.g., custom projections).

For long-term compatibility, styles should target the documented common subset of the spec.

Common misconceptions

“MapLibre is a clone of Mapbox.” It's a fork of Mapbox GL JS 1.13 — the last BSD-3 release. Subsequent development has diverged, with MapLibre having a different focus (open governance, no telemetry, broader projection support planned) than Mapbox v2+. The two have grown apart since the 2020 fork.

“Mapbox is dying.” It's not. Mapbox continues to be a major commercial provider with substantial revenue. The license change broadened the market for open-source alternatives but didn't kill Mapbox.

“MapLibre is for hobbyists; serious production uses Mapbox.” Apple Maps Server, AWS Location Service, Microsoft, and many other production services use MapLibre. Production-grade backing is one of MapLibre's strengths.

“The fork was hostile.” It was a business-forced fork rather than a hostile one. Mapbox's license change was a legal action by Mapbox; the fork was the open-source community's permitted response under the original BSD-3 license. Mapbox and MapLibre coexist; some engineers have contributed to both.

“MapLibre requires no migration cost.” For Mapbox GL JS 1.x users: minimal cost (one import change). For Mapbox v2+ users: meaningful cost (feature substitution, API replacement, tile-source change).

“The Mapbox Style Spec is closed.” The spec is open; the v2+ implementation (Mapbox GL JS) is proprietary, but the underlying JSON specification is published openly and is implemented by multiple libraries (MapLibre GL JS, several other renderers).

“Mapbox vector tiles are proprietary.” The MVT format spec is open (BSD-3). Mapbox's specific tile content (Mapbox Streets style data) is commercial, but you can use Mapbox-compatible vector tiles from any provider with MapLibre GL JS.

“Globe view requires Mapbox v2+.” Not anymore — MapLibre GL JS 5 (2024) added globe rendering. The feature gap that motivated some v2+ users to stay on Mapbox has narrowed.

“MapLibre is mobile-only.” No — the primary MapLibre product is MapLibre GL JS for web. MapLibre GL Native is a separate mobile project sharing the same governance and ecosystem.

“Mapbox v2+ is free for development.” Mapbox offers a free tier (50,000 map loads/ month at the time of writing) but the license itself requires registration and TOS acceptance regardless of cost. MapLibre is licensed under BSD-3 with no registration requirement.

“Migration from Mapbox v2 to MapLibre is trivial.” Migration from v1.x is trivial. Migration from v2+ requires more work, especially if v2-specific features are used. Plan time proportional to v2-feature usage.

“The fork solved the open-source map problem permanently.” Probably — the breadth of MapLibre's backers and OSGeo governance make a re-closure unlikely. But the broader lesson stands: depending on a single-vendor library means accepting whatever license they choose. Open governance is a durable property only if maintained.