Every ARK player eventually hits the same fork in the road: keep playing on a "non-dedicated" session hosted from one player's own game client, or move to a real dedicated server that runs independently, 24/7, on its own hardware. The two options look similar in the main menu but behave completely differently under real play, and picking the wrong one wastes either money (over-provisioning a dedicated box for two players) or hours of frustration (trying to run a 20-person tribe off someone's gaming PC).
This article breaks down exactly what changes between the two setups — player caps, uptime, save-file risk, mod support, and performance — and gives a clear decision framework for when it's actually worth paying for a dedicated server versus sticking with non-dedicated.
The choice matters more the longer you plan to play. A weekend co-op session doesn't need the same infrastructure as a tribe that's been building for eight months and has a real base, a real breeding line, and real feelings about losing progress. This guide is written for the second group as much as the first — the goal is to help you recognize the moment your group has actually outgrown non-dedicated, rather than either upgrading too early and wasting money or sticking with a session that's visibly failing your group's needs out of inertia.
What Is a Non-Dedicated ARK Session?
A non-dedicated session is a multiplayer game hosted directly from one player's own ARK client — the same instance they're playing on doubles as the "server" for everyone else connecting to it. It's built into the base game with no extra download or setup:
- Launched from the "Host/Local" menu rather than connecting to a listed server
- Limited to a small number of concurrent players (historically capped low, and heavily dependent on the host's own hardware and upload bandwidth)
- Only online while the hosting player is actively running the game — close the game, and the world goes down for everyone
- Uses the host's own save file, stored locally on their machine
- Subject to the host's own frame rate and network performance; if they alt-tab or their connection drops, everyone else's session degrades or disconnects too
How Non-Dedicated Actually Behaves Under Load
The host's game client is doing double duty: rendering their own first-person view at whatever framerate their monitor and GPU support, and simultaneously acting as the authoritative simulation for every other connected player's dinos, structures, and physics. The moment the host opens a demanding menu, tabs to Discord, or their own game stutters from a nearby explosion, everyone connected feels it too — there's no isolation between "the host's experience" and "the server's job." This is the single biggest practical difference from a dedicated setup, and it's the one new players underestimate most before they've actually felt it happen mid-raid.
What Is a Dedicated ARK Server?
A dedicated server is the standalone server binary (downloaded via SteamCMD) running on its own hardware, independent of any player's game client:
- Stays online continuously regardless of whether any specific player is logged in
- Supports much higher player counts, limited only by the hardware you provision, not a client-side cap
- Save data lives on the server itself, accessible for backup, migration, and cluster transfers
- Supports full mod lists, cluster transfers between maps, and RCON-based remote administration
- Requires you to actually manage hosting — either self-hosted hardware or a rented dedicated/VPS plan
What "Managing" a Dedicated Server Actually Involves
It's less ongoing work than people expect once it's set up correctly. The bulk of the effort is front-loaded into initial setup — SteamCMD install, config, firewall rules, and choosing your mod list. After that, ongoing admin work is mostly: reacting to occasional RCON alerts or player reports, applying game updates when a new patch drops, and periodically checking that scheduled backups are actually completing. A tribe with one moderately technical member can comfortably run this in an hour or two a month; it is not a full-time job, and it is far less demanding than most first-timers assume before they've tried it.
Side-by-Side Comparison
| Factor | Non-Dedicated Session | Dedicated Server |
|---|---|---|
| Player cap | Low, hardware/bandwidth dependent | Configurable, limited by your provisioned RAM/CPU |
| Uptime | Only while host is playing | 24/7, independent of any player |
| Performance | Shares resources with the host's own gameplay rendering | Dedicated resources solely for world simulation |
| Save file location | Host's local machine — lost if their drive fails without manual backup | Server storage, easily scheduled for automated backup |
| Mod support | Limited, host-client dependent | Full mod list support with server-side management |
| Cluster transfers | Not supported | Fully supported between multiple dedicated maps |
| Setup effort | None — built into the game menu | Requires SteamCMD install, config, and firewall setup |
| Ongoing cost | Free (uses host's existing hardware/internet) | Typically $20-$100+/month depending on player count and mods |
Cost and Effort Breakdown Over Time
The comparison above captures a snapshot, but the more useful way to think about this decision is total cost of ownership over a season of play, not just the sticker price on day one.
| Timeframe | Non-Dedicated Real Cost | Dedicated Real Cost |
|---|---|---|
| First weekend | Free, but host's PC is tied up and can't be used for anything else while hosting | Setup time (1-2 hours) plus first month's hosting fee |
| First month | Free, but any host hardware issue (reboot, driver crash, needing the PC for something else) takes the whole group offline | Flat monthly fee, uptime unaffected by any single player's PC |
| Six months in | Save file risk has usually already caused at least one "we lost some progress" incident in an active tribe | Automated backups mean this risk is effectively eliminated with minimal ongoing effort |
| A year in | Host burnout is common — the person hosting bears all the risk and inconvenience for a group that shares none of it | Cost has usually been absorbed into a shared group expense, and admin duties can rotate among trusted members |
When Non-Dedicated Is the Right Call
Small, Casual Groups (2-4 Players)
If you and one or two friends play in short, overlapping sessions and don't mind the world being offline when the host isn't playing, non-dedicated is genuinely fine — there's no reason to pay for a server that will sit at 5% utilization all day.
Testing a Mod List Before Committing
Non-dedicated is a reasonable way to sanity-check whether a mod combination even loads correctly before you invest in a paid dedicated server plan and go through full mod-ID configuration.
Short-Term or One-Off Sessions
A weekend co-op run with no intention of a persistent long-term world doesn't need dedicated infrastructure — the setup overhead isn't worth it for a session you'll abandon in a few days anyway.
When You Should Upgrade to a Dedicated Server
More Than 4-5 Regular Players
Non-dedicated sessions become noticeably unstable well before you hit double-digit players, both because of the client-side player cap and because the host's own PC is now rendering their game and simulating the world for everyone else simultaneously — this shows up as stutter for the host first, then desync for everyone else.
Anyone Wants to Play Without the Host Online
This is the single biggest practical reason tribes upgrade. The moment "I want to log in and build while Alex is at work" becomes a real desire, non-dedicated stops working — the world is only up when the host's client is running.
You Want Mods, Clusters, or Real Admin Tools
RCON remote administration, scheduled restarts, automated backups, and multi-map clustering are dedicated-server-only features. If your tribe wants to move between The Island and Scorched Earth with dino transfers, you need a real dedicated setup.
You're Worried About Losing Progress
A non-dedicated save lives only on the host's PC. If that drive dies, gets reformatted, or the host simply loses interest and deletes the game, the world is gone unless someone manually backed up the save folder. A dedicated server's save lives on server storage where scheduled backups are trivial to automate.
Real-World Example: A Tribe's Typical Upgrade Path
A common pattern looks like this: three friends start a non-dedicated session on The Island, playing mostly on weekends when everyone happens to be free at the same time. Within a month, a fourth and fifth friend join, and suddenly someone's always asking "can you host tonight?" in the group chat — the answer increasingly depends on whose turn it is and whose PC is free, not on whether people actually want to play. By week six, someone logs in solo on a weekday evening to find the host's PC is off, and the pattern of "the world is only up when Alex is playing" becomes the group's biggest source of friction. That's usually the exact moment a small dedicated plan (8-12 GB RAM, a handful of dollars a month split five ways) starts looking obviously worth it — not because the game demands it, but because the social friction of host-dependency outweighs the setup effort of moving to a real server.
Buyer's Checklist for Making the Switch
- Count your realistic concurrent player count over a normal week, not your best-case Saturday night — size for the average, not the peak, then leave headroom
- Decide whether you actually want mods and clustering, since that meaningfully changes your RAM/CPU requirements
- Check whether your prospective host supports SteamCMD-based install and full RCON access, not just a locked-down web panel
- Budget for NVMe storage — ARK's save and mod file sizes make slow disks a noticeable bottleneck during saves and backups
- Confirm the plan includes a static IP so your tribe can bookmark one server address permanently
- Ask about DDoS protection if you plan to run a public (not whitelist-only) server
- Decide who in the group will hold admin credentials and RCON access, and agree on that before launch rather than after a dispute
- Check whether the provider bills monthly and allows cancellation mid-cycle, in case your group's interest shifts faster than expected
- Ask whether the host offers a short trial period for a first-time dedicated tribe unsure how much server they actually need
What You Give Up by Staying Non-Dedicated Too Long
It's worth being honest about the accumulating cost of delay. Every week spent on non-dedicated past the point your group has actually outgrown it is a week of avoidable host-dependency friction, a week of save-file risk sitting on one person's local drive with no backup, and a week without the mod list or cluster setup your group has probably already discussed wanting. None of these costs are dramatic in isolation, but they compound — a tribe that upgrades in month two loses far less accumulated progress-at-risk than one that waits until month eight and then has a drive failure the week before finally making the switch.
Migration Walkthrough: Moving Your Non-Dedicated Save to a Dedicated Server
When your group decides to make the switch, the move itself is far less painful than most tribes fear — the whole process fits into an evening if you work through it in order.
Step 1: Locate and Back Up the Host's Save
On the hosting player's PC, find the local save folder (under the game's Saved directory for their installation) and copy the entire world save — not just the map file, but the player and tribe data files alongside it — to at least two separate locations before touching anything else. This backup is your undo button for every later step, so don't skip it or store it in only one place.
Step 2: Provision and Install the Dedicated Server
Rent a plan sized for your realistic weekly concurrency, install the server binary via SteamCMD, and complete a plain first boot with a fresh throwaway world to confirm the install, ports, and firewall rules all work before any migration data enters the picture. Debugging connectivity on a fresh world is much easier than doing it while also wondering whether your copied save is the problem.
Step 3: Copy the Save Into Place
Stop the server, place the backed-up save files into the server's SavedArks directory with naming that matches the map you're launching, and start the server pointed at that map. Keep the original untouched backup exactly as it was — if anything looks wrong, you want a pristine copy to retry from.
Step 4: Verify Before Announcing
Log in yourself and physically check the things your tribe cares about: bases standing, tames present, character levels and engrams intact. Have one other player confirm their character too, since character-data issues don't always show up on the first account tested. Only then tell the whole group the new address.
Step 5: Retire the Old Session Cleanly
Once everyone has played a few sessions on the dedicated box without issues, have the old host archive (not delete) their local save. Keeping that final non-dedicated snapshot for a few weeks costs nothing and protects against the rare late-discovered migration problem.
Common Mistakes When Making the Switch
The most common migration mistake is copying only the world map file and leaving the player/tribe data files behind, which produces a world with buildings intact but characters wiped — recoverable if you kept the full backup, devastating if you didn't. A second mistake is sizing the new server for your best-attended Saturday session ever rather than a normal week, overpaying from month one for capacity that sits idle; most hosts make upgrading later easy, so start realistic. A third is doing the migration and a game-version update in the same evening — if something breaks you won't know which change caused it, so migrate on the version you were already running and update separately once stable. Finally, some groups never agree on who holds admin access before launch, which turns the first rules dispute into an infrastructure argument; decide this while everyone is still excited about the new server rather than after the first raid controversy.
Quick Self-Assessment: Which Setup Fits Your Group Today?
If you want a fast answer without re-reading the whole comparison, score your group against this table — each row is a question that pushes you toward one column or the other.
| Question | Points Toward Non-Dedicated | Points Toward Dedicated |
|---|---|---|
| How many regulars play weekly? | 2-4 players | 5 or more |
| Do people want to play at different times? | Everyone plays together anyway | Schedules rarely overlap |
| How attached are you to the world? | Casual, could restart tomorrow | Months of breeding lines and builds at stake |
| Do you want mods or multi-map clustering? | Vanilla is fine | Yes, or planning to soon |
| Is anyone willing to spend an evening on setup? | Nobody technical or interested | At least one member can follow a guide |
| Is a shared monthly cost acceptable? | Group won't pay anything | A few dollars each is fine |
If four or more rows land in the right-hand column, your group has functionally already outgrown non-dedicated — the only question left is who sets the server up and when. If most rows land left, save your money and revisit the question in a couple of months; the upgrade path will still be there.
Frequently Asked Questions
Can I convert a non-dedicated save into a dedicated server world?
Yes, in most cases — copy the save file from the host's local save folder into the dedicated server's SavedArks directory with matching map naming, though always back up both copies before attempting this in case of format mismatches.
Is non-dedicated multiplayer actually peer-to-peer?
Functionally yes — the host's client acts as the authoritative server for everyone connected, meaning their upload bandwidth and CPU headroom directly cap how well the session performs for every other player.
How many players can realistically join a non-dedicated session?
It varies by platform and host hardware, but in practice sessions get noticeably unstable well before you'd comfortably run the same headcount on even a modest dedicated server plan.
Do non-dedicated sessions support mods?
To a limited degree, but every connecting player typically needs the same mods installed client-side, and there's no server-side mod management the way a dedicated server offers.
What's the cheapest way to get "always online" without full dedicated server pricing?
A small budget dedicated or VPS plan sized for 5-8 players is usually the sweet spot — enough to remove host-dependency and gain real backups without paying for a 30-player-scale box you don't need yet.
Can I run a non-dedicated session and a dedicated server at the same time to test the switch?
Yes — there's no conflict running a dedicated server for your live tribe while a separate non-dedicated session is used to sanity-check a mod list or settings change, since they're entirely independent instances with their own save files.
Does upgrading to dedicated mean losing our existing tamed dinos and structures?
Not necessarily — you can copy the host's local save file into the dedicated server's save directory as part of the migration, though always keep a backup of the original non-dedicated save until you've confirmed the dedicated server loads it correctly.
Who should actually pay for and manage a dedicated server for a friend group?
Splitting the monthly cost evenly and rotating basic admin duties (restarts, mod updates) among two or three trusted members works better long-term than putting the entire burden on whoever originally suggested upgrading — it avoids the same burnout problem that pushed the group off non-dedicated hosting in the first place.
Is there a middle ground between non-dedicated and a full dedicated server?
Not really within ARK itself — the game only offers these two hosting models. Some players treat a very cheap, minimally-provisioned dedicated plan as the middle ground, since it removes host-dependency at a lower cost than a fully-specced public server plan.
The honest answer for most small tribes is to start non-dedicated and upgrade the moment "I wish the world was up when so-and-so isn't playing" becomes a recurring complaint. When you're ready to make that jump, our ARK: Survival Ascended dedicated server setup guide walks through the full configuration, and WebsNP's VPS hosting plans are a cost-effective entry point for a first dedicated tribe server, with dedicated server plans ready when you outgrow shared resources — talk to us about sizing the right plan for your tribe.