Starfield Save Location and New-PC Transfer Checklist

Moving a Starfield character to another PC should begin on the machine that still has the working save. Confirm the checkpoint there, record the installation details and create an independent copy before making changes on either system. This guide concerns local Windows files; it does not assume that every storefront uses an interchangeable save format.

Community save download

New Game Plus save file — hosted on Nexus Mods. This listing provides a New Game Plus checkpoint. Review its original game build, character details and installation instructions before using it on a different version.

View download on Nexus Mods

This opens the original download page, not an instant download from SaveGamesDL. Follow the host’s sign-in and download prompts. Completion labels belong to the uploader; we have not independently verified completion, compatibility or file safety. Preserve your own saves before importing anything.

Reference Windows save path

Bethesda’s character-loading support article gives a reference location under Documents and My Games. Use this path as a starting point for the installation covered by that documentation: 1

%USERPROFILE%\Documents\My Games\Starfield\Saves

Verify the active location with a new save and its modification time after closing the game. A redirected Documents folder or different platform setup may require different instructions. If the directory is missing, investigate your specific installation rather than assuming a newly created empty folder will become the game’s save location.

Compare both PCs before copying

Record the game build and storefront on the old and new systems. Include relevant DLC, mods and any profile-specific settings. “Both are PC versions” does not establish that every raw file can be transferred without further checks.

On the destination, launch the game normally and create a small test save where appropriate. This establishes that the new installation can save and gives you evidence of its active folder. Back up the destination too; it may already contain progress worth keeping.

Make a transfer archive from a closed game

Open the last known-good checkpoint on the old PC and note the character and location. Exit the game before copying files, then create an independent backup outside the active save directory. Prepare the transfer archive from that copy rather than from a folder the game may still be writing to.

Give the archive a descriptive name and include a short note with the checkpoint, build, storefront and dependencies. Keep personal account identifiers out of any version you intend to share publicly.

Test one save on the new installation

1. Confirm that both source and destination backups exist.
2. Extract the transfer archive into a temporary folder and inspect its structure.
3. Compare the documented environment and stop if a necessary dependency is unresolved.
4. Add one identifiable checkpoint to the verified destination location, preserving existing files when names collide.
5. Load it and inspect the expected character, inventory and location.
6. Create a separate save on the new PC, exit and load that save again.

Only move the rest of the archive after this limited test works. Keep the old machine’s backup until you have independently verified the migrated progress. Copying a directory successfully is not the same as confirming a playable transfer.

Handle synchronization separately

If an official account-based synchronization method is available for your setup, distinguish that process from manual file copying. Mixing both during the first test makes it harder to understand which version you are loading. Preserve local data before responding to any cloud conflict, and compare actual progress rather than timestamps alone.

Frequently asked questions