How to Read Palworld Server Logs and Console Output

When something goes wrong, the console is your best clue. Knowing what to look for turns confusing text into useful information.

Where to look

• The Console tab of your panel shows live output.
• The file manager may contain log files in the server folders. Exact locations can differ between versions and setups, so browse the Pal folder and look for a Saved directory with logs.

What logs can tell you

• When the server started and finished loading.
• When players connect and disconnect.
• Warnings and errors about settings or files.
• Signs of a crash or an out-of-memory stop.

How to read it

1. Restart the server and watch the console from the beginning.
2. Note the time of the issue.
3. Look at the lines just before an error appears, because the cause is often earlier than the failure.
4. Search for words like error, warning, failed or fatal.
5. Copy the relevant lines and save them with the time.

Common patterns

• Repeated startup lines followed by a stop usually point to a configuration or save problem.
• Messages about memory suggest the plan may be too small.
• Many connection lines from one source in a short time can indicate unwanted traffic.

Do not treat every warning as a disaster. Many are harmless noise that appears on healthy servers.

Using logs with moderation

For griefing or cheating reports, check the log around the time reported. Combine this with player evidence before acting.

Sharing logs for help

When asking for support in Discord:

• Include the time of the problem.
• Paste the surrounding lines, not just one.
• Mention what changed recently, such as updates or settings edits.
• Remove private information such as passwords.

Keep it manageable

Old logs can take space. Check periodically and clear what you no longer need, keeping recent ones for troubleshooting.

Related guides

See our crash and connection troubleshooting guides for fixes once you have identified the issue.