# Vintage Story server hosting for your settlement

> Host a Vintage Story server with mods from the official ModDB, a whitelist, roles and land claims, sized with the official RAM formula. Plan it today.

Survival · Sandbox

Build a settlement that keeps growing while you are offline. Run the official Vintage Story server with your world settings, mods from the official mod database and a whitelist for your group.

- Official dedicated server for Windows and Linux
- Mods from the official ModDB, synced to players automatically
- Whitelist, roles and land claims for your group
- Size advice based on the official formula

See plans Find your size

Players MaxClients in serverconfig.json. Players beyond the limit can wait in a queue set with MaxClientsInQueue. 16 by default (MaxClients)\
Port Since 1.20 the server uses port 42420 over both TCP and UDP. Change it with Port in serverconfig.json. 42420 TCP/UDP\
Version 1.22.7 (August 2026)\
Config serverconfig.json\
Mods Official ModDB, synced on join\
Platforms PC: Windows, macOS, Linux

Options

- Survival
- Creative mode
- ModDB
- Whitelist
- Land claims
- Roles

Game facts from the official Vintage Story wiki and Anego Studios’ release notes, checked in October 2026.

- DDoS protection
- 20 game server locations

## Vintage Story plans are being prepared

Tell us your player count and the mods you plan to use, and our team will reply with the options. Or open a ticket and we will let you know when the plans are online.

