Move a Game Library Between Drives Without Breaking Shortcuts
I’ll show you how to relocate a large game library with the fewest moving parts, preserve saves and launcher records, and avoid stale shortcuts or an unexpectedly full SSD.
Running out of SSD space doesn’t mean you need to uninstall half your library. The risky part is moving game folders without telling the launcher, deleting saves stored somewhere else, or leaving shortcuts pointed at the old drive. A reliable move is less about copying files quickly and more about preserving the relationships between the launcher, installation folder, save data, and shortcut.
The minimalist approach is to move only what needs moving, use the launcher’s own relocation feature whenever it has one, and keep the original files until the game starts successfully from its new location.
Decide what actually needs to move
Start by separating the game’s installed files from its saves, settings, mods, and launcher data. The large installation folder is usually the best target for relocation. Saves are often much smaller and may live in Documents, Saved Games, AppData, a launcher-specific directory, or the game’s own folder. Moving the installation doesn't necessarily move those files with it.
Make a short inventory before touching anything. Note the game’s current drive and folder, the launcher that manages it, whether cloud saves are enabled, where local saves are stored, and whether you use mods or custom launch options. You don’t need to document every file. You do need to know which parts would be difficult to recreate.
If your goal is to free space on a system SSD, moving one or two large games may be more sensible than relocating an entire library. Keep frequently played games on the faster or more convenient drive if load times matter to you, and move less-used titles to a larger secondary SSD or hard drive. The drive’s available capacity, interface, and reliability matter more than giving every game the same location.
Check the launcher’s current move options: Menu names and supported features change, so open the game’s library or installation settings and confirm the available relocation method before copying anything.
Prepare the destination drive
Create a clear library folder on the destination, such as D:\Games on Windows or an equivalent folder on your operating system. Avoid burying a library inside a temporary download directory, a cloud-synchronized folder, or a location you may later rename. A stable path makes shortcuts, mod tools, and troubleshooting easier to manage.
Check the destination’s free space against the size of the game you’re moving. Leave room for updates, shader caches, temporary files, and saved data. A game that barely fits today may fail during a future update because launchers commonly need additional working space while replacing or unpacking files.
On Windows, a normal internal NTFS drive is usually the least troublesome choice for a permanent PC game library. External drives can work, but changing drive letters, disconnecting the device, or using an inconsistent USB connection can make a launcher lose track of the installation. If the destination is removable, assign it a stable drive letter and connect it before starting the launcher.
Avoid changing the destination’s format or permissions solely to make one game fit. File systems and access rules can affect launchers, mods, and games that create files beside their executable. If multiple Windows accounts use the computer, make sure the account that runs the launcher can read, write, and modify the library folder.
Use the launcher’s built-in move process first
A launcher’s relocation tool can update its library record and verify the files after the move. That is safer than dragging a folder in File Explorer and hoping the launcher notices. The exact controls differ, but they are commonly found in the game’s properties, installation settings, storage manager, or library-management screen.
Close the game before moving it and let any update, cloud synchronization, or file verification finish. If the launcher offers a destination library, create or select the library on the new drive. Then select the installed game and choose its move or relocate command. Let the launcher complete the operation rather than interrupting it when the progress appears to pause; large files and verification can take time.
Once the move finishes, start the game from the launcher. A successful launch is useful, but it isn’t the only test. Confirm that your save is present, your settings look correct, and any required mods or launch options still work. If the game supports multiplayer, allow it to reach the normal online or profile screen as well.
Some launchers are better at this than others. A launcher may let you add a new library but not directly move an existing installation. In that case, its supported process may be to begin an installation in the new location, pause it, replace the partial folder with the existing game files, and resume so the launcher discovers and verifies them. The details vary by launcher, so follow its current documentation rather than applying a procedure from a different service.
If a launcher only offers uninstall and reinstall, don’t assume that uninstalling first is harmless. The uninstall process may remove the files you intended to reuse, and it may or may not remove saves. Back up the installation and save data first, then use the launcher’s current “locate,” “scan,” or verification feature if available. If none exists, reinstalling to the new drive may be the cleanest option, provided your saves and settings are backed up.
Protect saves, settings, and cloud data
Cloud saves reduce the risk of losing progress, but they aren’t a complete backup. Sync conflicts, offline play, disabled cloud support, or a damaged local file can leave you with only one copy. Before moving a valuable game, make a separate copy of its save folder to another drive or a clearly named backup location.
Look for save locations in the game’s documentation, the launcher’s support pages, and common operating-system folders. On Windows, likely locations include Documents\My Games, Saved Games, and subfolders under %AppData% or %LocalAppData%, but there is no universal standard. Some games store saves inside the installation directory, while others use a publisher account or a platform-specific protected location.
Don’t overwrite a newer save with an older backup just because the folder names look similar. If cloud synchronization presents a conflict, compare modification times and, when the game provides one, choose the copy that contains your latest progress. Keep the backup until you have opened the game and confirmed the correct profile, settings, and save slots.
Moving the installation normally doesn’t require moving saves. In fact, leaving saves in their existing supported location is often the simplest choice. Move them only when you have a specific reason, such as relocating a large user-data folder or changing the operating system. If you do move them, update the game’s supported path or configuration rather than relying on an unexplained shortcut or symbolic link.
Repair shortcuts and related tools
A desktop shortcut usually stores a path to an executable. When that executable changes from something like C:\Games\Title\game.exe to D:\Games\Title\game.exe, the old shortcut may continue to exist but no longer launch anything. The launcher’s library shortcut may be repaired automatically, while a shortcut you created yourself may not be.
After the move, delete or edit stale shortcuts and create a fresh one from the launcher or the new executable. Check the shortcut’s target, working directory, launch arguments, and icon if you use custom settings. A shortcut that opens the game but omits an argument for a mod manager, language, or graphics option still needs attention.
Other tools can retain the old path too. Review mod managers, overlay tools, recording software, backup jobs, desktop search indexes, scripts, emulator front ends, and game-specific configuration files. If you use a mod manager, point it to the new installation before launching through it. Some mods also place files in a separate user folder, so a successful unmodded launch doesn’t prove the entire setup is restored.
If a launcher refuses to recognize the moved files, avoid repeatedly starting and canceling installs in different folders. Confirm the exact library path, check that the account owns the game, and use the launcher’s locate or verify function. As a last resort, a directory junction or symbolic link can make an old path redirect to a new drive, but treat that as a compatibility workaround rather than the default method. It adds another dependency and can confuse future maintenance, backups, or uninstallers.
Test before deleting the old copy
The old folder is your easiest recovery option, so don’t remove it immediately. First, close and reopen the launcher, then start the game from the launcher and from any shortcut you intend to keep. Confirm that the launcher reports the correct installation location and doesn’t begin downloading the entire game again.
Check one save from the main menu, not only the title screen. Test settings that matter to you, such as controller detection, graphics configuration, mods, and launch arguments. If the game uses an anti-cheat component or separate updater, let it complete its normal checks. For games that require an internet connection, verify that the account and online features still work.
When everything is correct, compare the old and new folder sizes and check the new drive’s free space. Don’t judge success only by the amount of space freed on the original SSD: the launcher may have left a download cache, a patch file, or a duplicate partial folder behind. Remove only the confirmed old installation and temporary files, not folders whose purpose you haven’t identified.
Wait through at least one normal launch and, for an important game, a save-and-reload cycle before treating the move as complete. If the game fails, restore the old path or use the launcher’s verify function while your original files are still available. This is much easier than recovering a deleted installation and trying to reconstruct missing saves at the same time.
A sensible routine for future moves
For the smallest reliable process, back up saves, prepare a permanent destination with enough update space, and use the launcher’s move feature. If the launcher lacks one, use its supported locate or verify workflow instead of inventing a folder structure. Recreate shortcuts after the move, then test saves and related tools before deleting anything from the old drive.
You don’t need to reorganize every game at once. Move the largest or least-used titles first, keep a consistent library structure, and record the new location if you use mods or scripts. That approach frees SSD space without turning a storage cleanup into a full rebuild—and it leaves fewer hidden paths to break the next time you change drives.