How to Self-Host a Minecraft Map Viewer (BlueMap/Dynmap)

A live web map turns your Minecraft world into something players can explore from any browser — spotting bases, planning builds and showing off the map. The two big options are BlueMap (gorgeous 3D) and Dynmap (classic 2D, lighter on resources). This guide sets up BlueMap on a server VPS and explains when to pick Dynmap instead. It assumes you already run a server — if not, start with how to set up a Minecraft server on a VPS.

BlueMap or Dynmap?

• BlueMap: stunning 3D renders you can fly through. It's heavier — rendering uses CPU and the tiles use disk — so it suits servers with a little headroom.
• Dynmap: a top-down and isometric 2D map, lighter and battle-tested, ideal for smaller VPS plans or huge worlds where 3D would be too costly.

Both run as a plugin (Spigot/Paper) or mod (Fabric/Forge) and serve their own web page.

Prerequisites

• A running Minecraft server on a VPS (Paper/Spigot assumed here).
• The server's plugins folder, typically ~/minecraft/plugins.
• A domain with an A record if you want a clean URL, e.g. map.example.com.

Install BlueMap

Download the BlueMap plugin JAR into your plugins folder and restart the server so it generates its config:

cd ~/minecraft/plugins
wget -O BlueMap.jar https://github.com/BlueMap-Minecraft/BlueMap/releases/latest/download/bluemap-paper.jar

Restart the server. BlueMap will refuse to start until you accept its download of Minecraft assets — edit plugins/BlueMap/core.conf and set:

accept-download: true

Restart again and BlueMap begins rendering your world in the background. Large worlds take time on first render, so let it work.

Serve the map

BlueMap includes an integrated web server, on port 8100 by default. Open just that port, or better, front it with a reverse proxy for a clean HTTPS URL:

sudo ufw allow OpenSSH
sudo ufw allow 25565/tcp   # the Minecraft server itself
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw enable

Point Caddy at BlueMap so players get https://map.example.com:

map.example.com {
    reverse_proxy 127.0.0.1:8100
}

Prefer Dynmap? Same idea, lighter

Drop the Dynmap JAR into plugins and restart; it renders a 2D map and serves it on port 8123. Reverse-proxy it the same way. Dynmap re-renders only changed chunks, which keeps ongoing CPU use low — a good match for a busy server on a modest plan.

Keep performance sane

Map rendering competes with the game for CPU. To keep tick rate healthy:

• Limit BlueMap's render threads in its config on smaller VPS plans.
• Let the initial full render finish during quiet hours.
• If ticks suffer, switch to Dynmap or cap the render distance.

For broader server performance tuning, see how to reduce Minecraft server lag.

Markers, multiple worlds and live players

Once the base map renders, BlueMap and Dynmap both support extras that make the map genuinely useful to players:

• Live player markers: see who's online and where they are on the map in real time — great for events, or spotting who's near your base.
• Custom markers: label spawn, shops, warps and points of interest. In BlueMap you add these via its marker config or a companion plugin; Dynmap has an in-game marker command set.
• Multiple worlds: the Nether and the End render as separate maps you switch between in the web UI, so your whole server is browsable, not just the overworld.

Re-rendering after big changes

After large builds or world edits, you may want a fresh render. In BlueMap use the in-game command to purge and re-render a map; in Dynmap use /dynmap fullrender. Schedule heavy renders for quiet hours so they don't compete with players for CPU, and on smaller plans cap the render threads in BlueMap's config. If map rendering ever hurts your tick rate more than you'd like, Dynmap's lighter 2D approach is the pragmatic fallback — you lose the 3D flythrough but keep a smoother server.

Controlling who can see the map

A live map reveals base locations, so think about who should have access. You have a few options:

• Fully public — great for community servers where the map is part of the appeal.
• Password-protected — put the map behind basic auth in your reverse proxy so only players with the password can view it.
• Private/staff-only — restrict the map's virtual host to your VPN or a set of IPs, so only admins reach it.

BlueMap also lets you hide the real-time player positions or the cave/underground view if you want players to explore the surface map without giving away everyone's location. Configure these in its webapp.conf and per-map settings, then restart to apply.

Storage and world size

The rendered map tiles take disk space that scales with how much of your world players have explored — a heavily travelled world can produce many gigabytes of tiles. Keep an eye on it, and if space gets tight, attach a block storage volume and point BlueMap's web root at it. Because the tiles are regenerated from the world, they aren't precious data; your actual save is what you back up.

FAQ

Does a web map slow down my Minecraft server?

The initial full render is CPU-heavy, but ongoing updates are light — especially with Dynmap. Render during off-peak hours and cap threads on smaller plans.

BlueMap or Dynmap — which is better?

BlueMap looks far better with true 3D; Dynmap is lighter and simpler. Choose BlueMap if your VPS has headroom, Dynmap for large worlds or small plans.

Do players need to install anything?

No. The map is a web page — players just open the URL in any browser.

Can I password-protect the map?

Yes. Put it behind a reverse proxy with basic auth, or restrict access to your VPN if it's for staff only.

Run your server and its live map on a game-ready Minecraft VPS, or explore game server hosting for other titles.