Where Are Palworld Server Logs? (And How to Get Real Logs)
Why Palworld dedicated servers don't ship a log file by default, and how to read the console output or use a logging mod.
If you've gone looking for a Logs/ folder on your Palworld server like every other Unreal game has — you've come up empty-handed. Palworld dedicated servers don't write a log file by default. This page explains why, what your options actually are, and how to get real persistent logs.
Why There's No Log File
Pocket Pair ships the dedicated server binary without enabling Unreal's standard log output. The server writes everything to stdout (the running console) and discards it when the process exits. There is no Pal/Saved/Logs/ directory unless something else creates one.
For comparison: ARK, Conan Exiles, and Squad all write ShooterGame.log / ConanSandbox.log / SquadGame.log to disk automatically. Palworld does not.
This is a Pocket Pair design decision, not a bug. They may change it in a future update.
Option 1: Read the Live Console (Easiest)
The XGamingServer panel Console tab streams the running server's stdout in real time. Everything Palworld would log to a file is visible here, just not persisted across restarts.
In the XGamingServer Panel, open your Palworld server.
Click the Console tab. The output area shows live server output — player joins, chat, errors, save events.
Scroll up to see history within the current session. History clears on restart.
This is enough for live debugging but useless for reviewing what happened yesterday.
Option 2: Use a Logging Mod
Community modders have built logging mods that hook into Palworld and write events to disk. The most-used one is on NexusMods.
- Nexus mod: Server Logging — writes player connect/disconnect, chat, deaths, and admin commands to a file in the server folder.
Mods require UE4SS installed on the server. See Mod Installation for the general workflow.
This is the only way to get persistent, structured logs of in-game events without writing your own scraper.
Option 3: Poll the REST API
If you only need a few events (player list, chat snapshot, server info), the Palworld REST API lets you poll the server on a timer and write the results to a log yourself.
Endpoints worth polling:
| Endpoint | What it returns |
|---|---|
/v1/api/players | Current player list with Steam IDs |
/v1/api/info | Server name, version, uptime |
/v1/api/metrics | Memory, CPU, FPS, current players |
A simple cron job calling /v1/api/players every minute and appending to a file gives you a passable join/leave log. See REST API for setup.
Option 4: Use the Container Output (XGamingServer)
XGamingServer runs Palworld inside a Pterodactyl container. The container's stdout is captured by the panel and persisted in the panel's database for the lifetime of the server instance. You can review historical console output:
In the panel, open the Console tab.
Use the scroll-back buffer (click and drag in the console area). The buffer stores recent output even across restarts in many cases.
For longer-term retention, the logging mod (Option 2) is still the right answer.
What You'll Find in the Console Output
Even without persistent logs, the live console captures useful events:
- Player connect/disconnect — Steam ID and player name appear on connect
- Save events —
[Pal] Auto-saved Worldlines on eachAutoSaveSpaninterval - Crashes — assertion failures and stack traces print to stdout before exit
- REST API errors — failed authentication attempts log a 401
- Memory pressure — Unreal warns about garbage collection running long
Don't Bother Looking For
| Path | Reality |
|---|---|
Pal/Saved/Logs/Pal.log | Doesn't exist on default Palworld dedicated server |
Pal/Saved/Crashes/ | Created only when the server actually crashes — usually empty |
Pal/Saved/Demos/ | Replay folder, not server logs |
Related Guides
How is this guide?