[Contact sales](https://hyperdc.com/contact-us) [Open a ticket](https://hyperdc.com/support/new-ticket)

## How much RAM does a Vintage Story server need?

The official wiki gives a simple rule: a base of 1 GB plus about 300 MB for every player. Mods and large explored worlds add more.

| Feature | **Small group** Up to 4 players | Recommended **Community** Up to 8 players | **Full server** Up to 16 players | **Large or modded** Up to 32 players or big mods |
| --- | --- | --- | --- | --- |
| Memory (RAM)Working memory for the world, the players and every mod. Leave headroom: memory use grows as players explore. | 3 GB | 4 GB | 6 GB | 12 GB |
| CPU threadsThe wiki suggests 4 threads at a base clock of 1 GHz plus 100 MHz per player. | 4 | 4 | 4 | 4+ |
| Disk spaceRoom for the game files, the world and its backups, plus updates and mods. | 5 GB | 10 GB | 15 GB | 25 GB |
| View distanceMaxChunkRadius sets how many chunks around each player the server sends; 12 by default. Lower values save memory and bandwidth. | 12 (default) | 12 | 10–12 | 8–10 |
| Typical use | Friends starting a new world | A group with a few mods | A full settlement community | Public server or large content mods |

- ### Small group
  Up to 4 players
  Memory (RAM)Working memory for the world, the players and every mod. Leave headroom: memory use grows as players explore. 3 GB\
  CPU threadsThe wiki suggests 4 threads at a base clock of 1 GHz plus 100 MHz per player. 4\
  Disk spaceRoom for the game files, the world and its backups, plus updates and mods. 5 GB\
  View distanceMaxChunkRadius sets how many chunks around each player the server sends; 12 by default. Lower values save memory and bandwidth. 12 (default)\
  Typical use Friends starting a new world
- Recommended
  ### Community
  Up to 8 players
  Memory (RAM)Working memory for the world, the players and every mod. Leave headroom: memory use grows as players explore. 4 GB\
  CPU threadsThe wiki suggests 4 threads at a base clock of 1 GHz plus 100 MHz per player. 4\
  Disk spaceRoom for the game files, the world and its backups, plus updates and mods. 10 GB\
  View distanceMaxChunkRadius sets how many chunks around each player the server sends; 12 by default. Lower values save memory and bandwidth. 12\
  Typical use A group with a few mods
- ### Full server
  Up to 16 players
  Memory (RAM)Working memory for the world, the players and every mod. Leave headroom: memory use grows as players explore. 6 GB\
  CPU threadsThe wiki suggests 4 threads at a base clock of 1 GHz plus 100 MHz per player. 4\
  Disk spaceRoom for the game files, the world and its backups, plus updates and mods. 15 GB\
  View distanceMaxChunkRadius sets how many chunks around each player the server sends; 12 by default. Lower values save memory and bandwidth. 10–12\
  Typical use A full settlement community
- ### Large or modded
  Up to 32 players or big mods
  Memory (RAM)Working memory for the world, the players and every mod. Leave headroom: memory use grows as players explore. 12 GB\
  CPU threadsThe wiki suggests 4 threads at a base clock of 1 GHz plus 100 MHz per player. 4+\
  Disk spaceRoom for the game files, the world and its backups, plus updates and mods. 25 GB\
  View distanceMaxChunkRadius sets how many chunks around each player the server sends; 12 by default. Lower values save memory and bandwidth. 8–10\
  Typical use Public server or large content mods

Starting points from the official wiki’s conservative estimate: 1 GB plus 300 MB per player, 4 threads, 1 GHz plus 100 MHz per player. Large mods and big explored worlds need more.

## Mods, roles and world settings

The official server brings the tools to run a settlement for friends or a public community.

### Official mod database

Install mods with /moddb install or drop the zip files into the Mods folder. Since 1.16, players receive the server’s mods automatically when they join.

### Roles and privileges

Ready-made roles from visitor to admin decide who may build, use blocks, kick or ban. Edit them with /role or make someone admin with /op.

### Whitelist and password

Dedicated servers start with the whitelist on since 1.20. Add players with /player name whitelist on, or set a password instead.

### World settings

Choose survival or creative, the seed, world size and climate when the world is created, and change many rules later with /worldconfig.

### Autosave and backups

The server saves every 300 seconds by default, and /genbackup copies the world into the backups folder without stopping the game.

### Bring your world

Create the world in single-player with the advanced options, then upload the .vcdbs file and point SaveFileLocation at it.

## Set up your Vintage Story server

Four steps to a world that keeps its seasons running.

1. ### Pick a size
   Use the table above: the official estimate is 1 GB plus 300 MB for every player.
2. ### Pick a location
   Choose the one closest to your players from our 20 game server locations.
3. ### Set your world and rules
   Set the server name, MaxClients and password in serverconfig.json, choose the world settings and add your players to the whitelist.
4. ### Invite your players
   Share the address and port 42420; players add the server in the multiplayer menu and join with their game account.

## Other game servers you might like

### Valheim

Up to 10 Vikings with crossplay, modifiers and backups.

### Minecraft

Java and Bedrock worlds with plugins, modpacks or crossplay.

### Terraria

Vanilla or tModLoader worlds for up to 255 players.

### Core Keeper

An underground world for up to 8 players, from every PC store.

### Necesse

Settlements for up to 250 players, with permissions and raids.

### Wurm Unlimited

Your own Wurm world: Adventure or Creative, PvE or PvP.

[Learn more](https://hyperdc.com/game-servers/wurm-unlimited)

## Frequently asked questions

Still have a question? Send us a message and our team will reply by email.

[Contact us](https://hyperdc.com/contact-us) [Open a ticket](https://hyperdc.com/support/new-ticket)

### How many players can join a Vintage Story server?

MaxClients in serverconfig.json sets the limit; it is 16 by default and can be changed in game with /serverconfig maxclients. The official guide plans about 300 MB of extra memory per player.

### How much RAM does the server need?

The official wiki gives a rough, conservative estimate: 1 GB plus 300 MB per player, 4 CPU threads and a base clock of 1 GHz plus 100 MHz per player. Mods and large explored worlds need more.

### Which port does the server use?

Port 42420, over TCP and, since version 1.20, also UDP. You can change it with Port in serverconfig.json.

### Do players need to install mods themselves?

No. Since 1.16, players who join a modded server receive the matching mods automatically, kept in a separate folder for that server. The server gets its mods from the official mod database or from its Mods folder.

### Why can my friends not join?

Dedicated servers start with the whitelist on since 1.20. Add each player with /player name whitelist on, or change WhitelistMode in serverconfig.json if anyone may join.

### How do I make someone an admin?

Use /op followed by the name, a shortcut for giving the admin role. Without console access, add the command to StartupCommands in serverconfig.json. Roles such as sumod or crmod give moderator rights.

### Can I bring my single-player world?

Yes. Stop the server, copy the .vcdbs save into its Saves folder and point SaveFileLocation in serverconfig.json at it. The wiki also suggests creating the world in single-player with the advanced options and uploading it.

### How are backups made?

The server autosaves every 300 seconds by default. /autosavenow saves at once, and /genbackup copies the save into the backups folder without pausing the server.

### Which version does the server run?

The current stable release is 1.22.7 from August 2026. Since 1.22 the server needs the .NET 10 runtime; 1.21 used .NET 8. Keep the server on the same version as your players.

### Do players need their own game account?

Yes. With VerifyPlayerAuth on, the default, the server checks that each player is logged in with a registered game account. The server itself needs no account.

### Can I list the server publicly?

Yes. Set AdvertiseServer to true to show it on the public server list; it is off by default.

## Ready to build your settlement?

Tell us your player count and mods, and we will help you pick the right Vintage Story server.

See plans [Contact sales](https://hyperdc.com/contact-us)

---

Source: <https://hyperdc.com/game-servers/vintage-story>\
Updated: 2026-10-09
