Today we are releasing MapLibre-Geoman v0.7.0 and both Mapbox-Geoman Free v0.7.0 and Mapbox-Geoman Pro v0.7.0.

This release means teams that rely on Mapbox can now use the same Geoman editing workflows already used in Leaflet and MapLibre projects, without rebuilding their tooling.

What is new in 0.7.0

• Full Mapbox GL JS compatibility
• New @geoman-io/mapbox-geoman-free and @geoman-io/mapbox-geoman-pro packages (v0.7.0)
• Smoother interoperability for teams running mixed MapLibre and Mapbox deployments
• A new live Mapbox demo on geoman.io to validate behavior in a real app setup

How to think about the packages

The best framing is: free and pro packages with one shared core.

• @geoman-io/maplibre-geoman-pro targets MapLibre GL JS
• @geoman-io/mapbox-geoman-free targets Mapbox GL JS for free usage and is available on npm: @geoman-io/mapbox-geoman-free
• @geoman-io/mapbox-geoman-pro targets Mapbox GL JS for Pro workflows
• Both are built from the same Geoman repository and share the same editing core, with engine-specific adapters

Why this matters

Many teams maintain more than one mapping stack across products, customers, or regions. With v0.7.0, you can keep one editing experience while staying flexible on your rendering engine.

That reduces migration risk, avoids duplicate feature work, and keeps your geometry UX consistent for end users.

Try it now

• Open the new Mapbox demo
• Explore the MapLibre-Geoman docs
• Compare options on the pricing page

Looking ahead

We will keep improving cross-library behavior so you can build once and deploy confidently across Leaflet, MapLibre, and Mapbox-based products.

If you want help with rollout planning or migration strategy, contact us at [email protected].