KeepWorlds

Palworld Multiplayer: Invite Code vs Dedicated Server

Palworld's three multiplayer routes are not interchangeable. What each costs in players, uptime and persistence, and when a dedicated server is the only answer.

Palworld has three ways to play together, and in the game they are three separate entry points with different capabilities. People who pick the wrong one usually find out a week or two in — by which point the world is built and switching costs a migration.

This isn't about how to set one up (that's a different article). It answers one question: which route is yours.

Three routes, three different menus

On the title screen, these three lead to different places:

Entry pointWhat runs the world
Invite code / join a friend's worldThe host's game client
Hosting from your own save (multiplayer toggle)The host's PC
Join Multiplayer Game (Dedicated Server)A machine of its own

The parenthetical is a branch point, not a description — type a server address into the invite-code route and it won't connect, and the game won't tell you why.

Invite code

The fastest route: the host starts a session, the game generates a 12-digit code, friends paste it in and they're through.

Three costs come with it:

  • Four players. That's a hard ceiling on this route
  • The host's game client runs the world. When the host quits, the world stops and everyone drops
  • The code changes every session. It isn't a fixed address; you re-share it every time you play

The fit is obvious: a Friday night that ends when everyone logs off. If that's how your group plays, this route is genuinely enough and you can stop reading.

Hosting from your own game

Enable the multiplayer option when creating the world and the cap goes to 32, with friends joining through invites or the friends list.

The only thing it widens is the player count. The core problem is identical:

  • The host's PC still runs the world. Host closes the game, world stops
  • The host carries two jobs at once: server-side simulation and rendering their own client. As the group grows, the person lagging worst is usually the host
  • Everyone's character data lives in the host's save. A problem on the host's machine is a problem for everyone's progress

This route often gets treated as "the free version of a dedicated server." It isn't. It's "an invite code with more seats."

Dedicated server

The world runs on its own machine, independent of anyone's game client.

That buys one property neither of the others can offer: the world runs 24 hours a day.

This is more than "you can always get in." Palworld's bases are a continuous production system — Pals mine, farm, cook and craft while you're away. Stop the world and you stop that too. So:

  • Ore is mined and crops grow while you sleep
  • People in different time zones each play on their own schedule
  • Nobody has to leave their own game running so that others can play

The cost is a machine, plus the setup on day one.

The question that decides it

Most people ask "how many of us are there," but player count only matters at the four-player line. The actual fork is this:

Does the world need to keep running when the host isn't there?

If the answer is no, take one of the first two routes and pick by headcount: four or fewer, invite code; more than that, host from your own game. The money and setup time you save are real.

If the answer is yes, the dedicated server is the only option left. There is no middle choice — in the first two routes the world's lifetime is welded to the host's game process, and that isn't a setting, it's the architecture.

A few signals that you've already crossed the line:

  • Somebody has asked "who's hosting tonight?"
  • Somebody missed a session waiting for the host to come online
  • Not being able to close the game has started to feel like an obligation
  • Someone in the group is several time zones away

Common questions

How many players can join by invite code? Four. That's a hard ceiling on this route; for more, host from your own save (up to 32) or run a dedicated server.

What's the difference between hosting from my game and a dedicated server? When you host from your game, your PC still runs the world and it stops when you close the game. A dedicated server runs on its own machine, 24 hours a day, whoever is online.

Can I move a local world to a dedicated server? The world save moves over, but character data usually doesn't — bases and structures survive, people re-roll. The earlier you switch, the less that costs.

If the answer is the third one

Migrating from a local world to a dedicated server is possible — the world save moves over. Be ready for one catch: character data usually doesn't come with it, because local worlds and dedicated servers don't store player saves the same way. Bases and structures survive; people re-roll.

So if you can already feel the third route coming, the earlier you switch, the cheaper it is. Migrating after three months means everyone levels again.

Once the world has to keep running without you, the question stops being which menu to use and becomes where the machine comes from. KeepWorlds runs Palworld dedicated servers that launch in a few minutes, where the settings are a form rather than a line of ini (all of them explained here) and saves back up on a schedule.

Read this in another language

Rather not run it yourself?

Pick a game and a plan, and your server launches on a machine of its own. Backups, game updates and expiry reminders are on us.

See supported games