How to Add Mods to Your Palworld Server

How to Install Palworld Server Mods (.PAK + RE-UE4SS + Workshop)

Palworld modding comes in a few different flavours, and the install steps depend on what you downloaded:

Workshop / “Official” server mods (you’ll see an Info.json + InstallRules).
.PAK mods (just a .pak file you drop into a folder).
RE-UE4SS mods (Lua/script/logic mods that need the UE4SS loader).

Most of the active Palworld modding scene lives on Nexus Mods – that’s the best place to find .pak mods and scripted RE-UE4SS mods. Palworld doesn’t use the Steam Workshop.

LOW.MS supports .PAK mods, and LOW.MS also offers one-click install of RE-UE4SS (Stable or Experimental) for modded Palworld servers.

Important: Since Palworld patch 0.4.1.5, the generic public UE4SS build no longer works – you need the Palworld-specific RE-UE4SS build (see pwmodding.wiki). Using the wrong UE4SS will crash the server on startup. LOW.MS’s one-click installer already uses the correct Palworld build.

Important: Not every Palworld mod is server-side. Some are client-only, and some require both the server and all players to install the same mod (and sometimes the same RE-UE4SS build). Always follow the mod author’s instructions.

Crossplay heads-up: Client-side mods can break crossplay. If your server is mixed Steam + Xbox, assume most .pak and RE-UE4SS mods will cause join failures unless every player has the exact same files.

Quick check: what type of mod did you download?

If you have a .pak file → go to Install .PAK mods.
If the mod mentions UE4SS / RE-UE4SS / Lua / scripts → go to Install RE-UE4SS mods.
If the mod includes an Info.json and references PackageName / InstallRules → go to Install Workshop / server mods.

Before you start (recommended)

Back up your world/save before installing mods (LOW.MS automatic cloud backups have you covered, but it doesn’t hurt to grab a manual one too).
Stop the server before uploading or changing mod files.
Install one mod at a time so it’s obvious which mod caused an issue.

Install Workshop / server mods (Info.json / PackageName)

This is the newer “server mod” workflow. It’s the cleanest way to manage mods long-term because you enable/disable them in a config file and the server deploys them on restart.

1) Run the server once (first-time setup)

If you’ve never launched the dedicated server before, start it once so it can generate the mod settings files, then stop it again.

2) Place the Workshop mod files

By default, the dedicated server reads this folder next to the server executable:

Mods/Workshop/<any-folder-name>/Info.json

The folder name doesn’t matter – Info.json must be directly inside that mod folder.

3) Enable mods in `Mods/PalModSettings.ini`

Open Mods/PalModSettings.ini and set:

bGlobalEnableMod=true
Add one ActiveModList= line per mod you want enabled

Example:

[PalModSettings]
bGlobalEnableMod=true
ActiveModList=ExamplePackageName
ActiveModList=AnotherPackageName

PackageName comes from the mod’s Info.json (it is not the folder name).

4) Restart to deploy

Start the server again. On restart, the server will deploy files according to the mod’s InstallRules and load enabled mods.

Disable or remove a Workshop/server mod

Remove the mod’s PackageName line(s) from ActiveModList, then restart.
If needed, delete the corresponding folder under Mods/Workshop/, then restart again.

Install .PAK mods (supported)

1) Get the mod’s `.pak` file

Download the mod (usually from Nexus Mods) and locate the .pak file (it’s often inside a ZIP/RAR).

2) Upload the `.pak` to the server

Open the File Manager in the TCAdmin control panel at control.low.ms. Most .pak mods go in one of these locations (mods differ):

Most common: Pal/Content/Paks/~mods
Also common: Pal/Content/Paks/Mods
Fallback (some mods): Pal/Content/Paks

If the ~mods or Mods folder doesn’t exist, create it.

Server-side file location for mods

3) Restart and test

Start the server, join, and confirm the mod works.

Uninstall a `.PAK` mod

Stop the server, remove the .pak you added, then start the server again.

Install RE-UE4SS mods (LOW.MS one-click)

RE-UE4SS is the loader most Palworld script/logic mods rely on. Since Palworld 0.4.1.5 you must use the Palworld-specific RE-UE4SS build – generic UE4SS will crash the server.

Choose Stable vs Experimental

Stable: Best default choice for most servers.
Experimental: Use when a specific mod requires newer RE-UE4SS features, or the mod author explicitly says “experimental”.

Install RE-UE4SS on LOW.MS

Open your Palworld server in the TCAdmin control panel at control.low.ms.
Go to Mod Manager.
Click Install RE-UE4SS (Stable) or Install RE-UE4SS (Experimental).
Restart the server.

Where RE-UE4SS mods usually go

Most RE-UE4SS mods are placed under a UE4SS mods folder inside your server’s Palworld binaries path. Common locations include:

Pal/Binaries/Win64/ue4ss/Mods
Pal/Binaries/Win64/Mods (depends on the RE-UE4SS package/mod)

Always follow the mod’s folder structure exactly. If the mod ships with folders like mods/, Scripts/, or LogicMods/, keep the structure intact when uploading.

Client requirements (don’t skip this)

Some RE-UE4SS mods require every player to install the mod on their own PC as well, with matching files. If players can’t join after adding mods, this is usually why – and it’s also the quickest way to break crossplay.

Mods we don’t support

Mods that require you to run a custom installer like a .bat file.
Anything that asks you to replace core executables or run unknown scripts.

If you’re unsure, send the mod link to support and we’ll tell you if it’s compatible.

Troubleshooting (fast)

Server crashes after adding a mod

Stop the server → remove the last mod you added → start again. If you just installed UE4SS and the server won’t boot at all, double-check you’re on the Palworld-specific RE-UE4SS build, not generic UE4SS.

Mod does nothing

Confirm it’s in the folder the author expects (~mods vs Mods vs Paks).
Confirm the mod matches your Palworld server version.
If it’s a RE-UE4SS mod, confirm RE-UE4SS is installed (Stable vs Experimental) and the mod files are in the correct folder.

Players time out / can’t join after installing mods

Test with no mods. If it works, add them back one-by-one.
Check if the mod requires client-side install.
If you’re running crossplay, remember client-side mods will almost always break it.
Still stuck? See our guide on troubleshooting Palworld connection timed out errors.

Need help?

Contact our support team with:

The mod link(s)
Whether it’s Workshop/server, .PAK, or RE-UE4SS
If RE-UE4SS: whether you installed Stable or Experimental
Any server logs (if available)