Set up a BlueMap web map and control rendering load

BlueMap turns a Minecraft Java world into a browser map. Its renderer and web listener are separate from the Minecraft connection, so a working game address does not prove the map is reachable. Start with one small map before rendering every world.

Choose a compatible release and a recovery point

Check the BlueMap release against your Minecraft server platform and Java runtime. Requirements change between releases; use the requirements for the JAR you actually download. A Bukkit plugin belongs in a compatible Paper or Spigot installation, while mod loaders require their matching build. BlueMap does not read Bedrock Edition world storage.

Stop normally and take a completed backup before adding the plugin. Keep a copy outside the game server. Include existing BlueMap configuration when upgrading, and check free storage before generating new map data. See game backups and plugin installation.

Configure the web listener

1. Install the matching JAR and start once to generate configuration. Confirm that BlueMap enables, then stop before editing.
2. On a plugin installation, open plugins/BlueMap/core.conf. Read the resource-download notice before deciding whether to set accept-download to true. This authorises BlueMap's required resource download; it is not a port setting.
3. Ask support for an available additional TCP allocation on your game server. Do not pick another customer's port or reuse the Minecraft port.
4. Set that allocated port in webserver.conf. Keep the generated binding setting unless support has given you a specific value for this environment.
5. Start and inspect the listener and renderer messages in Console. Open the assigned address and port from another connection, then check that the expected world appears.

The example default port in upstream documentation is not an allocation reservation. If you want a domain with HTTPS, arrange a supported reverse-proxy setup with support. Creating a DNS record alone neither configures TLS nor conceals an origin that remains publicly accessible.

Limit the first render and review privacy

Inspect the generated map configuration before publishing it. Decide which worlds should be visible and whether player locations should be shown. Do not expose an event world's hidden builds merely because it was detected automatically. Treat a public map link as public information, even if you only shared it with your Discord initially.

Run bluemap in Console, without the leading slash, to inspect status. Watch CPU usage, tick performance and free storage during initial rendering. Increase the area gradually; a large world or detailed map can require substantial disk and processing time. Do not run several competing map renderers while measuring the first job.

Separate reachability from rendering problems

If the browser times out, check the allocated TCP port, listener startup and the requested protocol before changing map settings. If the website loads but terrain is missing, inspect render progress and the selected world instead. Preserve configuration and generated data while investigating rather than reinstalling the server.

Send support the server ID, BlueMap version, exact URL without private tokens, error time and relevant redacted startup lines. Further reading: BlueMap installation and the official configuration wiki.

Looking for another plugin? Browse the Minecraft plugin guide directory.