WordPress map plugins: the whole category, explained
There are dozens of map plugins in the WordPress directory, and most of them are not competing with each other. They look like one category because they share a word. In practice they are four or five different products with different jobs, different data sources, and different reasons to exist, and the fastest way to be unhappy with a WordPress map plugin is to install one built for a job you do not have.
So before anything else, the routing. If you need a store locator, with dozens of pins, a distance search, and category filters, you want a dedicated store-locator plugin and you should skip to the section that names a few. If you need a shaded region map of US states or countries that reacts when a visitor clicks Kansas, that is a choropleth product and it is a different search entirely. Neither of those is what we make. Modern Maps is a map plugin, we build it, and this page will say plainly where it loses.
What follows is the whole category: how these plugins are built, what an API key commits you to, who the named players are, what separates them, what they cost, and a four-question way to pick one. The comparison is assembled from published feature lists, plugin directory listings, and pricing pages. Nobody here installed all nine and ran them side by side, and a page that implies otherwise is guessing at your expense.
What a WordPress map plugin actually is, and the three things they all differ on
Every map on every website is the same three parts stacked up. There is map data, meaning the roads, coastlines, place names, and building footprints. There is a renderer, meaning the code that turns that data into something you can pan and zoom. And there is a container, meaning the piece of your page the map sits inside. A WordPress map plugin is a wrapper that gets all three onto a page without you writing JavaScript.
Once you know that, the differences between plugins stop looking like a hundred feature checkboxes and start looking like three decisions.
Where the map data comes from. Some plugins call Google. Some call OpenStreetMap, the open data project that most non-Google maps on the web are built from. Some ship their own tiles. This decision drives almost everything downstream: whether you need an account, whether you get a bill, whether the map has Google’s business listings on it, and how the map looks by default.
How you place it on a page. A block, a shortcode, or a widget. This sounds like a detail and is not. It determines whether you configure the map while looking at it or in a separate admin screen, and it is the clearest signal of when the plugin was designed.
How much control you have over how it looks. This is the axis with the widest spread. Some plugins give you a basemap dropdown and nothing else. Some give you Google’s style JSON, which is powerful and miserable. A few let you steer the colors directly. Most people do not know they care about this until the map is on the page and looks like it belongs to a different website.
The two architectures: Google API plugins and self-contained plugins
Almost every difference in the category traces back to one split. A Google API plugin is a wrapper around the Google Maps JavaScript API: you supply an API key, Google supplies the map, and the plugin supplies the WordPress interface in between. A self-contained plugin ships its own map stack, so there is no account, no key, and no external console to configure.
The tradeoff is real in both directions. Google’s data is better than anyone else’s for business listings, Street View, and live traffic, and if you need those, nothing else will do. A self-contained plugin has a lower ceiling and no setup cost at all. That argument is worked through properly, with the plain iframe embed as a third option, in our comparison of the three ways to get a map onto a page. It is not repeated here.
Do you need an API key?
This is the highest-consequence decision on the page, because it is the only one that can send you a bill.
If you pick a Google-based plugin, the setup is roughly this. Create a Google Cloud project. Attach a billing account, with a real payment method, before anything will render. Enable the specific APIs your plugin asks for, usually the Maps JavaScript API and often the Places API and the Geocoding API as well. Generate a key. Restrict it to your domain, because an unrestricted key on a public page is a key anyone can copy and spend against. Paste it into the plugin’s settings. Then set a budget alert, because nothing else will tell you the map is costing money.
The billing model matters more than any specific number. Google Maps Platform is metered per request, there is a monthly allotment included, and past it you pay for what you use. The numbers move, so this post does not quote them; check Google’s current pricing page directly rather than trusting any figure printed in a blog post, including the ones printed confidently. What is worth internalizing is the shape of the risk. Your map costs nothing on a quiet contact page and costs something on a page that unexpectedly does well. That is a fine trade if you know it exists and an unpleasant surprise if you do not.
Restricting the key is the part people skip. An unrestricted key sitting in the page source of a public site is not a secret, and there are bots that scrape for exactly that. Domain restriction takes about ninety seconds and is the difference between a metered bill and someone else’s metered bill.
None of this applies to the self-contained plugins, which is the entire reason that category exists. We have written at length about why skipping the key is the whole point of the product, so the short version will do here: for a lot of sites the map is a contact page, the setup is the only hard part, and removing the setup removes the problem.
The landscape of WordPress map plugins, by install size
Here is the category as it currently stands, ordered by active installs. Every figure comes from each plugin’s own listing or pricing page, not from testing, and every figure has a date on it.
WordPress map plugins at a glance
Nine plugins, five columns that actually change your decision. Compiled from directory listings and published pricing pages, not from side-by-side testing.
| Plugin | Installs | Works without a key | Pricing model | Block editor |
|---|---|---|---|---|
| WP Go Maps | 300,000 | Leaflet mode only | Lifetime, $59 to $299 | Retrofitted |
| MapGeo (was Interactive Geo Maps) | 40,000 | Yes | $39.99/yr or $199.99 lifetime | Native |
| Leaflet Map | 30,000 | Yes | Free | Shortcode only |
| MapPress | 30,000 | Leaflet mode only | Annual, $39 to $79 | Retrofitted |
| Maps Widget for Google Maps | 30,000 | No | Lifetime, $39 to $79 | Retrofitted |
| Map Block for Google Maps | 20,000 | No | Free | Native |
| WP Map Block (aBlocks) | 20,000 | Yes | Free | Native |
| Open User Map | 10,000 | Yes | $39.99/yr or $279.99 lifetime | Native |
| Modern Maps | New listing | Yes | Free, or $29 to $99/yr | Native |
Three things worth reading out of that table.
Install count measures age more than quality. WP Go Maps has 300,000 installs because it has been in the directory since before the block editor existed. That is a genuine signal about stability and support, and it is not a signal about whether the plugin fits the site you are building today.
“Retrofitted” is doing real work as a label. Several of the largest plugins were built around a settings screen, then grew a block that mostly acts as a placeholder pointing at a map you configured somewhere else. It works. It also means you cannot see what you are changing while you change it.
Our own row needs the asterisk. “Modern Maps” in that table is two separate downloads. Modern Maps Lite, the WordPress.org listing, has no marker limit and never has. The build you download from modernmapswp.com is the commercial one, and it adds two markers before it asks for a license key. They are not a free tier and a paid tier of the same plugin, they are two plugins, and anyone telling you “the free version is capped at two markers” has flattened that into something false.
The features that actually separate them
Feature lists in this category run to a hundred bullets and most of them are the same six things renamed. These are the ones that genuinely determine which plugin you should install.
Store locators. A search field, a radius, a results list, and a map that filters as you type. This is the single most-wanted feature in the category and it is a real product on its own. WP Go Maps, MapPress, and WP Maps Pro all build around it. Modern Maps has none of it: no search field, no radius, no filtering. If this is your requirement, stop reading comparisons and go pick between those three.
Marker clustering. When two hundred pins collapse into a numbered circle that splits apart as you zoom in. Anything selling itself for large datasets has it. Modern Maps does not, and the honest reason is that it was built for maps with a handful of markers, where clustering would never fire.
Data import. GeoJSON, KML, and CSV, so your locations can live in a spreadsheet instead of in a page. This is what separates “a map with some pins on it” from “a map driven by a dataset”. Maps Marker Pro and the store-locator products handle it. Modern Maps does not import anything; markers are blocks you place by hand.
Directions and routing. Turn-by-turn, travel time, a directions panel. This needs a routing engine, and in practice that means Google, which means an API key. Any plugin offering it without one is sending you to an external service.
User submissions. Visitors add their own locations to your map. Open User Map is built entirely around this and does it better than the general-purpose plugins bolt it on.
Region and territory maps. Shaded countries, states, or sales territories, usually SVG rather than a real slippy map. MapGeo (listed until recently as Interactive Geo Maps) and MapSVG own this. It is a data visualization tool wearing a map costume, and it is a different product from everything else on this page.
Design control. The axis nobody markets on. Most plugins offer a basemap dropdown and stop. Google-based plugins expose Google’s style JSON, which can do a lot and is unpleasant to author by hand. This is the one column where Modern Maps is deliberately the strongest option in the table, and it is also the reason it is missing so many of the rows above.
How a map gets onto a page in 2026
Three mechanisms, and which one a plugin uses tells you roughly what year it was designed.
Blocks. The current answer. You add a block, the map appears in the editor, and you change settings in the sidebar while watching the map respond. Everything published after 2019 either uses blocks or has been retrofitted with one. WordPress documents the whole system in the Block Editor Handbook if you want the underlying model.
Shortcodes. The pre-block answer, and still the only mechanism some plugins offer. You configure the map in an admin screen, the plugin gives you [map id="3"], and you paste that wherever you want it. It is portable and it works anywhere, including inside page builders and theme templates. What you give up is seeing the map while you build it.
Widgets. The oldest mechanism, from when sidebars were how WordPress sites were assembled. Since WordPress 5.8 the classic widget areas accept blocks, which means “widget” now usually means “a block in a sidebar” rather than a registered widget class. A handful of older plugins still ship a true widget, and if your site depends on one you should check for it by name rather than assuming.
The practical version: if a plugin’s marketing screenshots show a settings page rather than a map, expect to configure it in a settings page.
What map plugins cost
Free is a real option in this category and not a trap. Leaflet Map, WP Map Block, and Map Block for Google Maps are free outright. What free usually means here is fewer markers per map, no styling beyond a preset, and support that consists of a forum thread.
Above free, the category splits into two bets that are often compared as if they were the same purchase.
Lifetime licenses, in the $39 to $299 range, are the dominant model at the top of the market. WP Go Maps sells only this way. The pitch is obvious and the risk is the one nobody prints on the pricing page: a lifetime license is a bet that the plugin will still be maintained in five years, funded by a revenue stream that stopped when you paid. Plenty of lifetime plugins are still going strong. Some are not, and a map plugin that stops getting updates is a plugin that eventually breaks against a WordPress release.
Annual subscriptions, usually $29 to $99 a year, are the other bet. You pay every year, which is worse, and in exchange the maintenance is funded by people who are still paying, which is better. Renewals usually gate updates and support rather than the plugin itself, so a lapsed subscription normally leaves your maps working.
Neither model is the honest one. They are different bets about the same risk, and the right one depends on whether you would rather pay for continuity or gamble on it.
A separate line item, easy to forget: if your plugin is Google-based, the license is not the whole cost. The Maps Platform bill is metered and it sits underneath whatever you paid for the plugin.
Where Modern Maps fits, and where it does not
Modern Maps is a block-native, self-contained map plugin with no API key and a strong bias toward the map looking like it belongs on your site. That is the entire product.
It fits when the map is part of the design. A contact page, a venue, a studio, a trip, a small set of locations that should pick up your palette instead of arriving in Google’s blue and beige. It ships three presets (Light, Dark, and Standard), alignment and height controls that take any CSS unit, a viewport that either fits itself to your markers or holds a fixed position with a zoom slider from 1 to 20, address search in the editor, and marker popups built from ordinary blocks, so a popup can hold an image, a heading, and a button. There are twenty-four preset examples in the gallery if you would rather look than read.
It does not fit, and here the list is longer, when you need a store locator, marker clustering, GeoJSON or KML or CSV import, directions or routing, region and choropleth maps, custom marker images (marker styling is color, and only color), a shortcode, a registered WordPress widget, page builder integrations for Elementor or Divi or Beaver Builder, or WPML and Polylang support. None of those exist, none of them are half-built, and every one of them has a better home named earlier on this page.
One more limitation worth stating out loud, because nobody in this category states theirs: the map needs WebGL. A visitor whose browser has WebGL disabled, which is a real if small population on hardened and privacy-focused setups, gets an empty container rather than a fallback image. That is a known gap, not a design decision.
If that description matches the map you actually need, download Modern Maps for free and try it on a draft page. It installs like any other plugin and commits you to nothing.
Modern Maps Pro is the same download with a license key pasted in, so there is no reinstall and no migration. The key adds exactly three things: markers above two, nine OKLCH color controls that steer the map’s base lightness, chroma, and hue along with the bounds and drift that produce its gradient, and theme-palette and marker colors that persist instead of being discarded when you change them. Plans are annual or monthly, for one, five, or twenty-five sites, and are listed on the plans page. There is no lifetime option.
Common questions, answered honestly
Is there a shortcode? No. Modern Maps ships three blocks and nothing else. If you need a shortcode, because you are placing maps inside a page builder or a theme template, Leaflet Map, WP Go Maps, and MapPress all provide one.
Is there a WordPress widget? Also no. All three blocks appear under the Widgets heading in the block inserter, which is a block-inserter category and not the same thing. There is no register_widget call anywhere in either build. In practice the block can usually go in a sidebar anyway, because modern WordPress widget areas accept blocks, but there is no classic widget to fall back on if yours does not.
Does it work with Elementor, Divi, or Beaver Builder? There is no integration. Some builders can render arbitrary blocks and some cannot, and we have not tested them, so the honest answer is to check with a test page before committing.
Does it work with WPML or Polylang? No integration exists. Marker popups are regular blocks, so whatever your translation setup does with block content it will do with them, but nothing is built for it.
Can you use your own marker images? No. Marker styling is a color. Not an icon, not an uploaded PNG, not a numbered pin. If your map needs branded pins, this is the wrong plugin and you want one of the Google-based products.
How many markers can you add? It depends on which build you installed, and this is the one thing worth getting right. Modern Maps Lite from WordPress.org has no marker limit. The build downloaded from modernmapswp.com allows two, then asks for a license key. One detail people appreciate: the limit only trims markers added during the current editing session. A page built with a license and later opened by someone without one keeps every marker it already had. The limit is a purchase prompt, not something that eats your content.
What happens if a visitor has WebGL turned off? They get an empty container where the map should be. There is no static image fallback yet.
Can it map US states or countries and shade them by value? No. That is a choropleth, and MapGeo or MapSVG is what you want.
Is a Google account needed for anything? No. Address search in the editor uses Komoot Photon, an OpenStreetMap-based geocoder, and it runs only while you are editing. Published pages never call it.
How to choose, in four questions
Work down the list. The first yes is your answer.
- Does your map need Google’s own data? Street View, business listings and reviews, live traffic, turn-by-turn directions. If yes, you need a Google API plugin and an API key, and the rest of this list does not apply. Budget an hour for the Cloud Console and set the billing alert.
- Is it a store locator? More than a dozen locations, a search box, a distance radius, category filters. If yes, you need a dedicated store-locator product. WP Go Maps, MapPress, and WP Maps Pro are the established options. General-purpose map plugins, ours included, will waste your afternoon.
- Is it a region map? Shaded states, countries, counties, or sales territories that respond to a click. If yes, it is a data visualization, not a street map, and MapGeo or MapSVG is the category.
- Everything else: does the map need to look like part of your site? If yes, a self-contained block plugin, which is where Modern Maps sits. If you genuinely do not care how it looks and there is one location, a plain Google iframe embed is free and takes five minutes, and you do not need a plugin at all.
Most people land on four. Question four is also the only one where the answer is a matter of taste rather than a requirement, which is why it comes last.
Where to go next
If you want a shortlist with an actual recommendation attached rather than a full landscape, our ranked picks by job takes seven common jobs and names one plugin for each, including the four where the answer is not us.
This page is maintained rather than published and forgotten. The figures in the card carry a date because they will go stale, and the date is there so you can tell how much to trust them. If you find one that has drifted, the fastest way to get it fixed is to say so.