Dynmap
Real-time web-based map of your Minecraft world. Renders an interactive Google Maps-style view players can browse.
World ManagementWhat is Dynmap?
Dynmap renders your Minecraft world as a live, browsable web map — a Google-Maps-style view of the terrain that anyone can open in a browser, with player markers updating in real time. It supports flat, isometric and surface render modes, custom markers and region overlays (it can draw WorldGuard or Towny boundaries), and two-way chat between the web and the game. It serves the map either through its own built-in web server on a configurable port or through your existing web server. It is the long-standing classic for giving a public, always-on view of a server's world.
Who it's for: Public servers wanting an always-online world map for players and prospective players, and admins who want to watch player positions and claimed regions from a browser. It is built and maintained by mikeprimm and sits in the world management category.
Key features of Dynmap
- Web-based world map
- Real-time player positions
- Multiple render modes
- Custom markers
- Region overlay
- Chat integration
- HD map support
- Multiple world support
How to install Dynmap
Dynmap runs on Bukkit, Spigot or Paper servers. mikeprimm maintains Dynmap for current Spigot/Paper versions with broad backward compatibility; it is one of the most version-resilient mapping plugins.
- 1Stop your server, or have it ready to restart. Always back up your world and plugins folder before adding a new plugin.
- 2Download Dynmap.jar (a build matching your server version) and place it in your server's /plugins folder.
- 3Dynmap has no required dependencies, so it runs on its own once the jar is in place.
- 4Start the server fully. Dynmap generates its configuration files on first launch — stop the server, edit them to taste, then start again.
- 5Confirm it loaded by checking the console for Dynmap on startup, or by running one of its commands in-game.
Note: Drop Dynmap into /plugins and restart; it begins rendering and serves the map on its internal web server (port 8123 by default) unless you configure it to use an external one. Open that port to make the map public. Initial full renders are CPU and disk heavy, so trigger /dynmap fullrender during quiet periods.
Dynmap commands and permissions
Main commands
/dynmap render- Renders the area around you, useful for refreshing a small changed region.
/dynmap fullrender- Renders an entire world (or a radius) to build or rebuild the map tiles — resource intensive.
/dynmap hide- Hides a player from the live map for privacy.
/dynmap show- Reveals a previously hidden player on the map.
Permission nodes
dynmap.render- Allows local area renders.
dynmap.fullrender- Allows triggering full-world renders; staff-only as it is heavy.
dynmap.hide- Allows hiding players from the map.
Dynmap FAQ
How do I view the Dynmap?
Dynmap serves a web page on port 8123 by default, so you open http://your-server-ip:8123 in a browser. Make sure that port is open on your host. You can also configure Dynmap to run behind your existing web server on a normal port or subdomain.
The map is blank or incomplete. Why?
The world has not been fully rendered yet. Run /dynmap fullrender <world> to build all the tiles — this can take a long time and uses significant CPU and disk, so do it during low activity. After the initial render, Dynmap updates changed areas automatically as players play.
Can I hide certain players or areas?
Yes. /dynmap hide <player> removes a player marker from the live map (and /dynmap show reverses it). You can also configure worlds or regions to be hidden or rendered with limited detail, which is common for hiding the End or staff areas.
Does Dynmap show WorldGuard or Towny regions?
Yes, via its add-on integrations. Dynmap-WorldGuard and Dynmap-Towny draw those claims as overlays on the map. Install the matching integration plugin and the boundaries appear, letting players see claimed land and town borders from the browser.
Is Dynmap heavy on performance?
Ongoing updates are light, but full renders are CPU and disk intensive because they generate many image tiles. Schedule large renders for quiet times, consider limiting render detail or worlds, and ensure you have disk space for the tile cache. Day-to-day live updating is generally inexpensive.
Features
- Web-based world map
- Real-time player positions
- Multiple render modes
- Custom markers
- Region overlay
- Chat integration
- HD map support
- Multiple world support
Commands
/dynmap render/dynmap fullrender/dynmap hide/dynmap show/dynmap statsPermissions
dynmap.renderdynmap.fullrenderdynmap.hidedynmap.showdynmap.stats