Back up two different things before a Steam game disappears: the installed game data and the game’s save and settings files. Copy both to a destination other than the source drive, then inspect the copy and, when practical, test a restore. A delisting normally removes the ability to buy a game rather than removing it from existing owners’ libraries, but a copied folder is not automatically a standalone installer and cannot replace Steam ownership checks or publisher-hosted services.
Valve says retired games remain in players’ Steam libraries, while its documentation treats installer creation, cloud synchronization and ownership verification as separate systems. That distinction determines what your archive can preserve and what it cannot.
What exactly should you back up?
Treat preservation as two jobs. The first is a copy of the installed game data: executable files, content, and any downloadable files already present on your drive. The second is a separate copy of the game’s user data: saves, configuration files, profiles and other progress-related files. Keeping only one of these can leave you with an unusable archive.
Installed game data
An installed copy can save you from downloading many gigabytes again if the title is later difficult to obtain. You can copy the game’s directory to another drive, or use Steam’s game-backup feature if it is offered in your client. The current client’s exact menu label and location were not established here, so do not rely on an old screenshot or a confidently stated click path. Whatever method you use, confirm that the destination contains the expected files.
Save and settings data
Save files are often outside the Steam library folder. Valve’s Steam Cloud documentation lists possible locations including the install directory, Windows Documents, AppData Local, LocalLow, Roaming and Saved Games folders, macOS home, Application Support and Documents folders, and Linux home and XDG data locations. Those are possible roots, not a universal checklist: an individual game may use one, several, or a completely different arrangement.
What a backup cannot promise
A consumer copy of a Steam directory is an archive of files, not proof of a standalone installer. Valve’s retail-disc documentation describes a separate, publisher-created setup application, while its DRM documentation explains that a game can require ownership verification and Steam at launch. A copied drive therefore does not guarantee DRM-free or offline play, restore online servers, or transfer an entitlement to another account.
Valve’s retirement guidance says existing owners normally retain access, but publishers are asked to explain any hosted services that will stop working. Your archive protects local data; it does not preserve a discontinued matchmaking service, login endpoint or other server-side feature.
Can you still download a Steam game after it is delisted?
Usually, yes, if you already own it. Valve states that “Retired games will remain in players’ Steam libraries,” and existing owners can generally download, install and launch them. Delisting is therefore not, by itself, a countdown to losing an owned copy.
That policy is not a guarantee that every retirement has identical consequences. A publisher may shut down hosted functions, remove a required service, change DLC availability or announce a game-specific deadline. Before archiving, open the game’s entry in your owned library and read the publisher’s announcement, support page or in-game notice for details that the general Steam policy does not cover.
Do not wait for a delisting notice to make your first copy. The safest time is while the game launches normally, its save location is known and the original files are intact.
How do you back up an installed game and its saves?
Use this sequence while the game is still installed and playable. It deliberately separates entitlement checks, installed files, saves, cloud synchronization and verification.
- Confirm the game’s status and ownership. In Steam, check that the title appears in the library under the account that owns it. Note any publisher announcement about a sale retirement, server closure, DLC change or access deadline. Valve’s retirement procedure specifically asks publishers to describe services players may lose; that information is more useful than assuming every delisting is the same. Valve’s product-retirement guidance is the reference for the general policy.
- Close the game and let writing finish. Exit to the desktop rather than copying while a save is being written. If Steam Cloud is enabled, wait for the client to finish its synchronization indicator before making the manual save copy. Keep the game installed until you have inspected the destination.
- Copy the installed game data. Use a separate internal drive, external SSD, external hard drive or another destination that is not the source drive. You may use Steam’s backup function if it appears in your client, or copy the game’s installed directory yourself. Because the contemporary menu path was not verified, describe your archive by what it contains rather than by an old menu name. Preserve the game’s directory structure and do not delete the source until the copy has been checked.
- Locate the specific game’s user data. Read the publisher’s support instructions first, then inspect the possible operating-system locations listed in the next section. Copy saves and settings into a separate folder from the installed binaries. If the title uses more than one location, preserve each one and write down the original path.
- Allow Steam Cloud to synchronize, but keep the manual copy. Steam Cloud only replicates files configured by that game’s Auto-Cloud settings or written through the Cloud API. Cloud can be disabled globally or for an individual title. A cloud copy is synchronization, not a complete image of every file on your computer.
- Record what you saved. Make a plain-text note containing the game name, operating system, date, source paths and whether Steam Cloud was enabled. This avoids guessing years later which folder belongs to which title and which files were intentionally omitted.
- Inspect and, if possible, restore. Open the destination and verify that the installed directory, expected save files and your note are present. For a stronger check, use the same entitled Steam account to install or launch the game and confirm that it recognizes the intended progress. A restore check demonstrates that the files are readable; it does not remove account, DRM or hosted-service requirements.
Where are Steam save files stored?
There is no single Steam-wide save folder. Valve lists possible Auto-Cloud roots by operating system, but each game chooses which files and paths it actually uses. Use the table as a search map, then confirm the result with the game’s own documentation.
| Operating system | Possible save or Auto-Cloud roots | How to use the list |
|---|---|---|
| Windows | Game install directory; Documents; AppDataLocal; AppDataLocalLow; AppDataRoaming; Saved Games | Search for the game or publisher name, compare timestamps with a newly created save, and preserve every location the title uses. |
| macOS | Game install directory; the user’s home directory; Application Support; Documents | Check the publisher’s macOS instructions and retain the original folder hierarchy when copying. |
| Linux | Game install directory; the user’s home directory; XDG data locations | Look for the title’s documented data directory and note the exact path for restoration. |
These locations are possibilities, not a claim that every game uses all of them. Steam Cloud’s account storage page is sign-in gated, and seeing a cloud interface does not prove that a particular save is present. The only dependable way to identify a title’s save set is to match the publisher’s instructions and the files that change when you create or update a save.
Does Steam’s game-backup function include save files?
Do not assume it does. A publisher’s Transport Fever 2 documentation explicitly distinguishes its Steam static-data backup from the game’s userdata folder, which contains saves. That example is a warning to verify each title, not a universal claim about every game’s implementation. The publisher’s troubleshooting documentation describes that separation.
When you use a Steam backup feature, open the resulting destination and look for the actual save files separately. If they are absent, copy the user-data directories yourself. Even when a backup utility appears to include a user folder, retain a second manual copy because the game may store settings or profiles elsewhere.
How does Steam Cloud affect a manual backup?
Steam Cloud is useful synchronization, but it is not a substitute for an independent archive. Valve says, “The Steam Client does the work of ensuring that the files are kept synchronized across all computers the user may be accessing.” That behavior applies only to files the game has configured for Auto-Cloud or written through the Cloud API. Valve’s Steam Cloud documentation explains the scope and configuration.
Before you copy
Exit the game and wait for synchronization to finish. If Cloud is disabled globally or for the title, there may be no remote copy to rely on. Keep the manual files even when the client reports that synchronization is complete.
When a conflict appears
A conflict prompt presents different local and cloud versions. Choosing one can overwrite the other, so preserve both versions before resolving the prompt. Copy the local save directory and, if available, download or otherwise retain the cloud version first; only then select the version you intend to use.
Why an account page is not proof
The presence of a Steam Cloud interface does not establish that every save, configuration file or profile is synchronized. Games can configure only selected paths, and unsupported files remain local. Treat Cloud as an additional copy whose contents you verify, not as evidence that your complete save set is safe.
Can copied Steam files work without Steam or after servers shut down?
Sometimes an installed game will run with fewer online dependencies; sometimes it will not. Valve’s DRM documentation allows developers to require ownership verification and to launch Steam, while hosted features can depend on publisher servers. A copied folder cannot remove those requirements.
Keep three separate questions in mind:
- Can the files be read? Your destination should contain the expected executable, content and save files.
- Does the account still own the game? Steam may require the entitled account to authenticate before installation or launch.
- Are required services available? Multiplayer, leaderboards, authentication or other hosted functions may stop even if local files remain intact.
Valve’s retail-disc documentation describes a distinct publisher-created installer workflow, not a consumer procedure for turning a Steam folder into an independent setup program. Do not label your archive a “standalone installer” unless the publisher supplied a genuine installer and its license permits that use.
Which destination should hold the backup?
The destination must have enough capacity for the files you actually copied, connect to your computer, remain portable or accessible when needed, and ideally be accompanied by another independent copy. Capacity alone is not redundancy: a second copy on the same failing drive does not protect the archive.
| Example destination | Documented capacity | Where it fits | Check before copying |
|---|---|---|---|
| Samsung Portable SSD T7, model MU-PC1T0T/AM | 1 TB | Portable SSD for a relatively small or curated game archive | Confirm that your computer and cable support the drive’s connection, that free space exceeds the files being copied, and that another independent copy exists. Samsung’s specification page identifies this model and capacity. |
| Western Digital My Passport, model WDBPKJ0040BBK-WESN | 4 TB | Higher-capacity portable archive when several installed titles must be retained | Check the drive’s connector, available space and readability on the computer where you will restore it. Treat the model as an example, not a tested ranking. |
Neither device makes Steam data DRM-free or replaces the game entitlement. If you use a separate cloud-backup service, verify exactly which folders it selects and whether restored files are readable. Backblaze describes Personal Backup as covering user-generated data on computers and connected external drives; its cited description does not establish coverage for installed Steam binaries, so do not assume a complete game archive without checking the selected folders and a restore.
Backblaze’s Personal Backup description is the source for that coverage statement.
How do you verify that the archive is usable?
Verification is a short inspection, not a promise that the game will run forever. Use this checklist after every copy:
- Open the destination and confirm the game’s installed directory is present.
- Confirm the separate save folder contains files with plausible names and current timestamps.
- Compare the copied folder size with the source and investigate an unexpectedly small result.
- Read the text note so the game, operating system, date and source paths are unambiguous.
- Disconnect and reconnect the destination, then open several files or directories to catch an unreadable copy.
- Where feasible, restore to a test location using the same entitled account and confirm that the intended progress appears.
A successful file check does not prove that Steam will accept the files on another account or that a server-dependent feature will return. It proves only that your archive contains readable local data in the places you recorded.
What can go wrong, and how do you recover?
The game launches but shows no progress
Usually the files were copied to the wrong path, only one of several save locations was preserved, or Cloud restored an older version. Quit the game, keep the current files as a separate copy, recheck the publisher’s documented path and compare timestamps before replacing anything.
A Cloud conflict offers two versions
Do not click through immediately. Preserve the local save directory and the other available version first, then choose the version whose progress you can identify. The unchosen copy may otherwise be overwritten.
The backup contains the game but no saves
This is consistent with a static-data backup that omits userdata. Search the title’s documented save roots and copy those files separately; the Transport Fever 2 documentation demonstrates why the installed-data archive cannot be assumed to contain user progress.
The copied files demand a login or Steam launch
That behavior is compatible with ownership verification or DRM. Sign in with the account that owns the title and retain the account information needed for restoration. A physical drive cannot bypass those checks.
Online features no longer work
Local files do not recreate publisher servers. Check the retirement announcement for hosted-service changes and distinguish an offline-capable local game from features that depended on a discontinued endpoint.
The destination is too small
First preserve the save and configuration files because they are usually much smaller than installed content. Then copy the installed data to a larger destination or split the archive across independent drives, keeping a note that identifies which part contains the binaries and which contains user data.
What should you do immediately before a delisting?
- Launch the game and create or update a known save so you can identify the correct files.
- Read the publisher’s retirement, DLC and server notices.
- Close the game and wait for Steam Cloud synchronization, if enabled.
- Copy installed game data to a separate destination.
- Locate and copy the game’s saves and settings independently.
- Write down the paths, date, operating system and account context.
- Inspect the destination and perform a restore check when practical.
- Keep an additional independent copy rather than trusting one drive or Cloud alone.
This process preserves what you control: local game files and local progress. Steam’s library entitlement and any publisher-hosted service remain separate conditions for future access.
Frequently Asked Questions
How should I label a long-term Steam game archive?
Use a folder name that includes the game title, operating system and backup date, then add a plain-text manifest listing each source path and whether the copy contains installed data, saves or both. Clear labels prevent a later restore from mixing files from different games or dates.
Can a network location serve as the separate backup destination?
It can be useful if the location is accessible, has enough capacity and lets you read the copied files later, but Steam does not turn a network copy into an installer or an entitlement. Treat it like any other destination: preserve an independent second copy and verify a restore.
What if the game is already uninstalled when I start planning?
Search the save roots documented by the publisher and the operating system, and check any earlier drive or Cloud copy you control. Reinstalling may still require the entitled Steam account, and a save found without the game’s installed data cannot guarantee that the title will launch.
Should I keep several dated versions of a save?
Keeping dated versions protects you from discovering that the newest file was corrupted or overwritten during a Cloud conflict. Retain at least one older, known-good copy until you have launched the restored game and confirmed the intended progress.