Vintage Story Custom Maps: Middle-Earth, Earth 30K & Running One on a Server

Vintage Story Custom Maps — Middle-Earth, the Earth Map, and Running One on Your Server

Last verified: June 12, 2026. The Middle-Earth map released this month on the Vintage Story Mod DB.

Vintage Story's custom-map scene just got its flagship: a community-built Middle-Earth map, 30,000 × 20,000 blocks, released in June 2026 after being constructed for a dedicated server and then opened up as a free singleplayer download. It joins the long-standing Earth Map (30K × 60K) as proof that premade worlds are now a real branch of how this game gets played. This page covers what these maps are, how to run one on your own server, and the navigation tooling that keeps a 30k-block world usable for a community.

The Middle-Earth map, specifically

• 30k × 20k blocks, distributed through the Vintage Story Mod DB, with the world files hosted for free download.
• Server-first design, singleplayer release. It was built for a community server (which runs its own Discord), then published so solo players could explore it too. A separate roleplay community, Middle-Earth Story: Shadow of the Fourth Age, runs its own modified Middle-Earth world — two flavors of the same idea.
• Gameplay over lore-accuracy. The creator is explicit about the philosophy: regions are cut and compressed, empty fields reduced, and important locations enlarged with mountains brought closer. The result plays like a curated adventure map rather than a 1:1 cartography exercise — the right call for a game where crossing 30,000 blocks is measured in real evenings.

Installing a downloaded world

• Singleplayer: drop the downloaded save into your VintagestoryData/Saves folder; it appears in the world list.
• Dedicated server: upload the save file into the server's Saves directory, set the server's world settings to that file name, and restart. On managed hosting this is a file-manager upload plus a config field.
• Keep the pristine copy. The most common failure is a corrupted or partial transfer of a multi-gigabyte save — verify the download, keep the original archive, and take your own backup before the first boot, because the first world load also migrates the save to your server's exact version.
• Version sanity. A world built on 1.22 wants a 1.22-line server. Loading old worlds on newer versions generally works (with migration); the reverse does not — same one-way rule as every save format.

Making 30,000 blocks navigable

A themed mega-map without navigation tooling is a screenshot, not a server. The stack that works:

• VS-LiveMap — a browser-based live world map for Vintage Story servers. Players open the map in a tab, see the world (and themselves) rendered, and your Discord stops being a stream of "where is Bree." On a landmark map like Middle-Earth this is half the experience.
• Waypoint conventions — name landmark waypoints after the map's own regions from day one. Custom maps come with a built-in shared vocabulary; use it.
• Boats and rivers — large maps make water travel the highway system; the rivers and boats guide covers the mechanics that turn a 30k map from a hike into a voyage.

Custom map vs generated world (the honest comparison)

Custom maps give a server identity: shared geography, named places, screenshots people recognize. They cost surprise — nobody discovers anything the mapmaker did not place — and they pin your worldgen decisions to someone else's choices. Generated worlds keep exploration alive and, more importantly for admins, let you tune climate and terrain to your community before launch: the Vintage Story world generator previews temperature, precipitation, and worldgen combinations so a generated world is a decision rather than a dice roll (pair it with the /worldconfig reference for the settings that must be set at creation). The pattern across long-running communities: themed and roleplay servers go custom, survival mainlines stay generated, and plenty of servers run one of each.

Server sizing for big maps

World dimensions scare people more than they should: simulation follows players, not map size. A 30k × 20k world with four friends loads the same chunks a generated world would. What does change: storage (a pregenerated map is large on day one), RAM value when a scattered population holds many distant chunk groups active (see chunk loading lag fixes), and event nights — a 20-player exploration weekend across a continent works the server harder than the same 20 players in one town. The large-population setup guide covers the scaling knobs.

Want to launch a Middle-Earth weekend for your community? Host a Vintage Story server with Supercraft — upload the world file, point the config at it, and walk to Mordor with backups running.

Looking for managed Vintage Story server hosting? Supercraft runs Vintage Story dedicated servers with daily backups, instant setup, and 5 region options. Plans from $5.99/mo.