A single modern AAA game can eat 100 GB or more, and a modest 512 GB SSD fills up faster than most players expect. When the “disk write error” or “not enough space” warning appears, the fix is usually not a new PC. It is moving a few installed games to a roomier drive. The good news: Steam has a built-in tool for this, and it takes minutes rather than hours. The catch is that a few small mistakes can leave a game broken or force a full re-download.
This guide covers the official method, the manual fallback, and the practical details that trip people up.
Why Moving Games Beats Deleting and Reinstalling
Reinstalling sounds simple, but it costs time and bandwidth. A 90 GB title on a 50 Mbps connection takes roughly four hours to download, assuming nothing interrupts it. Moving the same game between drives on the same machine is limited only by drive speed, often finishing in a fraction of that time.
There is also a data angle. Many households have monthly bandwidth caps, and some free steam games are large enough that repeated downloads add up. Moving files locally avoids the network entirely. (Steam (service)))
Storage layout matters for performance too. Putting a competitive shooter on an SSD and archiving a single-player backlog on a slower hard drive is a sensible split. Players who keep a large library of best survival games on steam often find that a mix of fast and slow drives works better than one giant, nearly full SSD. (Steam Support)
Before You Start: Two Things to Check
First, confirm the destination drive has enough free space. A cross-drive move copies files before deleting the originals, so the target needs room for the full install size. Steam’s storage settings show each game’s size, which makes the math easy.
Second, decide whether you need a new library folder at all. If the destination drive has never held Steam games, you must create a library folder there first. This is a one-time step per drive.
How to add a library folder on another drive
- Open Steam and go to Settings.
- Select Storage (older clients label this area differently, usually under Downloads).
- Choose Add Drive or the plus icon next to the drive list.
- Pick the drive and folder, then confirm.
Once the library exists, Steam treats that drive as a valid target for installs and moves.
The Official Method: Move Install Folder
This is the method to use first. It is built into the client, it updates Steam’s records automatically, and it avoids the file-matching errors that plague manual moves.
- Open your Library and find the game.
- Right-click the game and choose Properties.
- Go to the Installed Files tab.
- Click Move install folder…
- Select the destination library from the dropdown.
- Confirm and wait for the progress bar to finish.
Steam handles the rest. The game stays installed, and its shortcut keeps working. When the move completes, the game launches from the new location with no extra steps.
A useful detail: moves within the same drive are nearly instant because the files are effectively renamed, not copied. Moves across drives take real time proportional to the install size. A 120 GB game moving from an NVMe SSD to a SATA SSD might take several minutes; the same game moving to an external USB drive can take much longer.
What to do if “Move install folder” is missing or greyed out
A few situations cause this. The destination library may not exist yet, the drive may be full, or the game may be mid-update. Let any pending download finish, then try again. Games installed through a separate launcher that Steam merely tracks can also behave oddly, since Steam does not fully own those files.
The Manual Method: Moving Folders and Manifest Files
Sometimes the official tool fails, or the client refuses to cooperate. The manual approach works, but it requires care. Steam tracks installs through two things: the game folder itself and a small manifest file named `appmanifest_.acf` that lives in the `steamapps` folder.
Both must end up in the same library, or Steam will think the game is missing.
- Close Steam completely. Not minimized; exited.
- Open the source drive’s `steamappscommon` folder and locate the game’s folder.
- Cut that folder and paste it into the destination library’s `steamappscommon` folder.
- Go back to the source `steamapps` folder and find `appmanifest_.acf` for that game.
- Move that file into the destination library’s `steamapps` folder.
- Restart Steam and check the library.
If the game shows as installed and launches, the move worked. If Steam shows it as uninstalled or wants to download everything again, the manifest did not land in the right place.
Finding the app ID is the fiddly part. The number appears in the game’s store page URL, and the manifest filename uses it directly. Copying the wrong manifest, or moving the folder without it, is the single most common mistake here.
Never move folders while Steam is running
This is the mistake that breaks installs. Steam holds file handles and writes to its own records while running. Moving files underneath it creates a mismatch between what Steam believes and what is actually on disk. The result ranges from a harmless re-verify to a corrupted install that needs a full redownload.
The same rule applies to renaming folders, deleting `steamapps` contents, or reorganizing drives. Close the client first, every time.
Verify Integrity After Any Move
Whether the move was official or manual, running a verification pass is cheap insurance.
- Right-click the game and open Properties.
- Go to Installed Files.
- Click Verify integrity of game files.
Steam compares the local files against its records and re-downloads anything missing or damaged. For manual moves, this step catches manifest mismatches and stray files. For official moves, it usually confirms everything is intact.
A verification on a large game can take a while, but it downloads only what is actually wrong. In most cases, nothing is.
Which Drive Should Each Game Live On?
Not every game deserves fast storage. The table below is a practical starting point.
| Game type | Best drive | Why |
|---|---|---|
| Competitive multiplayer | NVMe or SATA SSD | Fast load times, fewer stutters during asset streaming |
| Large open-world single-player | SSD if space allows | Long loads and heavy texture streaming benefit most |
| Backlog and rarely played titles | Hard drive or external SSD | Frees fast storage without deleting anything |
| Mod-heavy games | Same drive as before the move | Some mod managers store absolute paths and break on relocation |
| Games with external launchers | SSD, verified after moving | Extra launcher files may need a re-check |
Modded installs deserve special attention. Mod managers often record the exact folder path, so moving a game can break every mod at once. Check the mod manager’s settings after a move and repoint it if needed. This is one of the few cases where a clean reinstall of the mods is faster than debugging.
Common Mistakes and How to Avoid Them
Moving the folder but not the manifest. Steam sees an orphaned folder and an install it cannot find. Always move both.
Leaving Steam open during a manual move. Covered above, but worth repeating because it causes most failures.
Assuming an external drive is always safe. USB drives can disconnect mid-session, and some games handle that poorly. External storage works well for archiving, less well for games played daily.
Ignoring free space on the destination. A move that runs out of room partway through can leave a half-copied install. Check first.
Forgetting about save files. Most modern games store saves in the cloud or in the user profile folder, not the install directory, so moves are usually safe. A few older titles keep saves next to the executable. Back those up before moving anything.
Skipping verification after a manual move. It takes minutes and catches problems before they become a corrupted save or a crash at launch.
Players who also juggle a console library will recognize the pattern; the same storage discipline that keeps a best N64 games collection organized applies to a modern Steam library, just with bigger files.
Steam’s Storage Manager Does More Than Moves
The Storage settings page is worth a look even if nothing needs moving today. It shows every library folder, how much space each game uses, and which drive is filling up. From there, games can be moved, uninstalled, or scheduled for a later download.
It also reveals a common surprise: shader cache folders and leftover depot files can occupy tens of gigabytes. Clearing those occasionally reclaims space without touching a single game.
For players building a library from scratch, the same page makes it easy to keep smaller titles on the system drive and route big installs elsewhere. Anyone browsing the best indie games on steam will find most of them small enough to fit anywhere, which makes them good candidates for a cramped boot drive.
When a Move Goes Wrong
If a game will not launch after moving, the recovery path is short.
First, verify integrity. Second, if that fails, uninstall the game (which removes the broken records) and reinstall it directly to the destination library. The download is annoying, but it produces a clean state.
If Steam itself is confused, check that each library folder still appears in Storage settings. A library pointing at a drive letter that no longer exists, common after unplugging an external drive, causes errors across the whole client. Removing the stale entry usually fixes it.
One more habit worth building: after any drive change, launch each moved game once. A quick load screen confirms the install is healthy far more reliably than a file listing.
Conclusion
Moving Steam games between drives is a solved problem, and the built-in Move install folder tool handles it cleanly for almost everyone. The manual method exists for the cases where the client misbehaves, and it works reliably as long as the game folder and its manifest travel together and Steam stays closed during the process.
The practical rules are simple. Check free space before starting, create the destination library first, close Steam for any manual work, and verify integrity afterward. Do those four things and a move takes minutes instead of an afternoon of re-downloading.
Storage fills up. That is normal. What matters is having a routine for managing it, so the next big release does not arrive to find a full drive and no plan.
Frequently Asked Questions
How long does it take to move a Steam game to another drive?
It depends on the drives and the game size. Moves within the same drive are nearly instant because files are renamed rather than copied. Cross-drive moves copy the full install, so a 100 GB game might take several minutes on fast SSDs and considerably longer on a hard drive or external USB drive.
Does moving a Steam game delete my save files?
In almost all cases, no. Most games store saves in the cloud or in a user profile folder outside the install directory, so relocating the game does not touch them. A small number of older titles keep saves beside the executable, so backing up the save folder first is a sensible precaution.
Can I move Steam games to an external hard drive?
Yes. Add the external drive as a library folder in Steam’s Storage settings, then use Move install folder. External drives work well for archiving games you play occasionally. For games played daily, an internal drive is more reliable because a dropped USB connection mid-session can cause problems.
Why is the “Move install folder” option greyed out?
The usual causes are a missing destination library, insufficient free space on the target drive, or a pending update for that game. Let any download finish, confirm the library exists, and check available space. Games managed by a separate launcher can also behave oddly because Steam does not fully control those files.
Is it safe to move game folders manually without Steam?
It works, but only if done carefully. Close Steam completely, move both the game folder in `steamappscommon` and the matching `appmanifest` file into the new library, then restart the client and verify integrity. Moving folders while Steam is running is the most common cause of broken installs.
Do I need to redownload a game after moving it?
No, not if the move succeeded. Both the official tool and the manual method relocate existing files, so nothing is downloaded again. A verification pass afterward may fetch a small number of missing files, but the bulk of the install stays exactly where it was moved.
