How to Add a Web Map to a Minecraft Server (BlueMap or Dynmap)

To add a web map to a Minecraft server, drop the BlueMap or Dynmap .jar into plugins (Paper, Purpur) or mods (Fabric, Forge, NeoForge) and restart. For BlueMap, set accept-download: true in plugins/BlueMap/core.conf or nothing renders. The map is served by a small web server on its own TCP port: 8100 for BlueMap (webserver.conf), 8123 for Dynmap (configuration.txt). That port must be open and different from the game port. Players then open http://<server-ip>:<port> in a browser.

What you are working with

Pick one, not both. Each renders the whole world and running two doubles the CPU and disk cost. BlueMap is the usual pick for new servers. Dynmap suits servers that want its web chat or an addon built for it. Vanilla servers run neither, so switch to Paper or a mod loader first.

Download from the projects' own pages: BlueMap's installation guide links the right builds, and Dynmap lives on GitHub. Match the build to your server type and Minecraft version. Recent BlueMap releases need Java 25, which current Minecraft servers already run.

Where the files go

Method 1: BlueMap

1. Install and start once

Stop the server, upload the BlueMap jar, start it so it writes its config files, then stop it again.

2. Accept the download

Open core.conf and change:

accept-download: true

BlueMap needs the textures from the Minecraft client jar, which it downloads from Mojang. Until you set this, BlueMap loads, logs a warning and renders nothing. This is the step most people miss.

3. Set the web port

In webserver.conf, the default is:

enabled: true
port: 8100

Change port to whatever second port you have open. Never set it to your Minecraft port: the game already holds that TCP port, and the web server fails to start.

4. Start and render

Start the server. BlueMap renders the worlds in the background. Type /bluemap in game or in the console to see progress, and /bluemap reload after editing configs. Open http://<server-ip>:8100 (or your port) to see the map fill in.

Method 2: Dynmap

1. Stop the server, upload the Dynmap jar, start and stop it once.
2. In configuration.txt, set webserver-port: 8123 to your open port. Leave webserver-bindaddress: 0.0.0.0.
3. Start the server and run /dynmap fullrender world from the console (world is the default world folder on Paper). From the console, Dynmap renders from the world's center.
4. Open http://<server-ip>:8123.

Use /dynmap pause all to stop rendering during busy hours, /dynmap pause none to resume, and /dynmap cancelrender world to stop a full render.

How long does rendering take?

Rendering reads every chunk that exists, so it scales with how much of the world has been explored. A small friends world finishes quickly, while a big, old world can take hours and uses CPU the whole time. Two things help:

• Set a world border first. The map only covers generated chunks, so a border keeps it from growing forever.
• Pregenerate, then render once. If you plan to pregenerate with Chunky, do it before the first full render so the map is not redrawn chunk by chunk. See how to pregenerate a Minecraft world with Chunky.

Tiles take disk space too, especially BlueMap's hires 3D data. Turn off maps you do not need, for example the End, in BlueMap's maps/ configs.

Sharing the link

Send players http://<your server IP>:<web port>. Use your server's numeric IP or domain with the web port, not the Minecraft port. For a tidy link like map.example.com, point a domain at the IP and put a reverse proxy in front of the web port. Both projects document that, but it needs a machine where you can run a web server.

Common problems

• BlueMap page loads but stays empty: accept-download is still false, or the render has not reached your area yet. Check /bluemap.
• "Failed to bind" or the web server does not start: the port is already in use, usually because it was set to the Minecraft port. Pick a different one.
• Page does not load at all: the web port is not open. It needs TCP open on the firewall or host, and the address must include the port.
• Map shows old terrain: players built after the last render. Both maps update changed chunks while the server runs, so give it time, or render that area again.
• Server lags while rendering: pause the render or limit render threads in the config, and run full renders when nobody is online.

Web maps on GamezServers

On a Minecraft server from GamezServers, uploading the jar and editing core.conf or configuration.txt takes a minute in the Files tab or over SFTP, and a one click Backup covers you before you add anything. Every server also comes with a spare port for a web map: the control panel lists it under your address as Extra ports (your game port plus two). Set BlueMap's port or Dynmap's webserver-port to that number, restart, and share http://your-address:that-port with your players. More plugin ideas are in the best Minecraft server plugins.

FAQ

What port does BlueMap use?

TCP 8100 by default, set with port in webserver.conf. Dynmap uses 8123, set with webserver-port in configuration.txt.

Why is my BlueMap blank?

Usually accept-download is still false in core.conf. Set it to true, run /bluemap reload and wait for the render.

Is BlueMap or Dynmap better?

BlueMap gives a 3D map and is the common choice for new servers. Dynmap is flatter but has web chat and many addons.

Can the web map use the same port as Minecraft?

No. Minecraft already uses its port for TCP, so the map's web server needs a different port that is open to the internet.