[{"data":1,"prerenderedAt":29},["ShallowReactive",2],{"doc-en-reset-palworld-player-data":3},{"path":4,"slug":5,"title":6,"description":7,"category":8,"subcategory":9,"icon":10,"date":11,"author":12,"order":13,"image":14,"tags":15,"keywords":20,"docGroup":26,"docGroupIcon":26,"link_fr":27,"bodyHtml":28},"\u002Fdocs\u002Fen\u002Fgaming\u002Fpalworld\u002Freset-palworld-player-data","reset-palworld-player-data","How to reset player data on your Palworld server","Complete guide to clear a specific player's save, inventory, and stats on your Palworld server via the Pterodactyl panel.","jeux","palworld","tabler:file-text","2026-08-11","Winheberg",68,"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Fpalworld\u002Freset-palworld-player-data.webp",[9,16,17,18,19],"wipe","save","pterodactyl","hosting",[21,22,23,24,25],"reset palworld player","wipe player data palworld","delete palworld player save","winheberg palworld server","pterodactyl panel","","\u002Fdocs\u002Fpalworld\u002Freinitialiser-donnees-joueur-palworld","\u003Ch2>Context\u003C\u002Fh2>\n\u003Cp>Are you hosting a \u003Cstrong>Palworld\u003C\u002Fstrong> server at Winheberg and need to reset a specific player's progress (to fix a bug, clear a corrupted save, or upon request)?\u003C\u002Fp>\n\u003Cp>On Palworld, player data (inventory, level, captured Pals) is stored in individual \u003Ccode>.sav\u003C\u002Fcode> files linked to each user's unique \u003Cstrong>Player ID\u003C\u002Fstrong> (UUID). Resetting progress involves finding and deleting this specific file from your \u003Ca href=\"https:\u002F\u002Fpanel.winheberg.com\">Winheberg panel\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>1. Locate the player's Player ID\u003C\u002Fh2>\n\u003Cp>Before deleting any files, you need to identify the exact code assigned to the player. Save files do not display usernames, but hexadecimal strings.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Go to the \u003Cstrong>Console\u003C\u002Fstrong> tab on your \u003Ca href=\"https:\u002F\u002Fpanel.winheberg.com\">Winheberg panel\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Ask the player to connect to the server.\u003C\u002Fli>\n\u003Cli>Check the console log: when they join, a log line will show their name and \u003Cstrong>Player id\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>Copy the character string listed under \u003Cstrong>Player id\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Fpalworld\u002Freset-palworld-player-data-1786459879337-f6ab985d7f84de4ff292bea2.webp\" alt=\"Pterodactyl console showing Palworld Player id\" width=\"800\" \u002F>\n\n\n\u003Ch2>2. Access the save files\u003C\u002Fh2>\n\u003Cp>Now that you have the ID, navigate to the player saves directory.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Stop your server\u003C\u002Fstrong> by clicking \u003Cstrong>Stop\u003C\u002Fstrong> (this step is crucial to prevent the server from overwriting the save file from RAM).\u003C\u002Fli>\n\u003Cli>Go to the \u003Cstrong>Files\u003C\u002Fstrong> tab on your panel.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Fpalworld\u002Freset-palworld-player-data-1786460161428-72945fd2aae67a1e0261e434.webp\" alt=\"Stopping Palworld server and opening Files tab\" width=\"800\" \u002F>\n\n\u003Col start=\"3\">\n\u003Cli>Navigate to the following path:\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cpre>\u003Ccode class=\"language-bash\">Pal\u002FSaved\u002FSaveGames\u002F0\u002F[Session_ID]\u002FPlayers\u002F\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The \u003Ccode>[Session_ID]\u003C\u002Fcode> folder is named after a unique string of characters (e.g., \u003Ccode>C2777061EB1F49F18BFE6364B6481A9A\u003C\u002Fcode>). If multiple folders exist, pick the one with the most recent modification date.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>3. Delete the player save file\u003C\u002Fh2>\n\u003Cp>Inside the \u003Cstrong>Players\u003C\u002Fstrong> folder, you will see all \u003Ccode>.sav\u003C\u002Fcode> files for players who have joined your server.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Locate the file matching the \u003Cstrong>Player id\u003C\u002Fstrong> obtained in Step 1 (e.g., \u003Ccode>703F9A95000000000000000000000000.sav\u003C\u002Fcode>).\u003C\u002Fli>\n\u003Cli>Check the box next to the file.\u003C\u002Fli>\n\u003Cli>Click the red \u003Cstrong>Delete\u003C\u002Fstrong> button at the top right to permanently remove it.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fgaming\u002Fpalworld\u002Freset-palworld-player-data-1786459899846-64cdb539adbbb48ab80bff44.webp\" alt=\"Deleting Palworld player .sav file in panel\" width=\"800\" \u002F>\n\n\n\u003Ch2>4. Restart the server\u003C\u002Fh2>\n\u003Col>\n\u003Cli>Go back to the \u003Cstrong>Console\u003C\u002Fstrong> tab.\u003C\u002Fli>\n\u003Cli>Click \u003Cstrong>Start\u003C\u002Fstrong> to launch your Palworld server.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>When the player reconnects, the server will treat them as a new player, requiring character creation starting at level 1.\u003C\u002Fp>\n\u003Ch2>Troubleshooting\u003C\u002Fh2>\n\u003Ch3>❌ The player still has their old character upon joining\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Server was running during deletion\u003C\u002Fstrong>: If the server was active, cached RAM data was written back to the file upon shutdown. Stop the server completely (\u003Cem>Offline\u003C\u002Fem> status), delete the \u003Ccode>.sav\u003C\u002Fcode> file again, then restart.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ The player cannot log in to reveal their Player ID\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>SteamID lookup\u003C\u002Fstrong>: You can convert the player's SteamID64 to hexadecimal format using an online converter to match their \u003Ccode>.sav\u003C\u002Fcode> filename.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Best Practices\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Create a backup before deletion\u003C\u002Fstrong>: Before deleting any files, create a quick backup by downloading the \u003Ccode>.sav\u003C\u002Fcode> file or creating a snapshot in the \u003Cstrong>Backups\u003C\u002Fstrong> tab on your panel.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Mind the guild leadership\u003C\u002Fstrong>: If the player being reset is the guild leader, ask them to transfer guild leadership to another member before the wipe to prevent base management issues.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Need help?\u003C\u002Fh2>\n\u003Cp>If you have trouble identifying the correct \u003Ccode>.sav\u003C\u002Fcode> file, feel free to contact the \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fsupport\">Winheberg support team\u003C\u002Fa>.\u003C\u002Fp>\n",1788993142823]