Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Playing with friends? Godlike.Host runs hosted Palworld servers from 10 data-center locations, with free DDoS protection.
If Palworld suddenly opens character creation even though you already have a survivor, do not create a permanent replacement yet. The most documented cause is a player-save identity mismatch: after moving between co-op, Windows dedicated, Linux dedicated, or SteamCMD servers, the new server can assign a different player GUID and treat the existing save as a first-time player.
Stop the server or game, make a complete copy of the save, identify the environment you came from and the one you moved to, then use the recovery path that matches it. Local rollback can restore an earlier character save; dedicated-server migrations usually require remapping the new GUID to the old player data. Deleting player files is a last resort because it can remove inventory and Pals.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What the new-character screen means
Palworld stores a player character separately from the shared world. The world contains the map, bases and other world state, while player data contains the survivor’s identity, inventory, progression and associated Pals. A server must match the connecting account to the correct player record before it can load that character.
xNul’s Host Save Fix documentation explains that Palworld save files differ by environment and can generate different player GUIDs. The documented affected transitions include co-op to dedicated server and moves between Windows and Linux dedicated servers. If the new server’s GUID does not match the GUID attached to the old player file, the server has no matching survivor to load and presents character creation instead.
#1 Best Overall
- Officially licensed Palworld merch. Join the hunt and capture all the creatures in this open world survival video game. Weaponize your creatures or put them to work in this unique collecting game.
- Perfect graphic apparel for fans of Video Games, Creature Collecting, Open World Games, Cute Animals, Funny Games, and Pocketpair.
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
This is different from an intentional wipe. Xbox Wire reported on June 12, 2024 that the Palworld Update Preview was “fully compatible with existing saves,” indicating that an update that supports existing saves should not normally require a new character. A prompt that appears immediately after a migration, host change or server restore is therefore more consistent with an identity, save-selection or player-file problem than with a planned reset.
Check these symptoms before changing anything
| What you see | Most likely explanation | Safest first action |
|---|---|---|
| The old world is visible, but your survivor is missing | The world loaded while the player GUID did not match | Exit without creating a permanent character and back up the complete save |
| The prompt appeared after moving from co-op to a dedicated server | Environment-specific GUID mismatch | Use a dedicated-server GUID-remapping workflow |
| The prompt appeared after changing Windows and Linux dedicated servers | The migration generated a different player identity | Preserve the old player file and remap it to the new GUID |
| Only one user is affected and the server otherwise works | A corrupted or unreadable player file is possible | Have the server owner back up the Players data before attempting a replacement |
| Several players lost data after a dedicated-server update | A server-version bug or failed data conversion may be involved | Confirm the server version, restore a backup if available and check the relevant patch notes |
Do not infer that Pals or inventory are gone merely because the character-creation screen appears. In a GUID mismatch, the old player data may still be present but no longer linked to the identity generated by the new server.
Do this before attempting recovery
- Stop making changes. Do not finish character creation, play for hours, move items or overwrite a server backup. New writes can complicate identification of the original record.
- Shut down the game or server cleanly. A dedicated-server owner should stop the process before copying or replacing save files. A local player should leave the world and close Palworld normally.
- Make a complete, untouched backup. Copy the entire local or server save, including world data and player data, to a separate location. Keep at least one original copy read-only or clearly marked so it cannot be confused with a working copy. The Host Save Fix README labels the utility experimental and specifically warns users to back up because data loss is possible.
- Record the circumstances. Note the old environment, new environment, platform, server version, date of the last successful login and whether the world map and bases still appear. These details determine which recovery method is appropriate.
- Find out who can access the save. Local or co-op recovery can be done by the save owner. Dedicated-server migration normally requires the server owner to access the save and Players data. If you rent or share the server, ask the administrator to perform the backup and file work.
Choose the recovery method
| Recovery method | Best fit | Access or tools | Risk to inventory and Pals | Status |
|---|---|---|---|---|
| Local or co-op rollback | A local world or co-op save has an earlier usable backup | Access to the original save and backup copies | Low if the original is preserved; progress after the backup is lost | Community-reported workflow |
| GUID remapping | Co-op-to-dedicated or dedicated-server migration | Server-owner access plus the Host Save Fix GUI or script and its Python dependencies | Designed to retain the old player record, but the tool is experimental | Documented by xNul; not an official Pocketpair utility |
| Replace a corrupted player file | One player file appears damaged and no direct remap works | Server-owner access to player files and a known-good backup | High; the community warning says inventory and Pals can be lost | Community fallback |
| Patch or support escalation | Multiple users are affected or no intact save can be identified | Correct server version, backups and Pocketpair support | Depends on whether a usable backup exists | Official support route |
Recover a local or co-op character from a backup
This route applies when you are not moving between dedicated-server formats, or when the old world and character files are available locally. It is a community-reported procedure, so work only on a copy and keep the original backup untouched.
Step 1: Create a temporary save without overwriting the original
Start Palworld, create a temporary new world and temporary character, then return to the title screen. The purpose is to let the game generate a valid save structure that can receive the earlier data. Do not use your only copy of the affected world for this test.
Step 2: Close the game and identify the temporary files
After returning to the title screen, exit the game completely. Compare the temporary save with the backup so you can distinguish the newly created world and character data from the original files. The exact file names and folders can vary by platform and installation, so do not rename or delete files until you have a second copy.
Step 3: Restore the earlier world and character data onto the working copy
Copy the earlier world and player data into the temporary save structure, replacing only the corresponding files in the working copy. Keep the untouched backup elsewhere. If the newest backup still opens the character-creation screen, the community report indicates that an earlier backup can sometimes work better; test older copies one at a time rather than mixing files from different dates.
Step 4: Test before committing
Launch the working copy and check the character, inventory, Pals, bases and map. If the character loads, make a new backup immediately. If it does not, close the game, restore the working copy from the untouched source and test the next earlier backup. Never “repair” the only original by repeatedly replacing files.
Fix a co-op or dedicated-server migration with GUID remapping
When the world is present but the old survivor is treated as new after a server move, GUID remapping is the most targeted option. xNul’s Host Save Fix documentation describes a workflow for applying the new server identity to the old player save. The documentation calls the tool experimental, so a complete backup is mandatory.
What you need
- A copy of the migrated save on the new server.
- The old player data from the source save or source server.
- Permission to stop the dedicated server and access its save and Players data.
- The Host Save Fix GUI or script from xNul’s documentation.
- The Python dependencies specified by that documentation if you use the script rather than the GUI.
- A separate backup that will not be modified during testing.
Step 1: Copy the save to the destination server
Place the source save on the new server using the server host’s normal save-transfer process. Verify that the world opens and that the affected player still receives the new-character prompt. Do not delete the source player files at this stage.
Step 2: Let the new server write a temporary identity
Allow the affected player to join and create a temporary character. This character is not the one you intend to keep; it gives the destination server a newly generated player GUID that can be identified in the destination save. Leave the world as soon as that identity has been written.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Step 3: Stop the server and make another backup
Stop the dedicated server cleanly. Copy the entire destination save, including the newly written temporary player data, before running any repair tool. If the remap fails, this copy lets you return to the exact pre-repair state.
Step 4: Run Host Save Fix
Open the Host Save Fix GUI or run its script according to xNul’s documentation. The process applies the destination player GUID to the old player save so the server can associate the existing character with the identity it generated on the new server. Use the documentation’s stated parameters and dependencies rather than substituting guessed file names or options.
Step 5: Start the server and verify the complete character
Restart the server and have the affected player connect. Check more than the character’s appearance: verify inventory, equipped items, technology progress, Pals, bases and map access. If any of those are missing, stop before saving further changes and return to the pre-tool backup.
Step 6: Retire the temporary character only after verification
Do not remove temporary data until the old survivor is confirmed in-game and a fresh backup has been made. Keep the pre-remap backup for a reasonable rollback period in case another player is affected by the same migration.
What to do when the player file is corrupted
A corrupted player file is a different problem from a simple GUID mismatch. Community troubleshooting describes moving or deleting the affected player files, allowing the user to create a replacement character, identifying the replacement save ID and then restoring appropriate backed-up data. This can make the world playable again, but it is destructive: the warning explicitly says that the character’s inventory and Pals may be lost while the world map remains intact.
Use this only after non-destructive attempts
- Confirm that the old player file exists and that a GUID-remapping attempt cannot load it.
- Preserve the original Players data in a separate backup.
- Have the server owner move the suspected file rather than permanently deleting it when possible.
- Let the affected user create a replacement only on the working copy.
- Record the new save ID and compare it with the backed-up player records.
- Restore only the data you can identify with confidence, then test inventory and Pals in-game.
If the old file is genuinely damaged, there may be no complete way to reconstruct everything from the world save alone. The map and bases can survive while personal inventory and Pals do not.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Check the server version and known dedicated-server bugs
A Steam discussion dated December 23, 2024 reproduced a patch notice stating: “We have released a patch to fix a bug on the v0.4.11 dedicated servers that was causing player data to disappear.” Reports in the same discussion said the problem continued for some users, so the patch should not be treated as a universal repair.
Before attempting a file conversion, record the server’s exact version and whether the issue began immediately after an update. If multiple players lost data at once, first confirm that the server is running the intended patched build and restore a known-good backup if the update or conversion damaged the save. If only one migrated player is affected, a GUID mismatch remains the more targeted explanation.
Rank #4
- Officially licensed Palworld merch. Join the hunt and capture all the creatures in this open world survival video game. Weaponize your creatures or put them to work in this unique collecting game.
- Perfect graphic apparel for fans of Video Games, Creature Collecting, Open World Games, Cute Animals, Funny Games, and Pocketpair.
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
Common mistakes that make recovery harder
Creating a permanent replacement before backing up
A replacement character can create new player data and overwrite clues needed to identify the old record. Create a temporary character only when the selected recovery procedure specifically requires it, and only on a copied save.
Deleting the Players folder immediately
Removing player files may clear the prompt, but it can also remove inventory and Pals. It does not repair the original identity link. Move files to a quarantine backup first.
Mixing files from unrelated backup dates
Combining a world from one date with player data from another can produce missing bases, rollback surprises or new mismatches. Test a complete dated backup before trying selective replacement.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsRunning a repair while the server is online
The server can rewrite the same files while a tool is modifying them. Stop the process, make a copy, run the repair, then restart and test.
Assuming every new-character prompt has the same cause
A migration mismatch, a corrupted player file, a version bug and a wrong save selection can look similar. The environment, number of affected players and presence of the old player files determine the correct branch.
How to prevent the problem on future migrations
- Back up the complete save before changing server software, operating system, host or save format.
- Keep the source save until every player has logged in successfully on the destination.
- Record the old and new server types, versions and migration date.
- Have each player test character, inventory, Pals, bases and map access before the old server is retired.
- For a dedicated server, ensure the administrator can access both world data and the Players data before starting the move.
- Keep multiple dated backups rather than one rolling copy, because an earlier backup may be more usable than the newest one.
When to contact Pocketpair support
Escalate when no intact backup loads, the save remains broken after a controlled GUID-remapping attempt, or a server-wide update appears to have removed player data. Steam lists Pocketpair as Palworld’s developer and publisher and provides support contact information, including support_palworld@pocketpair.jp. Include the platform, server type, exact version, migration history, number of affected players and the backups you still possess. Do not send your only save copy; retain it locally.
Quick Recap
Recovery decision checklist
- Did this happen after a server or host move? If yes, preserve the old player file and follow the GUID-remapping path.
- Is the world local or co-op with an earlier backup? If yes, test the temporary-save rollback workflow on a copy.
- Can the server owner access the Players data? If no, request administrator help before changing anything.
- Is only one player affected? Investigate that player’s GUID or file before assuming a world-wide wipe.
- Are several players affected after a version change? Check the server build and restore a known-good backup before individual repairs.
- Are you considering deletion? Stop and confirm that you accept the possible loss of inventory and Pals; deletion is the last fallback, not the first fix.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
