The default savegame location is




Just copy the whole remote folder somewhere safe.

And when necessary you delete the existing remote folder and replace it with your backup.

I do a daily backup and just started naming the copies by date.

If you do not like to manually backup, I recommend to you running a simple yet very effective backup script.

You can download a version here by Tacumoto[next.nexusmods.com]
https://www.nexusmods.com/monsterhunterwilds/mods/379

After you set it up, the script automatically runs whenever you start Monster Hunter Wilds.

It automatically makes a copy, put it in an easy to track folder.



You can easy access your Monster Hunter Wilds game folder by

Right-click on Monster Hunter Wilds in your Steam Library -> Manage -> Browse local files




Right-click on the script file and select Edit in Notepad



Specifically set your Steam ID into the file, so it knows where your savegame is located



You can find the necessary ID via your Steam Settings





And the location where you want your backup to be stored




Right-click on Monster Hunter Wilds in your Steam Library -> Properties



Enter in the field Launch Options



Now, every time you launch the game, the script will automatically make a copy of your savegame for you BEFORE starting the game, preventing savegame issues which can occur BEFORE starting the game, but not when exiting the game.

Right-click on Monster Hunter Wilds in your Steam Library -> Properties -> uncheck the option for Steam Cloud



This will reduce the risk of your savegame being destroyed by a faulty Steam Cloud synchronisation.

The Synchronized Photo Save feature is unfortunately another piece which can break savegames. I do not recommend using the feature at all, especially considering that it is a feature which only makes sense for console. On PC you can make higher quality screenshots by using Steam's Overlay Screenshot feature (default press "F12").

Save the game first



Then quit the game without saving



By separating these actions and giving the game more time to process the save, we reduce the risk of savegame corruption when closing the game to an absolute minimum.

Most issues, including Steam Cloud synchronisation failures, occur after the game is closed - for example, when the game is still processing and writing the savegame file, but Steam Cloud is already trying to upload it - causing desynchronisation and resulting in a corrupted savegame.

In short, if you use mods that affect your savegame, there is no guarantee that your savegame will ever be safe.

Even a mod that works today may become incompatible in the future, and any changes you make to your savegame may inevitably and irreversibly corrupt it, rendering it unplayable.

The easiest way to check whether your savegame is corrupted or not is to force the game to load the game without a savegame.

To do this, make sure that Steam Cloud is disabled for the game, so that it does not interfere with the test by downloading a corrupted save game when it detects none.

Right-click on Monster Hunter Wilds in your Steam Library -> Properties -> uncheck the option for Steam Cloud



Go then to your savegame folder


and rename the remote folder into something else





If you now start the game, it will miss the savegame and initialise a new one.




A. If the game still crashes regardless of your savegame, then it is probably not a corrupted savegame that is causing the crash on startup.

B. If the game continues to run normal with a new savegame, then it is most likely that your savegame got corrupted and cannot be used anymore.

Unfortunately, there is currently no known way to recover a corrupted savegame, whether caused by a desynchronisation problem, a DRM problem or mods.

As savegames are stored locally and not on Capcom's servers, Capcom Support cannot provide any assistance.



The best course of action is to use the methods outlined in this guide to reduce the risk of losing your savegame, and to have a backup ready if you need one.