---
title: "Palworld Dedicated Server: Memory Leak, RAM, PalWorldSettings.ini & Save Transfer"
description: "Fix Palworld server memory leaks (8 to 32 GB RAM), edit single-line PalWorldSettings.ini without resets, and transfer local co-op saves (Level.sav)."
url: https://tickserv.com/guides/palworld-server-memory-leak-save-transfer
site: "TickServ (https://tickserv.com)"
lang: en
published: 2026-10-25
games: [palworld]
---
# Palworld Dedicated Server: Memory Leak, RAM, PalWorldSettings.ini & Save Transfer

Running a persistent multiplayer world in Palworld requires tackling two major technical challenges: memory bloat over prolonged sessions and rigid configuration formatting. If you want a ready-to-play setup, you can launch a [Palworld dedicated server](https://tickserv.com/games/palworld) on our platform with automated backups and hourly billing.

## Why RAM usage climbs with world age (and how to stop the memory leak)

The Palworld dedicated server runs on Unreal Engine and communicates over UDP port `8211` (up to 32 simultaneous slots). Unlike Minecraft servers running on a JVM garbage collector, Palworld manages memory natively in C++. Memory footprint increases not just with concurrent players, but with overall simulated activity: every active base camp, every Pal assigned to crafting tasks, and newly explored map chunks remain cached in RAM.

Recommended RAM tiers:

- **8 GB** (€0.06/h in Eco): suitable for starting a new adventure with up to 4 players on a fresh map.
- **16 GB** (€0.12/h in Eco, €0.24/h in Dedicated): the recommended baseline for smooth gameplay up to 16 players, or from 8 players with established bases.
- **32 GB** (€0.24/h in Eco, €0.48/h in Dedicated): necessary for larger communities, heavy exploration, or modded worlds.

On a monthly subscription server left running 24/7, this progressive memory buildup eventually triggers the Linux kernel OOM killer, causing an abrupt crash mid-session. With TickServ hourly billing (€0 when stopped), turning off the server when everyone logs off stops the charges and launches a clean, unbloated process for your next session.

## The PalWorldSettings.ini trap: OptionSettings on a single line

Server configuration is a common pitfall. The engine will discard your edits unless you follow two strict rules:

1. **Edit the correct file while stopped**: the active file is `Pal/Saved/Config/LinuxServer/PalWorldSettings.ini`. Never edit `DefaultPalWorldSettings.ini`, which is only an installation template. Always stop the server before editing, or the shutdown process will overwrite your modifications.
2. **Keep the block on a single line**: all settings must live inside `OptionSettings=(...)` on **one continuous line** without line breaks. If your text editor wraps lines, the server will silently restore default parameters on launch.

Key settings include `PalEggDefaultHatchingTime` (egg incubation time), `ExpRate` (experience multiplier), `DeathPenalty` (death penalties), and `bEnableInvaderEnemy` (disabling base raids significantly cuts down memory usage on large bases).

## Transferring a local solo or co-op save (Level.sav and Players/)

To import an existing co-op playthrough from a local PC without starting over, locate your save directory at `%LOCALAPPDATA%\Pal\Saved\SaveGames\<SteamID>\<WorldID>\`.

This directory contains:

- `Level.sav`: global world state, base structures, and containers.
- `LevelMeta.sav`: world metadata and player tracking.
- The `Players/` folder: individual player files (inventory, progression, captured Pals).

In local co-op, the host player always uses GUID `00000000000000000000000000000001.sav`. When joining a dedicated server, the server assigns a new GUID based on their Steam ID. Without a GUID migration tool, the host will be asked to create a new character, but all world progress and chests in `Level.sav` remain intact. You can upload your `.zip` archive (up to 4 GiB) in one click via the TickServ console (/app).