Move your solo Dragonwilds world to a 1.0 dedicated server
Stop the server, back up Savegames, empty that folder, then copy your .sav from %LOCALAPPDATA%\RSDragonwilds\Saved\Savegames without renaming it. Renaming breaks progress. Restart to load the world.
A Dragonwilds world is one .sav file. The filename is part of the
world. Copy it onto the 1.0 dedicated server with that name intact.
Xbox / PC Game Pass worlds use WGS storage first. Follow the Xbox and Game Pass save-migration guide and use the free WGS-to-SAV converter to extract your world before following the upload steps below. PS5 and Nintendo Switch 2 worlds do not currently have a supported migration route.
Do not rename the .sav. Changing the filename breaks progress. Buildings and character
advancement can look wiped even though the file is still on disk. If you already renamed it,
change it back to the original name and restart.
The move is five steps. Do them in this order:
- Stop the server.
- Back up
Savegames. - Empty the server
Savegamesfolder. - Copy your
.savin without renaming it. - Restart.
1. Find your solo save
On the Windows client, worlds live here:
%LOCALAPPDATA%\RSDragonwilds\Saved\SavegamesPress Windows + R, paste that path, and press Enter. Each world is one
.sav. The name matches the world you created in-game, without extra suffixes.
Windows treats Savegames and SaveGames as the same folder. Use the
%LOCALAPPDATA% path above so you do not have to hunt through hidden AppData.
There is no documented native Linux client path. The Steam game lists Windows.
If you play through compatibility layers, look under that same
RSDragonwilds/Saved/ tree for a Savegames or SaveGames folder and copy
the .sav you actually play.
2. Server save path and casing
When a dedicated server starts, it loads the latest .sav in its save folder.
If that folder is empty, it creates a default Standard world.
The server folder is:
RSDragonwilds/Saved/SavegamesWindows is case-insensitive. Savegames and SaveGames are one folder. Open
RSDragonwilds/Saved/Savegames in Files or over SFTP and put the .sav there.
Linux is case-sensitive. Savegames and SaveGames are different directories. After
the first boot, look at the folder the server already created under
RSDragonwilds/Saved/ and copy into that folder. Do not mkdir a second copy with
different capitalisation — the process will ignore it and generate a new world in the
other one. berrybyte servers are Linux; use the Files tab and match what is already on
disk.
Empty the folder. Do not delete Savegames itself — remove the files inside, leave the
directory.
3. Move the world
Stop the server
Wait until it reports offline. A running process can write a new .sav over the file you
are about to upload.
Back up Savegames
Copy every file in the server Savegames folder somewhere safe — your PC, another host
folder, or Backups. Keep the originals until you have joined and
confirmed the world.
Empty the server Savegames folder
Remove the .sav files inside. Leave the folder in place. If you skip this, the server
may load a newer default world instead of yours.
Copy the .sav without renaming it
Upload your local .sav from %LOCALAPPDATA%\RSDragonwilds\Saved\Savegames into the
server save folder. Keep the exact filename. Do not add _backup, a date, or a new
world name. Over plain FTP, use binary mode.
Restart and verify
Start the server. In-game, open Worlds → Public and search the original world name,
case sensitive, without .sav. Join and check buildings and character progress before
anyone plays further. Leave, rejoin, and restart once to confirm it stuck.
The don't-rename step is the whole guide. A file named Ashenfall_final.sav is a different
world from Ashenfall.sav. The server can boot either. Only the original name keeps your
progress.
On berrybyte, use the Files tab (or SFTP) after the server is stopped. Self-hosters
copy into the same RSDragonwilds/Saved/Savegames tree on the machine that
runs Steam app 4019830.
4. After the upload
Search the Public tab for the filename, not the Server Name. Server Name
is the "Created By" label. The world players type is the .sav basename, and
it is case sensitive.
Do not rename the uploaded file to match World Name in the panel. If those
two disagree, stop the server and update the panel field to the original .sav
basename so Overview shows the right join target. That setting does not rename
or convert the world file.
The server still needs an Owner ID (your 32-character Player ID from the bottom of in-game Settings) before it will start. Uploading a world does not remove that requirement. See RuneScape: Dragonwilds server setup and 1.0 guides.
Editing DedicatedServer.ini while the server is running discards the change. Stop the
process, edit, then start.
Next steps
Player cap, Owner ID, and the rest of the 1.0 hosting pages.
How much RAM do you need?Official formula: 2 GB base plus 1 GB per player. 8 GB for a full six.
Start a hosted server4- and 6-player plans with Owner ID and world name set from the panel.
Back up your serverKeep a copy before the next upload or game update.
Frequently asked questions
Why did my Dragonwilds progress reset after I uploaded a world?
The .sav was renamed. Dragonwilds ties progression to the original filename. Copy the file into the server Savegames folder with the same name, including capitalisation, then restart. If the server already booted on a renamed file, restore the original name and restart again.
Where is my solo Dragonwilds save on Windows?
Client worlds live at %LOCALAPPDATA%\RSDragonwilds\Saved\Savegames. Press Windows + R, paste that path, and press Enter. Each world is one .sav file named for the world you created.
What is the dedicated-server save path on Windows and Linux?
Jagex's dedicated-server guide loads the latest .sav from RSDragonwilds/Saved/Savegames. Windows treats Savegames and SaveGames as the same folder. Linux is case-sensitive, so put the file in the folder the server already created on first boot and do not make a second differently-cased copy.
Do I change World Name after uploading a .sav?
Keep the .sav filename unchanged. Players search the original filename without .sav. If berrybyte Overview shows a different configured World Name, update that field while the server is stopped so the displayed join target matches, but never rename the save to match the panel.