For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

What Mapster WP Maps is, how it works, and what's new in V2.

Mapster WP Maps is a WordPress plugin for building interactive, fully customizable maps β€” directly from your WordPress admin. No coding required to get started, with extensive developer tools available when you need them.

How It Works

WP Maps has three layers that work together:

  1. The Mapmaker β€” a visual map editor that lives in your WordPress admin. This is where you configure everything: add features, style them, set up controls, and manage how your map looks and behaves.

  2. The WordPress Plugin β€” handles storing your map configuration, serving it to the frontend, and providing the shortcode you use to embed maps on any page or post.

  3. The SDK β€” a JavaScript library that runs in your visitors' browsers and renders the actual map using the mapping library of your choice.

As a regular user, you'll mostly be working inside the Mapmaker. The plugin and SDK handle everything else automatically.

Map Libraries

WP Maps supports three mapping libraries, each with different strengths:

Library
API Key Required
Best For

MapLibre

No

Free, open-source maps with no usage limits

Mapbox GL JS

Yes

High-quality styles, advanced features, satellite imagery

Google Maps

Yes

Familiarity, Street View, Google-native styling

You choose your library when creating or editing a map. Most features work across all three β€” any exceptions are noted in the relevant section.

Tip: If you're just getting started or don't need a specific mapping style, MapLibre is a great choice β€” it requires no API key and has no usage limits.

What's New in V2

V2 is a significant rewrite focused on a better editing experience:

  • New visual Mapmaker β€” replaces the old ACF-based editor with a purpose-built, real-time map editor. Changes preview live as you make them.

  • Unified editing interface β€” map settings, features, controls, and styles are all managed in one place.

  • Improved developer API β€” the old hooks system has been replaced with an event-based SDK. See the Developer section for details.

  • Same core functionality β€” all the features you know from V1 are still here. Only the interface has changed.

If you're upgrading from V1, see Upgrading from V1.

Last updated