How To Move Steam Games To Another Drive Without Re-downloading

Moving a large Steam library to a new drive sounds like it should trigger a full re-download — but it doesn't have to. Steam has built-in tools specifically designed to relocate games while keeping all your installed files intact. Understanding how those tools work, and where they can trip you up, makes the difference between a smooth transfer and a corrupted install.

Why Steam Lets You Move Games Without Re-downloading

Steam stores games in library folders — designated directories on any drive where your games actually live. When you move a game, you're telling Steam to recognize a new library folder location and associate your existing game files with it. As long as the files arrive intact, Steam validates them locally rather than pulling them from the internet again.

This matters most when you're dealing with large games. A 100GB open-world title or a game with several years of DLC can take hours to re-download even on a fast connection. Moving files between drives on the same machine is almost always faster.

Method 1: Using Steam's Built-In Move Feature

This is the cleanest approach and the one Valve officially supports.

Step 1: Add your new drive as a Steam library folder Open Steam → Settings → Storage. Click the + button and select the drive you want to use. Steam will create a new library folder there.

Step 2: Select the game you want to move Still in the Storage panel, select your current library, find the game in the list, check its box, and click Move.

Step 3: Choose the destination Select the new library folder (on your other drive) from the dropdown and confirm.

Steam will copy the game files to the new location, verify them, and then remove them from the original. You don't need to do anything else — the game will launch normally from its new location.

⚠️ One thing to know: The move process uses copy-then-delete, not a true file move. That means both drives need enough free space to temporarily hold the game during transfer. If your source drive is nearly full, this can fail mid-process.

Method 2: Manually Moving Files (For More Control)

If Steam's built-in tool is slow, freezing, or you're moving an entire library at once, the manual method gives you more control.

Step 1: Exit Steam completely Right-click the taskbar icon and choose Exit — not just close the window.

Step 2: Copy the game folder Navigate to your Steam library directory (commonly C:Program Files (x86)Steamsteamappscommon on Windows) and copy the game's folder to the equivalent path on your new drive. Make sure you've already set up a Steam library folder on that drive through Steam's settings first.

Step 3: Also copy the .acf manifest file In the steamapps folder (one level up from common), there's an .acf file for each installed game — something like appmanifest_XXXXXXX.acf. Copy the matching file for your game to the steamapps folder on your new drive.

Step 4: Relaunch Steam and verify Steam reads those manifest files to know what's installed and where. It should now show the game as installed in the new location. Right-click the game → Properties → Local Files → Verify integrity of game files to confirm everything transferred cleanly.

What Affects Transfer Speed and Reliability

Not all moves go equally smoothly. Several variables determine how fast and cleanly this process goes:

If you're moving to an external drive, expect slower transfer speeds and keep in mind that some games with anti-cheat software or shader caches behave differently when launched from external storage.

Moving an Entire Library at Once

If you're migrating everything — not just one game — the process scales up but follows the same logic.

Copy the entire steamapps folder (including common and all .acf files) to your new drive's library path. Then in Steam's Storage settings, add that drive as a library folder. Steam will detect the existing files and register them all as installed.

🗂️ This approach is common when upgrading to a larger drive or switching from an old HDD to a new SSD.

Common Problems and What Causes Them

Game shows as "not installed" after moving: Usually a missing or misplaced .acf manifest file. Check that the manifest is in the steamapps folder on the new drive, not inside common.

Steam tries to re-download anyway: Often caused by a corrupted manifest or a file that failed to copy. Run a file verification — Steam will patch what's missing rather than redownloading the entire game in most cases.

Move option is greyed out in Steam: The destination library folder may not be properly initialized. Remove it from Storage settings and re-add it.

Game launches but crashes: Some games write absolute file paths into configuration files. This is relatively rare but worth searching for in the game's support forums if you hit it.

The Variable That Changes Everything

The right method — built-in Steam tool vs. manual move — and how long it takes comes down to factors specific to your setup: what drives you have, how full they are, whether you're moving one game or twenty, and whether you're on a desktop with internal bays or a laptop with a single external option.

The mechanics work the same way for everyone. Whether the process takes five minutes or three hours, and which approach fits your workflow, depends entirely on what you're working with.