Best Vintage Story Server Hosting (2026): Mods, RAM, and Long-Term World Checklist
Vintage Story rewards a host that respects long-term worlds. A village, animal husbandry, mechanical-power setup, custom map, and a large mod list make a very different server from a short vanilla test. Runtime and mod compatibility matter as much as raw RAM.
The current Supercraft tiers list 8/16/32 slots with CPU Priority 1/2/3. Use the checklist below to compare .NET/runtime support, port/config access, mod synchronization, save safety, and the workload of the world you want to keep.
The short version
| Runtime | Vintage Story dedicated server uses the .NET runtime; keep server version and runtime dependencies aligned. |
|---|---|
| Capacity | Supercraft lists 8, 16, and 32 player tiers with CPU Priority 1/2/3. |
| Network | The default server port is TCP 42420 unless the host assigns a different endpoint. |
| Mods | The local guidance uses about 4 GB for vanilla and 8+ GB for heavy mods, with mod zip/version sync as a key risk. |
| Operations | The source page lists mod support, FTP/config access, backups, DDoS protection, and four regions. |
What actually matters when choosing Vintage Story hosting
Use these checks when comparing any provider. They are deliberately tied to this game’s server model, so a high slot number or generic “unlimited” badge cannot answer them for you.
1. .NET and server-version parity
A correct port cannot fix a server launched under the wrong runtime or a client/server version mismatch.
Check: Ask which .NET/runtime and Vintage Story build run, and how updates are staged.
2. RAM for vanilla versus heavy mods
A vanilla world can be comfortable around 4 GB while an 8+ GB modded workload needs more room and more careful sync.
Check: Choose by mod list and world age, not by player slots alone.
3. Tick performance and mechanical power
Villages, animals, machines, farms, and long-running mechanical systems create persistent tick work.
Check: Compare CPU priority and ask how performance is monitored when the world grows.
4. Mod zip and config management
A modded Vintage Story world is a set of exact files. One incompatible mod can prevent startup or alter a save.
Check: Require upload/file access, version notes, logs, and a pre-update restore point.
5. Port, whitelist, and admin controls
Private communities need a stable 42420 path or assigned port and admins need scoped commands.
Check: Confirm port/firewall details, whitelist/password, admin commands, and configuration files.
6. Long-term migration and price
A world may run for years, so the ability to export it and restore after a runtime or mod change is part of the value.
Check: Compare backups, downloads, migration, region, DDoS, support, and renewal terms.
Green flags and red flags
Use these as questions for a provider, not as a substitute for testing the exact game build, map, mod list, or save.
Green flags
- The .NET/runtime and game build are explicit.
- Vanilla and heavy-mod RAM guidance is separated.
- Mod zips, configs, logs, and backups are accessible.
- Port 42420, admin/whitelist, and migration are documented.
Red flags
- The host claims all mod lists fit the smallest plan.
- Runtime is ignored because “it is just a server.”
- Mod files cannot be exported or rolled back.
- The port and whitelist path are hidden behind support.
Where Supercraft fits the checklist
Supercraft is the operator behind the offer shown below, so this section is an affiliation disclosure as well as a comparison. The useful claim is limited to what the corresponding hosting page actually lists; verify unusual mods, platform mixes, or capacity assumptions before ordering.
Current Vintage Story hosting offer
These are the current plan facts collected from the canonical hosting page. Prices are loaded from WooCommerce at request time and adapt to the visitor’s store currency; no static price is embedded in the guide.
Vanilla or light-mod world for a small group.
Growing village, animals, mechanical power, or moderate mods.
Large community, heavy mod stack, or persistent simulation load.
The cards show Supercraft’s current plan structure for this game. They are included so you can compare a concrete offer against the checklist; they are not a claim that Supercraft is objectively the best provider for every group.
See the full Vintage Story server hosting pageVintage Story hosting FAQ
How much RAM does a Vintage Story server need?
The local guidance uses about 4 GB for vanilla and 8+ GB for heavier mods. World age, animals, machines, and map/mod complexity can justify more headroom.
Which Vintage Story plan should I choose?
Use S for a small vanilla/light-mod world, M for a growing village or moderate mod load, and L for a larger community or heavy persistent simulation. CPU priority matters alongside slots.
What port does Vintage Story use?
The default dedicated-server port is TCP 42420. A managed host may assign a different endpoint, so use its connection details and test from the client.
Can I install Vintage Story mods?
Yes, but mod zips, versions, dependencies, and client/server sync must be kept consistent. Back up before changing a mod list.
Can I migrate a Vintage Story world?
A suitable host should support world and mod-file export/import. Preserve the original and test the destination after matching the server/runtime version.
Keep researching
Sources used for this guide: Vintage Story official wiki: dedicated server guide · Supercraft Vintage Story hosting page.