Guides Showing a live map of your Minecraft server in a browser takes a plugin such as Dynmap, BlueMap or squaremap, installed on a Paper, Spigot or Fabric server, plus a web port opened so it can be reached from outside. Expect 10 to 20 minutes to get a first visible map, and a bit of extra RAM (300 to 600 MB depending on world size) during the initial render. None of these three plugins costs anything: the real difference is the rendering style (2D or 3D) and the load at startup.
Why show your server's map
A live map gives players an immediate point of reference: where their friends' bases are, which areas are still unexplored, where to settle without overlapping a neighbor. On a community server or a small group of friends, that is often the difference between a world that stays alive and one where nobody knows where to go anymore. On the admin side, the map also helps spot overbuilt areas at a glance, a lag spot (lots of entities or redstone in one place), or an abandoned base to clean up.
It also saves a lot of back and forth in chat or on Discord: instead of describing coordinates by hand, a player can just point at a spot on the map. On a server that has been running for months, the map becomes the easiest way to see how much of the world has actually been explored, and where it is still worth venturing out.
Dynmap, BlueMap or squaremap: which one to pick
All three do fundamentally the same thing, a live web map with connected players shown on it. What changes is the rendering, the load on the server, and how easy it is to configure.
| Plugin | Rendering | Startup load | Compatibility | Strengths |
|---|---|---|---|---|
| Dynmap | 2D (top down view) | High on a large world | Paper, Spigot | The oldest, extensively documented, advanced markers and zones |
| BlueMap | 3D (real perspective, zoom, rotation) | Moderate, progressive rendering | Paper, Spigot, Fabric | Impressive rendering, modern interface, light once the map is generated |
| squaremap | Minimalist 2D | Low, built to stay unobtrusive | Paper, Fabric | Very little RAM/CPU in continuous use, ideal on a small server |
In practice: BlueMap for the wow factor and a real 3D map, Dynmap if you want detailed markers and zones backed by a huge library of resources, squaremap if the priority is keeping performance untouched. On a small server with friends (under 10 players, a world of a few thousand chunks), all three are fine. On a busier server, a community survival world with dozens of players and a world already well explored, squaremap's lightness or BlueMap's progressive rendering stand out more than Dynmap, which is heavier during a full render. All three run comfortably on the Plugins plan (€8.99/month, 12 GB of RAM, 6 vCPU), plenty for a typical world with a handful of players.
Installing the plugin on your server
From the panel, the Files tab or the Plugins tab, which searches Modrinth and SpigotMC directly: look up "Dynmap", "BlueMap" or "squaremap", install it in one click, or drop the downloaded .jar into the plugins/ folder. A server restart is enough to activate it. On first startup, the plugin creates its configuration folder (plugins/dynmap/, plugins/BlueMap/ or plugins/squaremap/) and starts rendering the map in the background: that initial render is what uses a bit more RAM and CPU while it goes through already explored chunks. On an older world with several thousand generated chunks, that first full render can take anywhere from a few minutes to several hours; player connections keep working normally the whole time. Our guide on essential Minecraft server plugins covers how to organize your plugins/ folder beyond just the map.
Opening the map's port from the panel
By default, your Minecraft server only exposes a single port (the one used to connect to the game). To make the map reachable from a browser, you need an extra port: the Ports section of the Advanced tab in the panel exists for exactly that, for a web map (BlueMap, Dynmap) or Geyser. Steps to follow:
- In the panel, open the relevant server, Advanced tab, Ports section.
- Click "Request a port": the request goes into a queue, processed within a few minutes by the system, no restart needed on your end for that part.
- The assigned port shows up in the panel and is emailed to you. Only one request can be pending at a time per server, and there is a maximum number of ports per server depending on your plan.
- Put that port number into the plugin's configuration file (
config.txtfor Dynmap,core.conffor BlueMap,config.ymlfor squaremap, theportorweb-server-portkey), then restart the server. - The map is then reachable at your server's address followed by that port, for example
http://your-address:8123.
To release a port you no longer need, the server has to be stopped first: Pterodactyl keeps the port reserved as long as it is running, that is a technical constraint of the hosting system, not a limit we added.
HTTPS and reverse proxy for the map
The port opened by the panel serves the map over plain HTTP, which is enough for use between players. For a clean HTTPS link through a domain name, you need a reverse proxy (Nginx, Caddy) pointed at your server's IP and port, hosted on your own side: that is not something the panel automates today. For everyday use between friends or a small community, a direct HTTP link with the port is enough and skips this step entirely. If you do want a proper domain (for example map.yourdomain.com) over HTTPS, the principle stays the same with Caddy or Nginx: a configuration block that forwards that subdomain to your server's IP and port, with a certificate issued automatically by Caddy. This step happens on a machine or service you control, the panel does not automate it today. It is worth doing only once you already have players checking the map regularly: for a brand new server, the plain HTTP link is a better starting point, and the reverse proxy can be added later without touching the plugin's own configuration.
What about the Modpack plan's built-in map
The live Minecraft map page presents a Livemap built for the Modpack plan. If you are on a different plan, or you simply want a self-hosted, customizable web map right away, the most reliable route today remains the manual install described above (BlueMap, Dynmap or squaremap as a plugin), which already works on any Paper, Spigot or Fabric server on the Plugins plan.
Frequently asked questions
Which port should I open for the map?
The one assigned through the Ports section of the Advanced tab in the panel (see above), to be entered in the plugin's configuration. It is never the game port (25565 by default), always a separate one.
How do I share the map link with my players?
Give them your server's address followed by the assigned port, for example http://your-address:8123. A clickable link in your Discord description or the server's MOTD saves re-typing it every time.
Why isn't my map updating?
Dynmap and BlueMap only recompute the areas that change (a full render aside). If nothing visibly moves after several minutes, check that the plugin is actually running (/plugins in game) and that its rendering task is not paused in its configuration (update-rate for Dynmap).
What is the real difference between Dynmap and BlueMap?
Dynmap shows a 2D top down map, BlueMap a true 3D map with free zoom and rotation. BlueMap looks more impressive, Dynmap offers more advanced marker and zone options built up over years of use.
How much RAM and CPU does it use?
At rest, not much: 100 to 200 MB of extra RAM for most worlds. During the initial full render of a well explored world, expect more like 300 to 600 MB and a temporary CPU spike while it goes through existing chunks. squaremap is the lightest of the three in continuous use.
Can I hide certain areas of the map (spawn, a private base)?
Yes, all three plugins let you define hidden zones or exclude an entire world from rendering (hiddenworlds on Dynmap, per-world exclusion in core.conf for BlueMap, render-unlimited-y-levels and exclusions in config.yml for squaremap).
Does it work with Paper, Spigot or Fabric?
BlueMap and squaremap run on Paper, Spigot and Fabric. Dynmap is limited to Paper and Spigot, no official Fabric version so far. To choose between these server types, our Paper, Purpur, Spigot and Fabric comparison covers the differences.
Can I get the map on HTTPS with a domain name?
Not directly from the panel: you need a reverse proxy set up on your side (see above). For simple sharing between players, the plain HTTP link with the port is enough.
squaremap or Dynmap, why switch?
Servers that migrate from Dynmap to squaremap almost always do it for lightness: squaremap was designed from the start to run continuously without weighing on performance, at the cost of fewer marker options.
Will generating the map slow the server down at startup?
A bit, during the first full render (anywhere from a few minutes to several hours on a very large, already explored world). Player connections are not blocked during that time, only the CPU is more loaded.
Do I need to restart the server after every configuration change?
In most cases yes, so the plugin reloads its configuration file, except for a few reload commands specific to each plugin (/dynmap reload, for instance).
Summary
To get a live map of your Minecraft server: install BlueMap, Dynmap or squaremap as a plugin from the panel, request an extra port in the Advanced tab (Ports section), enter it in the plugin's configuration, and share the link with your players. BlueMap for 3D rendering, Dynmap for advanced markers, squaremap for lightness. The Plugins plan (€8.99/month, 12 GB of RAM, 6 vCPU) handles all three comfortably for a typical server.
