Free tools Windows power users keep installed
One-click scans. No signup required.
To move an Official ARK: Survival Ascended world to your own server, download and extract the official export, preserve an untouched rollback copy, stop the destination server, back up its existing save, and upload the official map, player, and tribe files into the destination map folder. Rename the world file to the standard filename that your server expects before restarting it.
Prefer not to run the server on your own PC? Godlike.Host offers hosted ARK: Survival Ascended servers with free DDoS protection and up to three free backups a day.
This is a complete save-file import: it can preserve the world, survivor, tribe, structures, and tames when the files and platform are compatible. It is different from an in-game CrossARK transfer, which moves selected characters, creatures, or items through an obelisk or transfer terminal and does not recreate an entire world.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsWhat you are actually moving
An Official export is made up of several data types. Treating them as interchangeable is a common reason an imported map loads without a survivor, tribe, or creatures.
| File or data | What it contains | Why it matters |
|---|---|---|
.ark world file |
The map state: terrain state, structures, wild and tamed creatures, inventories, and world settings stored in the save. | This is the file that makes the destination server load the exported world instead of its newly generated default world. |
.arkprofile player file |
Survivor-specific data, including the player identity and progression associated with that profile. | Without the matching profile, you may join as a new survivor even though the map itself loads. |
.arktribe tribe file |
Tribe membership and tribe-level information. | It allows the imported survivor and structures to remain associated with the tribe represented in the export. |
| Player or tribe folders | Some exports package the profile and tribe files inside folders rather than placing them at the archive root. | Upload the supplied folders and their contents when the export is organized this way; do not discard them because they are not beside the .ark file. |
The exact archive layout can vary by export provider. Before changing anything, confirm that the extracted working folder contains a map file and the player and tribe data, either as individual files or as containing folders.
#1 Best Overall
- ARK: Survival Ascended has completely recreated and redesigned the artwork and worlds of ARK to take advantage of the latest in videogame technology, Unreal Engine 5, using high-end graphics features such as fully dynamic Global Illumination (“Lumen”), so that light bounces realistically of off surfaces and provides realistic reflections, and advanced mesh streaming (“Nanite”) of hundreds of millions of triangles for extreme detail.
- Advanced new physics systems such as dynamic water so that every creature creates waves, ripples, splashes, and bubbles as they move through fluids, and fully interactive physical foliage where every blade of grass, bush, and tree reacts to characters, explosions, projectiles, and physics objects.
- ARK: Survival Ascended includes access to all of ARK’s worlds, including Scorched Earth, Aberration, Extinction, ARK Genesis Part 1, ARK Genesis Part 2, and more. The Island is released now, with the subsequent expansion worlds to be added at no additional cost on a regular basis.
- Thorough Quality of Life revamps in every area: redesigned User Interfaces, dynamic navigation for intelligent creature pathfinding, Wild Babies, Photo Mode, new Camera systems, new Map system, Tracking System, new Structures and Items, new Creatures, and much more.
- Cross-Platform Modding: Download & play new custom content created by players, including new maps, creatures, items, and game modes, through a dedicated new Mod-bowser directly within the game! Enjoy an endless stream of new ARK content as the creativity and talent of the community is fully unleashed for the first time ever across gaming platforms!
Before you begin: requirements and safety checks
Plan the migration as a reversible replacement, not as a one-way overwrite. You need access to the official export, access to the destination server’s files, and enough local storage to keep two copies of the important data.
- Official export: Obtain the save download supplied by Studio Wildcard or by the provider hosting the Official export. Availability and the exact download process can change, so verify that the export is currently offered for your account and platform.
- Extraction space: Extract the archive into a working folder rather than editing files inside the compressed archive.
- Destination file access: You need the server’s File Browser or FTP access. A control panel that only exposes console commands is not sufficient for a complete file import.
- Server control: You must be able to stop the destination server completely before replacing its save.
- Rollback storage: Keep the untouched export and a separate copy of the destination save. A USB flash drive for ARK save backups can be useful as an offline second copy, provided it has enough free space and is stored safely.
- Platform compatibility: Confirm that the export and destination use a compatible platform and save format. A Steam PC procedure is not automatically valid for console or another PC distribution.
- Map identity: Know the destination map’s internal folder and expected world filename. The folder and filename are related but not always identical to the name shown in the server browser.
Do not delete the destination save while the server is running. A process that still has the world open can write over your changes or leave a partial save.
Recommended Free Tools
Step 1: Download, extract, and inventory the Official export
Download the Official save export from the source that supplied it, then extract it into a new working folder. Do not rename or edit anything until you have made a preservation copy.
- Create a folder with a descriptive name, such as
ASA-Official-Export-Original, and copy the extracted files into it. - Make a second working copy for any renaming or staging. Leave the original folder untouched.
- Locate the map file ending in
.ark. Official exports can use a server-oriented filename such asOfficialServer1234.arkinstead of the map name your destination expects. - Locate the
.arkprofileand.arktribefiles. If they are inside player or tribe folders, keep the folder structure intact in the staging copy. - Record the map represented by the export. Uploading an Island world into a server configured for a different map can cause a load failure or an apparently empty world.
Studio Wildcard previously announced Official Network save games so players could host their own server and continue their progress. That announcement is historical context, not a guarantee that every Official save is still downloadable today; confirm current export availability before starting a migration.
Rank #2
- Brand new UK Import PAL version. Game in English. UK PSN store account required to use any online features
Step 2: Prepare Steam PC files when applicable
Steam PC imports have an additional profile-naming requirement. Nitrado’s Steam PC instructions identify the local save location as ShooterGame/Saved/SavedArksLocal.
- Copy the map save, player profile, and tribe file from the extracted export into a separate staging folder.
- Find
LocalPlayer.arkprofile. This generic filename identifies a local profile but is not the filename the imported server expects for a Steam survivor. - Rename the profile so its filename begins with the player’s OSS ID, while retaining the
.arkprofileextension. Use the OSS ID associated with the survivor being imported; do not substitute the display name or Steam nickname. - Keep the renamed profile beside the map and tribe data in the staging copy. Preserve the untouched original with its original filename in case you need to repeat the process.
The reason for this step is data matching: the map file holds the world, the .arkprofile file holds player data, and the .arktribe file holds tribe information. A correctly uploaded world with a profile that does not match the server’s expected identity can load without your established survivor.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →This profile rename is specific to the Steam PC workflow described above. Do not apply it blindly to console exports or another platform’s file format; follow the destination provider’s current platform-specific naming rules.
Step 3: Stop the destination server and create a rollback
Stop the destination server from its control panel and wait until its status shows that it is fully stopped. Then preserve the current destination files before replacing the default world.
Rank #3
- Ark graphics and worlds are completely recreated and designed to use the latest video game technology, Unreal Engine 5
- Advanced new physical systems such as dynamic water and fully interactive physical leaves
- Design your survivor, shape the trunk and tame, train, multiply and ride dinosaurs in a vivid ecosystem
- Public online mode for up to 70 players, private multiplayer mode for up to 8 players + local split screen for 2 players
- Use the server panel’s stop command, not merely a disconnect or a restart.
- Open the provider’s restore-point or backup function and create a restore point if one is available.
- Download the existing save files or copy them to a separate backup location through the File Browser or FTP.
- Label the backup with the date, map, and server state, for example
Before-Official-Import-TheIsland-2026-10-14. - Only after the backup is complete, rename or remove the destination’s default world files. Renaming is safer than immediate deletion because it leaves a quick local recovery path.
Nitrado’s documented warning is: “We recommend backing up your server before you delete the default save.” Take that literally. The restore point is your fastest recovery if the imported world fails to load, has the wrong map, or contains unexpected data.
Step 4: Upload the files into the destination map folder
Use the server’s File Browser or connect by FTP while the server remains stopped. The documented destination root is /arksa/ShooterGame/Saved/SavedArks. Inside it, open the folder for the map, such as TheIsland_WP.
- Navigate to
/arksa/ShooterGame/Saved/SavedArks. - Open the map-specific folder that corresponds to the server’s configured map. Examples include
TheIsland_WPandTheCenter_WP. - Confirm that the folder belongs to the map you intend to import. Do not place an Island save in a Center folder simply because both folders are visible.
- After confirming the backup exists, rename or move the default world file out of the way. Leave unrelated configuration files alone unless the provider’s instructions specifically require otherwise.
- Upload the official
.ark,.arkprofile, and.arktribefiles into that map folder. If the export supplies player or tribe folders, upload those folders and their contents instead of flattening or omitting them. - Wait for every upload to finish. A partial FTP transfer can leave a file with the correct name but incomplete contents.
The target is the destination map folder under ShooterGame/Saved/SavedArks/<MapName>, not the top-level ShooterGame/Saved directory and not a neighboring map’s folder. The angle-bracket notation means the actual map directory, such as TheIsland_WP, not a folder literally named <MapName>.
Step 5: Rename the world file to the server’s standard name
The official export’s world filename often identifies the Official server rather than the map. The destination server normally looks for a standard map filename, so rename only the uploaded world file after it is in the correct map folder.
| Map | Example standard world filename |
|---|---|
| The Island | TheIsland_WP.ark |
| The Center | TheCenter_WP.ark |
| Scorched Earth | ScorchedEarth_WP.ark |
- Identify the map configured in the destination server.
- Check the provider’s exact expected spelling and capitalization for that map. Custom maps may use a different internal name.
- Rename the uploaded Official world file to that exact name, preserving the
.arkextension. - Do not rename the profile or tribe files to the map name. Their identity is separate from the world filename.
- Check that the folder does not now contain both the old Official filename and the new standard filename. Two competing world files can make it unclear which save the server is loading.
Examples from the documented guide are TheIsland_WP.ark, TheCenter_WP.ark, and ScorchedEarth_WP.ark. These examples do not establish the correct name for every custom map; verify a custom map’s internal save name before startup.
Step 6: Start the server and verify the imported world
Start the server only after the files are in place and the world has its standard name. The first boot can take longer than a normal restart while the server reads the imported save.
- Start the destination server from its panel.
- Allow the startup process to finish instead of repeatedly restarting when the server does not appear immediately.
- Join the server using the same map and platform context as the export.
- Check the map identity first. A loaded server showing a fresh spawn area may indicate that the default world is still active rather than that the import succeeded.
- Check that the expected survivor appears. On Steam PC, confirm that the OSS-ID profile rename was done correctly.
- Check tribe membership, owned structures, tamed creatures, inventories, and important locations.
- Stop and investigate rather than playing on the imported world if any major element is missing. New progress made on the wrong save complicates rollback.
Once the map, survivor, tribe, structures, and tames are confirmed, create a fresh backup of the working imported server. Keep the original export and the pre-import destination backup separately; they serve different recovery purposes.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.If the imported world does not load
Do not repeatedly overwrite files while the cause is unknown. Stop the server, restore the pre-import backup, and work through the checks below in order.
The server starts a new world
- Verify that the world file is inside the configured map folder under
ShooterGame/Saved/SavedArks, not one directory higher. - Check the exact standard filename, including capitalization and the
.arkextension. - Confirm that the server is configured for the same map represented by the export.
- Check for a second world file with the old Official filename or a stale default filename. Move conflicting files aside after preserving a backup.
The map loads, but the survivor is missing
- Confirm that the
.arkprofilewas uploaded to the same map folder as the world. - For Steam PC, verify that
LocalPlayer.arkprofilewas renamed with the correct OSS ID and that the extension was not changed to something such as.arkprofile.txt. - Ensure that you did not upload only the
.arkfile while leaving the profile in a local staging folder. - Check platform compatibility. A profile from an incompatible platform may not be recognized even when the world file is valid.
The survivor appears, but tribe or structures are missing
- Confirm that the
.arktribefile or supplied tribe folder was uploaded. - Check that the tribe data belongs to the same export as the profile and world. Mixing files from different snapshots can produce inconsistent ownership.
- Restore the pre-import copy and repeat the upload with the complete set of files if any transfer was interrupted.
The server crashes or refuses to start
- Stop the server and restore the destination backup so that it can boot on the known-good save.
- Check map-folder spelling, world filename, platform, and save-version compatibility before trying again.
- Confirm that the uploaded file sizes are plausible and that FTP or File Browser transfers completed without errors.
- Review the provider’s current map and import requirements, especially for custom maps or modded servers.
- If the imported world still will not load, contact the host’s support team with the map name, platform, filenames, and the time of the failed startup. Nitrado specifically advises contacting support when the imported world remains unable to load after these checks.
Complete save import versus in-game CrossARK transfer
These methods solve different problems. Choose a complete file import when the goal is to continue an entire world; choose CrossARK when only selected player, creature, or item data needs to move and file access is unavailable.
| Decision point | Complete save-file import | In-game CrossARK transfer |
|---|---|---|
| What moves | The exported world plus its associated player and tribe data. | Selected characters, tames, and items transferred through in-game map towers or obelisks. |
| World and structures | Can preserve the imported map state, tribe, and structures when the files are compatible. | Does not recreate the complete Official world or copy all structures. |
| Required access | Official export access, server stop control, and File Browser or FTP access. | Access to the relevant in-game transfer interface and servers linked for the transfer. |
| Platform scope | Depends on compatible save format and platform-specific file rules, including the Steam PC profile naming step. | Depends on the platform’s current transfer restrictions and what the linked servers permit. |
| Rollback | Clear and reversible when the original export and pre-import destination backup are retained. | Not equivalent to restoring a whole world; transferred items or creatures may need to be moved back individually, if the rules allow. |
| Best use | Continuing an Official world on a privately controlled or managed server. | Moving a survivor, selected creatures, or selected inventory when a full save export cannot be accessed. |
Nitrado describes CrossARK as an in-game feature using map towers to transfer characters and tame data between linked servers. It is not a shortcut for uploading an Official .ark file, and it does not replace the backup-and-import procedure above.
Choosing a self-hosted or managed destination
The migration steps are fundamentally the same, but the practical work depends on how much control the destination gives you.
| Consideration | Self-hosted server | Managed hosting |
|---|---|---|
| File access | You normally control the operating system and can copy files directly, but must understand its directory permissions and backup locations. | A File Browser or FTP account may expose the save directory without giving operating-system access. |
| Backup tooling | You must configure and test your own restore process. | The panel may provide restore points and downloadable backups; confirm retention and storage limits. |
| Platform support | You are responsible for platform-specific configuration and compatibility. | The host may document supported platforms, but support does not guarantee that every Official export is compatible. |
| Map and mod support | You control the installed map and mods, subject to your hardware and configuration. | Check whether the host supports the map, mods, and save format before importing. |
| Support availability | There is no external operator unless you arrange one. | Support can inspect server logs or restore files, but you still need to provide accurate filenames and platform details. |
| Current price | Not stated; it depends on hardware, bandwidth, electricity, and administration. | Not stated; plans and import availability vary by provider and region and must be checked at the time of purchase. |
The deciding factor is not the advertised server location or price. It is whether you can stop the server, back up its current files, place the export in the correct map folder, and restore the previous save if the import fails.
A repeatable rollback and maintenance routine
After a successful migration, keep the same discipline for future updates or experiments.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Keep the untouched Official export in read-only or clearly labeled storage.
- Keep the pre-import destination backup until the imported server has been tested and several normal save cycles have completed.
- Create dated backups before installing a major map, mod, or server-version change.
- Record the destination map folder, standard world filename, platform, and the OSS-ID profile filename used for Steam PC.
- When troubleshooting, change one variable at a time and preserve the last known-good copy before testing.
- Never assume that a CrossARK transfer provides a complete backup. It moves selected game data, not a restorable copy of the whole world.
The safest migration is therefore a staged replacement: preserve the source, preserve the destination, upload the complete matching file set, use the destination’s exact map filename, and verify every important object before treating the new server as the primary home of the save.
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.
