Dynmap is one of the most powerful and popular plugins available for Minecraft server owners. It transforms your server into an interactive, Google Maps-style experience — fully viewable in any web browser, in real time. Whether you want to track players, explore your world from above, or share your server’s map with the community, this step-by-step guide will walk you through everything you need to enable and configure Dynmap on your Minecraft server.
Before installing Dynmap, make sure your server is running Paper, Spigot, or Bukkit — Dynmap does not work on vanilla Minecraft servers. Once confirmed, download the latest Dynmap .jar file from the official SpigotMC page or CurseForge, making sure it matches your current Minecraft version. Upload the .jar file to your server’s /plugins folder via FTP or your hosting panel’s file manager, then restart your server. Dynmap will automatically generate its configuration files inside /plugins/dynmap/.
Dynmap requires its own dedicated port to run its built-in web server. By default, it uses port 8123. If you are on a managed hosting provider, you will need to allocate an additional port through your server panel. Open the Dynmap configuration file at /plugins/dynmap/configuration.txt, then set the webserver-port field to your newly assigned port. Save the file and restart your server to apply the changes.
Once your port is configured, open configuration.txt to fine-tune your Dynmap setup. Key settings to adjust include: deftemplatesuffix (set to lowres or vlowres to reduce storage usage), the worlds to render such as Overworld, Nether, and End, map styles including flat, surface, cave, or 3D isometric views, and player visibility controls. For HD quality maps, you can enable ‘deftemplatesuffix: hires’, though this will consume significantly more disk space. Always save the file and reload Dynmap after making changes.
After saving your configuration, start your server and trigger the first full map render. Use the in-game command /dynmap fullrender or type dynmap fullrender WORLDNAME directly into the server console. The map will begin rendering gradually — progress messages will appear in your console confirming that Dynmap is working. Be aware that a full render can be CPU and RAM intensive, so it is best to run it during off-peak hours or low-traffic periods.
Once the render is underway, open your browser and navigate to http://YOUR-SERVER-IP:PORT to view your live Dynmap. You should be able to see your world updating in real time, including player positions, current in-game time, and weather. If you see a black background at first, do not worry — the map will fill in progressively as chunks are rendered. You can also use /dynmap radiusrender for smaller, targeted area renders to save resources.
Dynmap supports a rich set of add-ons and integrations to extend its functionality. You can connect it with plugins like WorldGuard, Towny, Residence, and Factions to display protected regions and territories directly on the map. The dynmap-mobs add-on provides a real-time marker layer showing selected mob positions. Additional features include chat balloons, web-to-game chat, and fully configurable markers, areas, and custom lines — all manageable through the component configuration files.
If players are not appearing on the map, check the visibility settings in configuration.txt and ensure players have the dynmap.show.self permission, or have them run /dynmap show. For performance issues, consider switching to SQLite storage instead of filetree, reducing the deftemplatesuffix resolution, or limiting the number of concurrent render threads. If you own a custom domain, you can also set up a reverse proxy to access your Dynmap via a clean URL without exposing a port number.