TL;DR
Steam Machine game install locations sit inside a Steam library’s steamapps/common folder, while numbered appmanifest files in steamapps tell Steam which games belong there. On SteamOS or Linux, the usual library is under your home directory; Windows commonly uses C:\Program Files (x86)\Steam, and every extra drive can contain another SteamLibrary folder.
Your 100 GB game can appear to vanish while every byte still sits on the drive. Steam may lose track of a library, a removable SSD may mount somewhere new, or you may be searching the visible desktop folders while SteamOS keeps the files behind a hidden dot folder.
This guide gives you a practical map of Steam storage across SteamOS and Linux, Windows, and macOS. You will learn where the default install directory sits, how each added library repeats the same structure, and why game files, save files, workshop downloads, and shader caches often live in separate places.
The distinction matters when you replace a drive, install a mod, rescue a save, or clear space before a large update. Think of Steam as a railway network: steamapps is the station, common holds the parked trains, and appmanifest files tell the dispatcher what has arrived. Once you can read that map, a supposedly missing steam machine game becomes a folder you can locate, move, and reconnect without tearing up the tracks.
Open a game’s Properties > Installed Files page and use Browse when you need its exact folder; this avoids guessing among multiple Steam libraries.
Treat steamapps/common and the matching appmanifest_[AppID].acf file as a pair when recovering a manually copied installation.
Back up saves separately because many live in Documents, AppData, macOS Library folders, Linux user folders, or SteamOS compatdata rather than beside the game.
Move games through Steam’s Storage controls so the client transfers the files and updates its library records together.
When many games disappear at once, check the drive mount and registered library path before deleting files or downloading the collection again.
Steam Machine Game Install Locations Explained
Installed games normally sit inside a Steam library’s steamapps/common folder. The matching numbered manifest one level above tells Steam that the game belongs there. When either the library path or its label goes missing, a 100 GB game can appear to vanish while every byte remains on the drive.
Executables, maps, textures, audio and other installed game files.
The AppID record connecting a title to its Steam library.
Properties → Installed Files → Browse reveals the exact active folder.
Repeated inside every registered library.
The familiar named installation folders.
The number embedded in each manifest filename.
Internal, SD card, USB and secondary drives.
Three platforms, one repeating structure
The path before steamapps/common changes by operating system and selected drive. Added libraries repeat the same internal structure.
Hidden at home
/home/username/.steam/steam/steamapps/common/
The .steam folder is hidden. Some installations link through ~/.local/share/Steam. On Steam Deck, the username is commonly deck.
Program folder or drive library
C:\Program Files (x86)\Steam\steamapps\common\
A second disk may instead use a path such as D:\SteamLibrary\steamapps\common\. The “x86” location remains common even on 64-bit systems.
Inside your user Library
~/Library/Application Support/Steam/steamapps/common/
The user Library is hidden in Finder by default. The active game library is normally user-specific rather than beside the Steam icon in Applications.
Open the game’s Properties → Installed Files → Browse. This avoids guessing among an internal SSD, microSD card and removable drive with nearly identical folder structures.
Steam game backup external hard drive
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Steamapps is a filing system
A library is more than a row of named game folders. Steam tracks payloads, ownership records, community content, temporary downloads and compatibility data separately.
The root registered under Steam’s Storage settings.
The station connecting files, manifests and support data.
The parked game folders containing the main payload.
The title’s executable, maps, assets and shipped tools.
The nearby record identifying the installed title.
Think of Steam as a railway network: steamapps is the station, common holds the parked trains, and appmanifest files tell the dispatcher what has arrived.
Formal Methods for Industrial Applications: Specifying and Programming the Steam Boiler Control (Lecture Notes in Computer Science, 1165)
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Installation, saves and support data are not the same thing
Copying common may preserve the game while leaving progress, mods or cached data behind. Back up each layer according to what you actually need.
| Data type | Typical location | Moves with game? | Safe to rebuild? | What it contains |
|---|---|---|---|---|
| Game installation | steamapps/common/GameName | ✓ Through Steam | ✓ Re-downloadable | Executables, maps, textures, audio and shipped tools. |
| App manifest | steamapps/appmanifest_[AppID].acf | ✓ Client-managed | ~ Usually recoverable | Install directory, state, AppID and library record. |
| Local saves | Documents, AppData, Library, user folders | ✗ Often separate | ✗ Back up first | Progress, profiles, settings and user-created data. |
| Proton prefix | steamapps/compatdata/[AppID]/pfx | ✗ Separate layer | ~ Saves may not be | A Windows-like C: drive for games running through Proton. |
| Workshop content | steamapps/workshop/content/[AppID] | ~ Subscription-based | ✓ Re-downloadable | Subscribed maps, mods and community files. |
| Shader cache | steamapps/shadercache/[AppID] | ✗ Not essential | ✓ Rebuildable | Compiled shader data that can reduce stutter. |
What occupies the drive
Conceptual scale only: a game’s payload is normally much larger than its tracking record, while caches and add-ons vary by title.
Preserve progress separately
Steam Cloud only synchronizes files selected by each game’s developer. A local backup still matters before reinstalling an operating system or replacing a drive.
- Check Steam Cloud status and allow synchronization to finish.
- Inspect Documents, Saved Games and AppData on Windows.
- Inspect user Library folders on macOS.
- Check ~/.local/share and ~/.config for native Linux games.
- Back up relevant compatdata prefixes for Proton titles.
Steam game move without re-download
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Reconnect the tracks before downloading again
When several games disappear at once, the likely problem is the library connection—not simultaneous deletion of every game folder.
Confirm the SSD, SD card or external disk is connected and mounted at the expected path.
Open Steam’s Storage settings and confirm that the library root is still registered.
Look for both the named folder in common and its matching appmanifest file.
Choose the same library when installing; Steam may detect and verify the existing payload.
Use Installed Files controls to replace only missing or damaged content.
Treat steamapps/common/GameName and the matching appmanifest_[AppID].acf as a pair. Close Steam before manually handling manifests because the running client may rewrite them. Prefer Steam’s Storage or Move Install Folder controls whenever available.
Steam game folder organizer
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Find the Exact Folder Steam Uses on Your System
Steam Machine Game Install Locations usually end in steamapps/common, but the path before that point depends on your operating system and chosen library. On SteamOS or Linux, start in your home directory; on Windows, check the Steam program folder; on macOS, inspect your user Library rather than the Steam icon in Applications.
| Platform | Common default library path | What may confuse you |
|---|---|---|
| SteamOS or Linux | /home/username/.steam/steam/steamapps/common/ | .steam is hidden; some systems point it to .local/share/Steam |
| Windows | C:\Program Files (x86)\Steam\steamapps\common\ | Another drive may use D:\SteamLibrary instead |
| macOS | ~/Library/Application Support/Steam/steamapps/common/ | Your user Library is hidden in Finder by default |
Steam typically installs a game in the default install directory selected under the client’s storage settings [1]. A 64-bit Windows PC still commonly uses the Program Files (x86) path because the Steam client grew from a 32-bit application. If you chose a second disk during installation, however, the real folder may be D:\SteamLibrary\steamapps\common\GameName.
On a SteamOS box, open the desktop file manager and turn on hidden files, often with Ctrl+H. The pale folders beginning with a dot will appear, including .steam. For example, if you installed Hades in the internal library, you may find its files under /home/deck/.steam/steam/steamapps/common/Hades, though usernames and links vary by device image.
For the fastest answer, let Steam point at the files. Open the game’s properties, choose Installed Files, and select Browse; menu wording can shift between client versions [1]. That button avoids guessing, especially when three nearly identical library folders sit across an internal SSD, a microSD card, and a USB drive.
Read the steamapps Folder Without Getting Lost
Steam Machine Game Install Locations make sense once you read steamapps as a small filing system. The common folder contains playable game files, appmanifest files identify installed titles, workshop holds subscribed community content, and downloading or temp folders hold unfinished work that Steam may later clean up.
Open steamapps and you may see common beside files named appmanifest_570.acf or appmanifest_730.acf. The number is the game’s Steam AppID, not a random serial. Steam reads that lightweight manifest to learn the install directory, update state, disk usage, and ownership details associated with the library.
Imagine moving a labeled crate between two garages. The game folder is the heavy crate, while the appmanifest is its paper label; move the crate without the label and Steam may stare at a full shelf and call it empty. That quiet contradiction explains why a copied game sometimes produces an Install button even though its textures, music, and executables occupy dozens of gigabytes.
- common: the main folders for installed games and many locally shipped tools.
- workshop: downloaded Workshop items, commonly arranged by AppID.
- downloading: partial files used while a download or update is running.
- shadercache: compiled shader data that can reduce stutter but may be rebuilt.
- appmanifest_[AppID].acf: the record connecting a title to that library.
Suppose common contains a game folder but Steam wants to download the title again. Do not delete the folder in frustration. Confirm that the correct library remains listed in Settings > Storage, then start installation into that same library; Steam may discover and verify the existing files instead of fetching every byte [1]. Keep Steam closed if you manually handle manifests, since the client can rewrite them and turn organized chaos into ordinary chaos.
Separate Game Installations From Saves Before You Back Up
Steam Machine Game Install Locations usually contain the executable, maps, audio, and textures, but your save files may live elsewhere. Many games place saves in a user profile folder or a Proton prefix, while Steam Cloud synchronizes only the files chosen by that game’s developer [2]. Backing up common alone can preserve the game and lose your progress.
On Windows, check Documents, Saved Games, and folders beneath AppData. On macOS, saves often sit beneath ~/Library/Application Support or another user Library subfolder. Native Linux games use several patterns, including ~/.local/share and ~/.config, so the game’s documentation or PCGamingWiki entry can help when the path is not obvious.
Windows games running through Proton on SteamOS add another layer. Steam commonly creates a numbered directory under steamapps/compatdata, then builds a small Windows-like pfx tree inside it. A game’s AppData-style save may sit several folders deep, like a tiny apartment hidden inside a warehouse, complete with a simulated C: drive and user profile.
For example, you might copy a 70 GB role-playing game from common before reinstalling SteamOS, then discover that your 80-hour character lived in compatdata or Steam Cloud. You saved the orchestra and lost the score. Check the game’s Steam Cloud status in the client, wait for synchronization to finish, and make a separate copy of any local saves you cannot replace [2].
Back up both halves: the installation saves download time, while the user-data folder or confirmed cloud copy preserves your actual play history.
Cloud synchronization adds convenience, not a universal guarantee. A game may omit settings, screenshots, mods, or certain save slots from its cloud rules, and a conflict can ask you to choose between local and remote copies. Read the dates and file sizes before choosing; a fresh, empty save created this morning should not quietly replace last night’s hard-won campaign.
Move a Game to Another Drive Without Downloading It Again
You can move an installed Steam game through the client’s Storage controls or the game’s Installed Files properties, avoiding a full download. Add the destination as a Steam library first, select the title, choose the move command, and let Steam transfer both the files and its installation record [1].
- Connect the destination drive and confirm it has enough free space for the game plus working room.
- Open Steam > Settings > Storage and add the drive or library folder if it is not already listed.
- Select the installed game, open the move control, and choose the destination library.
- Wait until Steam reports completion; do not unplug an external drive while files are moving.
- Launch the game once, then check saves, mods, and controller settings before removing any old manual backup.
For a concrete example, say your internal 256 GB SSD has only 18 GB free and a 92 GB game needs a 30 GB update. Moving that game to a 1 TB library clears the bottleneck without another overnight download. Steam carries the files and updates its records, saving bandwidth and your evening.
The built-in move feature is safer than dragging folders in a file manager because it handles the game directory and manifest relationship. It also reduces permission mistakes on Linux, where a library owned by the wrong user can block updates. The move may still take time: shifting 100 GB to a mechanical USB drive can sound like a faint gravel rattle and run far slower than an internal NVMe SSD.
If the move button is unavailable, pause active downloads, check that the target library is writable, and confirm the drive uses a compatible file system. Removable drives can also vanish after a reboot if SteamOS mounts them differently. Use a stable library selected through Steam’s storage screen rather than building a fragile chain of manual symbolic links.
Mods deserve a separate check. Workshop items may follow Steam’s own records, while manually installed files can sit inside the game directory and ride along unnoticed. A mod manager may keep staging files somewhere else, so open one heavily modded save after the move before you celebrate with a clean old drive.
Choose the Drive That Gives You Space Without Painful Loading
The best Steam library drive balances capacity, speed, connection quality, and reliability. An internal SSD usually gives the quickest loading and fewest disconnects, while an external SSD offers flexible space with a cable attached. A hard drive costs less per gigabyte but can stretch loading screens in games that stream large assets.
| Storage choice | Best use | Main tradeoff |
|---|---|---|
| Internal NVMe or SATA SSD | Large open worlds and frequently played games | Higher cost per gigabyte |
| External USB SSD | Portable libraries and easy expansion | Cable, port, and enclosure speed can limit it |
| Internal or external hard drive | Older games and bulk archives | Longer loads and slower large updates |
| microSD card | Compact SteamOS handheld storage | Write speed and endurance vary by card |
An SSD does not normally raise frame rate once every needed asset is loaded, but it can cut waiting and reduce asset-streaming pauses. A fast drive behind a slow USB connection is like a fire hose attached to a drinking straw. Installing on external storage can affect loading or stutter when the interface, enclosure, cable, or file system becomes the narrow point.
Consider a racing game that loads a dense city full of reflective glass, traffic, and wet asphalt. On a healthy internal SSD, the starting grid may appear quickly; on an aging portable hard drive, you may hear the disk chatter while textures arrive late. The exact result depends on the game, platform, storage device, and connection, so treat universal performance claims with care.
On Steam Deck, Verified, Playable, Unsupported, and Unknown compatibility labels concern the tested game experience, not the speed of every storage device. Valve can update those ratings after game patches or review changes, so check the current store page on your device rather than relying on an old screenshot. Performance reports should also name the platform, SteamOS version, game build, and storage type.
A practical split works well: keep competitive games and sprawling open worlds on the fastest internal storage, then place turn-based titles, older releases, and rarely played games on roomy secondary media. That arrangement holds both your library and your patience. Leave some free space too, since downloads and updates may need temporary working room beyond the final installed size.
Fix a Missing Library Before You Delete or Reinstall Anything
Steam Machine Game Install Locations often seem missing because Steam lost the library path, the drive failed to mount, or an appmanifest no longer matches the files. Reconnect the library first, confirm the drive is readable, and verify the game through Steam before deleting data or starting a full download [1].
Start with the simple scene: you boot a SteamOS machine, open your library, and 40 installed games suddenly show gray Install buttons. If all 40 lived on one external SSD, simultaneous corruption is unlikely. Check whether the drive appears in the desktop file manager and whether its SteamLibrary folder still contains steamapps/common.
Next, open Settings > Storage and add or reselect that library. Client labels can change, but the goal remains the same: point Steam at the folder that directly contains steamapps. Choosing steamapps/common itself goes one floor too deep, like giving a delivery driver your bedroom number but not the building address.
- One game is missing: inspect its folder and matching appmanifest file, then attempt discovery through installation into the same library.
- An entire drive is missing: check its cable, power, mount point, permissions, and library registration.
- A game crashes after a move: use Properties > Installed Files > Verify integrity of game files.
- An update loops: confirm free space and inspect the downloading folder only after Steam has fully stopped.
According to Valve’s Steam support guidance, file verification compares the local installation with Steam’s expected files and reacquires missing or damaged items [1]. Verification may reset modified game files, so copy manual mods or edited configuration files first. It verifies the installation; it does not promise to repair a damaged save stored elsewhere.
Avoid downloading third-party relocation tools for a problem Steam already handles. Such tools can help specialized mod setups, but they add permissions, links, and another set of records that can break. When troubleshooting, simplify the path: one mounted drive, one registered library, one recognized manifest, and one verified game.
Frequently Asked Questions
Where does Steam install games by default on a SteamOS machine?
SteamOS commonly keeps the internal library under /home/deck/.steam/steam/steamapps/common, though system images and usernames can produce a path under .local/share/Steam or a linked equivalent. Turn on hidden files in the desktop file manager because folders beginning with a dot do not appear by default.
Why does Steam say Install when the game folder already exists?
Steam may see the files but lack the matching appmanifest record, or the library containing them may no longer be registered. Add the correct folder under Settings > Storage, then begin installation into that same library so Steam can discover and verify usable files.
Can I move a Steam game to another drive without reinstalling it?
Yes. Add the destination as a Steam library, select the game in Steam’s storage manager or Installed Files properties, and use the move command [1]. This keeps Steam’s records aligned with the transferred files and avoids downloading the whole game again.
Are Steam saves stored inside steamapps/common?
Some games keep saves beside their installation, but many use Documents, AppData, macOS Library folders, Linux user folders, or Proton compatdata. Steam Cloud may copy selected saves between devices, yet its coverage depends on each game developer’s setup [2].
Will an external SSD make Steam games run slower?
A good external SSD on a fast connection can deliver short loading times, but the port, cable, enclosure, and file system can limit it. Frame rate may remain similar after loading, while games that stream textures continuously can expose a slow or unstable connection through pauses and late-arriving detail.
What should I do if Verify integrity replaces my modded files?
Verification restores files to the version Steam expects, so it can replace manually edited or modded game files. Copy those changes before verification, run the check, and then reinstall compatible mods through their manager or documented method.
Conclusion
The one idea to remember is simple: find the library before touching the game. Every Steam library uses the same broad map, with steamapps as its hub, common holding the large installation folders, and appmanifest files acting as labels. Saves may live beyond that map, so protect them separately before a reinstall, drive replacement, or manual repair.
When a title disappears, open Steam’s storage settings, reconnect the right library, and let the client browse, move, or verify the installation. Do not erase a full folder because one button says Install. Follow the bytes first; they often sit exactly where you left them, quiet as a dark arcade before the power switch clicks.
