Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesTo move an ARK: Survival Evolved singleplayer world to a dedicated server, stop the destination server, back up its current save, upload the complete local save set (the map .ark file plus matching .arktribe and .arkprofile files), select the same map in the server configuration, and restart. Uploading only the map file can leave you with a world that has no original survivor, tribe, or dinosaurs.
Playing with friends? Godlike.Host runs hosted ARK: Survival Evolved servers from 10 data-center locations, with free DDoS protection.
Check that these instructions match your game
This procedure is for ARK: Survival Evolved (ASE), primarily a PC local save moved to a rented or self-hosted dedicated server. ARK: Survival Ascended (ASA) has separate transfer documentation and save behavior. Do not assume that an ASE folder layout or file set can be used for ASA; confirm the edition-specific instructions for ASA before changing any files.
As an Amazon Associate I earn from qualifying purchases.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →The destination must also support access to its save files and map configuration. A host that offers a web file manager or FTP, permits a clean stop and restart, and exposes the startup map setting is suitable for this migration. Paths, permissions, supported maps, and crossplay rules vary by provider, so the provider’s own directory and compatibility documentation takes precedence over the example path below.
Prepare the destination before replacing anything
Stop the server first
Use the host control panel to stop the server completely. Do not upload over a world that is still running. A running process can write an older state over the files you are transferring, or leave a mixture of old and new files that loads unpredictably.
#1 Best Overall
- Get NVMe solid state performance with up to 1050MB/s read and 1000MB/s write speeds in a portable, high-capacity drive(1) (Based on internal testing; performance may be lower depending on host device & other factors. 1MB=1,000,000 bytes.)
- Up to 3-meter drop protection and IP65 water and dust resistance mean this tough drive can take a beating(3) (Previously rated for 2-meter drop protection and IP55 rating. Now qualified for the higher, stated specs.)
- Use the handy carabiner loop to secure it to your belt loop or backpack for extra peace of mind.
- Help keep private content private with the included password protection featuring 256‐bit AES hardware encryption.(3)
- Easily manage files and automatically free up space with the SanDisk Memory Zone app.(5). Non-Operating Temperature -20°C to 85°C
Make a restorable backup
Download or copy the destination server’s existing save before removing or replacing files. Keep that backup outside the active save directory and label it with the map and date. If the migration fails, restoring this copy is safer than trying to reconstruct the previous world from a partial upload.
Remove conflicting files only after the backup
For the target map, remove or move the destination’s conflicting save files as directed by the host. Nitrado’s documented ASE sequence stops the server, backs up the files, and removes conflicting files before the replacement upload. Other providers may use a different root directory or a restore workflow; follow their instructions rather than deleting unrelated maps.
Free tools Windows power users keep installed
One-click scans. No signup required.
Locate the singleplayer save on your PC
Steam installation
- Open Steam and go to your ARK library entry.
- Choose Properties, then Installed Files, then Browse.
- From the installation folder, open
ShooterGame/Saved. - Locate the local-save directory and the files belonging to the map you intend to transfer. Keep the entire set together; do not copy just the largest file.
The Browse command is preferable to guessing a drive letter or Steam library location, because the game may be installed in a secondary library. The exact subfolder presentation can vary with the installation, but the ShooterGame/Saved area is the place to inspect for ASE local saves.
Rank #2
- Solid state performance with up to 800MB/s read speeds in a portable drive. (Based on internal testing; performance may be lower depending on host device, interface, usage conditions and other factors. 1MB=1,000,000 bytes.)
- Back up your content and memories on a storage solution that fits seamlessly into your mobile lifestyle.
- Take it with you on your adventures—up to two-meter drop protection means this durable drive can take a beating. (Based on internal testing.)
- Secure it to your belt loop or backpack for extra peace of mind thanks to the tough rubber hook.
- From Sandisk, a brand professional photographers trust to take on assignments.
Epic installation
Epic installations use a SavedArksLocal location in the game’s saved-data area, as shown in Nitrado’s ASE transfer instructions. Use the actual installation and user-data location on your machine, and make sure you are selecting the save created by the same game installation and account. If several maps or older backups are present, sort by the most recent modification time and verify the map name before uploading.
Do not confuse a local save with a configuration folder
Configuration files and mod data are not substitutes for the world save. The migration needs the world file and the associated player and tribe files described in the next section. Preserve the original folder structure until you have identified those files.
Identify the complete file set
An ASE singleplayer world is more than one map file. Select the world file ending in .ark and the associated .arktribe and .arkprofile files from the same save. File names identify the map, tribe, or player data; do not mix files from different maps or older snapshots.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
| File type | What it carries | What happens if it is omitted |
|---|---|---|
.ark |
The map-world state, including the world and placed structures. | The server cannot load the intended world, or it may start a new world if no matching save is found. |
.arktribe |
Tribe data associated with the world. | The world can load without the expected tribe relationship or access rights. |
.arkprofile |
Player and survivor data associated with the save. | You may spawn as a new survivor or fail to see the original survivor and its progression. |
These consequences are practical symptoms, not a guarantee that every omission produces exactly the same result. The important rule is to upload the complete matching set rather than trying to repair a missing survivor after the server has already generated a new state.
Upload the save to the server
Use the host’s file manager or FTP
- Confirm the destination server is still stopped.
- Open the provider’s file manager, or connect with FTP using the credentials supplied by that provider.
- Open the provider’s ASE save directory. In Nitrado’s documented example, the destination is
/arkse/ShooterGame/Saved/SavedArks/. - Upload the map
.arkfile and its matching.arktribeand.arkprofilefiles into the directory used for active saves. - Wait for every transfer to finish. A file that appears in the listing while still uploading is not proof that the transfer completed.
- Check names and extensions after upload. Avoid renaming files unless the host’s documentation specifically requires it.
The Nitrado path is an example, not a universal path. A different host may expose a different root, use a differently named save directory, or require a particular instance subfolder. Uploading valid files to the wrong directory is functionally the same as not uploading them: the server starts without seeing your world.
Preserve the file relationships
Keep the player and tribe files from the same local save as the map file. Do not combine a current .ark with an older .arkprofile or a tribe file from another map. If you made a safety copy, leave it outside the active directory so the server does not mistake an old copy for the live save.
Rank #4
- NEARLY 2X FASTER THAN OUR PREVIOUS GENERATION(8) – move 1,000 high-res photos in under 60 seconds(6) with up to 2000MB/s transfer speeds(2).
- IP65 RATING AND UP TO 3M DROP PROTECTION(3) – protects against spills and drops.
- POCKET-SIZED – fits easily in pockets and small bags.
- SPACE TO OWN YOUR AI CONTENT – speed and capacity to download your high-res clips and photo edits.
- 256-BIT AES ENCRYPTION(4) – helps keep private files secure with password protection.
Set the server to the save’s map
Open the server’s general or startup settings and set Mapname (or the provider’s equivalent map field) to the exact map represented by the uploaded .ark file. Save the configuration before starting the server.
The map setting is not cosmetic. It determines which world the server attempts to open. If it points to another map, the server can create or load a fresh world even though your uploaded files are present. Match spelling and punctuation exactly as the host expects; do not select a similarly named map merely because it is in the same expansion or cluster.
Restart and verify the migration
- Start the server after the upload and map setting have been saved.
- Wait for the server to finish its normal startup, then join it using the usual server browser or direct connection method.
- Check for the survivor you used in singleplayer, not only the map scenery.
- Confirm that the expected tribe is present and that your survivor has the appropriate tribe access.
- Visit several known locations to verify structures, storage, and other placed objects.
- Check the dinosaurs and other tames that should have been in the transferred world.
A successful connection by itself proves only that a server is online. Verification must include the player, tribe, structures, and tames, because an incorrectly selected map or incomplete file set can still produce a playable but apparently empty world.
Best Value
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Troubleshoot the common failure symptoms
| Symptom | Likely cause | What to check next |
|---|---|---|
| A new survivor creation screen appears | The .arkprofile file was omitted, uploaded to the wrong directory, or the server opened a new map. |
Stop the server, verify the player file is in the active ASE save directory, confirm the exact Mapname, and restart. Restore the backup if the destination has already written a new state. |
| The map loads but dinosaurs are missing | The upload was incomplete, the wrong map was selected, or files from different saves were mixed. | Compare the uploaded file set with the local source, re-upload all matching files, and verify the map setting before starting again. |
| The survivor is present but tribe access is wrong | The tribe file did not transfer correctly, or the migration encountered ASE singleplayer-to-dedicated limitations. | Confirm the matching .arktribe file was uploaded. If it was, treat the result as a known transfer limitation rather than repeatedly overwriting the save; use the provider’s support process and your backup. |
| The server starts a completely different world | The startup map does not match the uploaded save, or the files are outside the host’s active save path. | Stop the server, inspect the provider’s documented directory, correct Mapname, and check that the transfer completed without errors. |
| Only some files are visible after transfer | FTP or the web manager interrupted the upload, or a large file is still transferring. | Wait for completion, compare names and sizes with the local files where the client provides that information, then upload the missing files again while the server is stopped. |
When testing a correction, stop the server before changing files again. Starting it with an incomplete set can cause it to create a replacement state, making it harder to tell whether the original problem was the path, map selection, or missing data.
Recommended Free Tools
Understand the tribe-transfer limitation
Nitrado warns that tribe access may not transfer correctly in some singleplayer migrations. That warning matters even when the world, structures, and survivor appear to be present. A conversion can therefore be usable without being a perfect reproduction of every ownership relationship from singleplayer.
Before inviting other players, test the tribe permissions with the transferred survivor and inspect access to representative structures and tames. Keep the original local save and the server backup until you are satisfied with the result. If tribe ownership is wrong, avoid deleting the source copy: the limitation may not be fixable by changing the map name or uploading the same files repeatedly.
Choose a server setup that can actually accept a save
If you are selecting or changing providers for this migration, evaluate capabilities rather than a brand name or advertised game count. The following checks determine whether you can perform a controlled transfer and recover from a mistake.
| Capability | Why it matters for a singleplayer upload | Questions to ask the provider |
|---|---|---|
| File-manager or FTP access | You need to place the .ark, .arktribe, and .arkprofile files in the active save directory. |
Can you upload and download ASE save files, and is the actual path documented? |
| Safe stop and restart controls | The server must be offline while files are replaced. | Can you stop it fully, confirm it is stopped, and restart it after configuration changes? |
| ASE map and save support | A host may support ARK while imposing limits on particular maps or save formats. | Is the intended ASE map supported, and are imports from another host or self-hosted machine allowed? |
| Backup and restore controls | A backup gives you a way back if the first boot creates a new world or damages the active copy. | Can you download a manual backup and restore it without contacting support? |
| Map configuration | The server must open the map represented by the uploaded save. | Where is Mapname configured, and does the setting require a restart? |
| Platform and crossplay compatibility | Save transfer and connection support can differ by platform and crossplay mode. | Does the server configuration match the platform on which the local ASE save was created? |
Nitrado documents file-manager or FTP uploads for worlds originating on another host or from self-hosting, while also noting that some games have import or export exceptions. That is why the destination provider’s ASE-specific documentation should be checked before you commit to a migration.
Operational checklist
- Edition: Confirm this is ASE, not ASA.
- Source: Identify the correct local map save from the Steam or Epic installation.
- Safety: Stop the destination and keep a separate backup of its current save.
- Files: Include the matching
.ark,.arktribe, and.arkprofilefiles. - Destination: Use the provider’s documented active ASE save directory; the Nitrado example is
/arkse/ShooterGame/Saved/SavedArks/. - Configuration: Set Mapname to the exact uploaded map.
- Validation: After restart, check survivor, tribe, structures, and dinosaurs.
- Recovery: If the result is a fresh or incomplete world, stop again, inspect the path and file set, and preserve the original backup.
Following those checks transfers the world data the server can read while making the two main failure points—an incomplete upload and a mismatched map—easy to isolate.
Quick Recap
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.
