
Maplibre Mapbox Migration
This walks you through swapping Mapbox GL JS for MapLibre GL JS: changing imports, dropping the access token, and most critically, replacing the style URL since mapbox:// sources won't work. The libraries share the same API from the 2020 fork, so most map code survives unchanged. The real work is picking a new tile source (OpenFreeMap for quick testing, then evaluate self-hosted or paid options) and migrating any custom Mapbox Studio styles by hand-editing the JSON to match your new tile schema. Covers what you gain (open source, no vendor lock, lower costs) and lose (Studio, hosted services, official support). Good reference if you're evaluating the switch or already committed to it.
- skills.sh installs
- 498
- GitHub stars
- 160
- last updated
- Aug 21, 2026
Install
$ npx -y skills add maplibre/maplibre-agent-skills --skill maplibre-mapbox-migration --agent claude-codeInstalls into .claude/skills of the current project.
Files
Mapbox to MapLibre Migration
This skill guides you through migrating an application from Mapbox GL JS to MapLibre GL JS. The two libraries share a common ancestry (MapLibre forked from Mapbox GL JS v1.13 in December 2020), so the API is largely the same. The main changes are: swap the package, replace the namespace, remove the Mapbox access token, and choose a new tile source (MapLibre does not use mapbox:// styles).
When to Use This Skill
- Migrating an existing Mapbox GL JS app to MapLibre
- Choosing tile sources and services after moving off Mapbox
Migration at a Glance
Work through these in order; each item has a numbered step below.
Sponsors
Details
- Repository
- github.com/maplibre/maplibre-agent-skills
- Category
- AI & Agent Building
- First seen
- Jun 3, 2026