ARK: SA Character Transfer Deleted — Recovery and Prevention

ARK: SA character transfer deleted — recovery and prevention

You uploaded your survivor to the obelisk, hopped to a new map, and your character is gone. Inventory empty, levels reset, name back to the default placeholder. It is one of the worst failure modes in ARK and it happens often enough that the community has a name for it: profile loss on transfer. This page covers what actually causes it, what to do in the next few minutes, and how to harden a cluster so it stops happening to your players.

What actually broke

Each character on a multiplayer ARK server lives in a .arkprofile file. When you upload a character at an obelisk or supply drop, three things happen in sequence:

1. The source server reads your .arkprofile and writes a copy into the cluster's shared upload directory.
2. The source server deletes (or marks invalid) the local copy.
3. The destination server, when you connect and pick a character, reads from the cluster upload directory and writes a fresh .arkprofile on its local disk.

Profile loss happens when step 3 fails after step 2 succeeds. You end up with the file removed from the source and never written on the destination. The classic triggers:

• Server save in flight during transfer. If the destination server is mid-save when your client requests the profile read, the read can return empty and the destination writes a default profile on top of it.
• Crash during the writing window. If the destination server crashes or restarts between the cluster read and the local write, the profile is in the cluster file system but not in the server's save.
• Cluster ID mismatch. If the two servers in the cluster were started with different -clusterid values, the upload goes to one directory and the download reads from another. Profile appears lost; it's actually sitting in the wrong folder.
• 24-hour upload timer expiry. Uploaded characters, dinos, and items expire after 24 hours of cluster real-world time by default. If a player uploads on Friday night and logs in on Sunday morning, the upload has expired and the deletion is permanent.
• Did not move enough to commit. A character only "commits" to the new server's save after you take an in-game action (place a structure, harvest, fight). If you log in, accept the character, log out within a few seconds without doing anything, the profile may not have been persisted yet.

If the loss just happened — what to try first

Order matters. Each step assumes the previous one did not recover the character.

1. Do not log out, do not transfer back

If your client is still on the destination server with a placeholder character, leave it logged in. Every additional transfer compounds the problem. Take a screenshot of the placeholder and note the exact time.

2. Check the cluster upload directory directly

If you self-host or have File Manager access, look in the cluster directory for a .arkprofile file matching the player's Steam ID or EOS ID. The path is whatever you set with -ClusterDirOverride=. If the file exists there, the upload is still valid and you can manually copy it into the destination server's ShooterGame/Saved/<Map>/PlayerData/ folder.

3. Contact the host / server admin within the same day

If you rent the server, every reputable host runs automatic snapshots — usually rolling daily backups for the last 5 to 7 days. A snapshot from before the failed transfer contains the character's pre-transfer profile. The host can restore just the PlayerData directory of the source server without rolling back the entire world.

4. Cross-check upload status with the destination obelisk

On the destination map, walk up to an obelisk and look at the player upload list. If the profile is still showing as "available to download," the upload survived even though the download attempt failed. Download a second time, with everyone else off the server, after manually running a save command (SaveWorld from RCON).

5. If nothing worked, log the loss before recreating

If you create a fresh character on the destination, the lost profile becomes unrecoverable because the slot is now occupied. Record the previous character's level, engrams unlocked, and any unique cosmetic before clicking "Create new" — a server admin can spawn back levels via GiveExpToTarget if they decide to comp the loss.

How to prevent this on a cluster you run

Profile loss is a server-configuration problem far more than a player-action problem. If you operate the cluster, the following changes drop the failure rate close to zero.

Make all cluster servers share an identical cluster ID

Start every server in the cluster with the same value:

-clusterid=MyCluster -ClusterDirOverride="/home/u<port>/arksa/cluster_shared"

The directory should be the same physical path on every node (a shared mount, an NFS export, or for a single-host cluster, a literal shared directory). Diverging IDs is the most common silent failure mode.

Raise the save interval on every cluster server

The default 15-minute autosave creates a 15-minute window per server during which a transfer can collide with a save. Raise to 60+ minutes:

?AutoSavePeriodMinutes=60

Trade-off: a server crash now risks losing up to an hour of world state. But profile loss during a transfer is permanent for the player, while world state can be re-played. Tilt the trade in the player's favor.

Extend the upload expiry timer

The 24-hour default catches casual players who upload on Friday and log in Monday. Push it to a week:

[/Script/ShooterGame.ShooterGameMode]
TributeItemExpirationSeconds=604800
TributeDinoExpirationSeconds=604800
TributeCharacterExpirationSeconds=604800
NoTributeDownloads=False

604800 seconds is 7 days. Use the same value on every server in the cluster.

Schedule transfers during low-traffic windows

Restart and save schedules should not overlap. If your cluster has a 4am save on every node, players who transfer in that window are exposed. Stagger saves so at any given moment one node is mid-save and the rest are quiet. Most server hosts allow per-server cron scheduling.

What server admins should communicate to players

Three rules in your Discord pinned message:

1. Download to the new server within 24 hours of upload (or whatever expiry you configured). Past that, the upload is gone and there is no recovery.
2. Move after you arrive. Place a foundation, punch a tree, anything that commits the new server's save with your fresh profile.
3. If your character looks missing, do not panic-create. Open a support ticket first; restoring from snapshot is a 10-minute operation if you catch it before you log out.

For server admins running on Supercraft, daily backups roll for 5+ days by default and the panel exposes one-click rollback of the PlayerData directory. See ARK: Survival Ascended plans.

Looking for managed ARK: Survival Evolved server hosting? Supercraft runs ARK: Survival Evolved dedicated servers with daily backups, instant setup, and 5 region options. Plans from $5.99/mo.