Steam AppManifest File: What It Is, Where It Lives, and How to Fix It
A practical guide to appmanifest_<AppID>.acf files, Steam library detection, safe backups, common failure symptoms, and the point where creating a replacement file helps—or makes the problem worse.
On this page
Steam can have all of a game's files on disk and still offer an Install button. That confusing state often points to a missing or unusable appmanifest file rather than a deleted game. The large files under steamapps/common are the payload; the small appmanifest_<AppID>.acf file is part of the local record Steam uses to identify and manage that payload.
This distinction matters because copying a random ACF file is not a harmless shortcut. A manifest that names the wrong AppID, install directory, build, state flags, or depots can make Steam verify the wrong location, queue a large download, or overwrite useful evidence about the existing installation. A safe repair starts with the disk, not with a generated template.
The guide below explains the file in plain language, maps its normal location, identifies the fields worth checking, and gives a reversible recovery order. It also draws a firm boundary between informational repair and the site's AppManifest Generator so the two pages answer different search intents.
What Is a Steam AppManifest File?
An appmanifest is a Valve KeyValues-style text document with an .acf extension. Steam creates one for each locally managed app in a library. The filename follows appmanifest_<AppID>.acf, so Counter-Strike 2 uses AppID 730 and the corresponding filename is appmanifest_730.acf.
The file is not the game, a depot manifest download, a license, or a backup of save data. It is local state metadata. It helps Steam connect an AppID to an install directory and track whether the app is installed, updating, staging, shared, or otherwise managed in that library.
One game may use many depots, but it normally has one appmanifest record per Steam library installation. Depot manifest files describe versions of depot content; the appmanifest ties the app-level installation together. Mixing those two meanings is a common source of unsafe advice.
appmanifest_730.acf
appmanifest_570.acf
appmanifest_<AppID>.acf| File or folder | Purpose | Replace casually? |
|---|---|---|
| appmanifest_<AppID>.acf | Local app state and library recognition | No; back up and match the real AppID first |
| steamapps/common/<Game> | Installed game files | No |
| steamapps/content | Raw depot output from download_depot workflows | No if you need the downloaded depot |
| depotcache | Staged or cached download data | Not while downloading, preloading, or unpacking |
| userdata | Account-specific local data and some saves/configuration | Not part of an appmanifest repair |
Where Are Steam AppManifest Files Stored?
In the default Windows installation, appmanifest files are usually under C:\Program Files (x86)\Steam\steamapps. A secondary library commonly uses a path such as D:\SteamLibrary\steamapps. The important rule is structural: the ACF file sits directly inside steamapps, while the installed game directory usually sits one level lower under steamapps/common.
Do not assume every game is in the first Steam folder you find. Steam supports multiple storage libraries, external drives, and custom folders. Open Steam's Storage settings or inspect libraryfolders.vdf to identify the library that actually contains the game's common folder, then look for the matching appmanifest in that same steamapps directory.
On Linux and Steam Deck, paths vary with native, Flatpak, and compatibility setups. The same relationship still helps: find the active Steam library, then check its steamapps directory for the ACF record and its common directory for the installed payload.
C:\Program Files (x86)\Steam\steamapps\appmanifest_730.acf
D:\SteamLibrary\steamapps\appmanifest_730.acf
D:\SteamLibrary\steamapps\common\Counter-Strike Global Offensive
Match the library, not just the filename
An ACF file in the wrong Steam library does not reliably reconnect a game stored on another drive. Confirm the library root and common folder together.
Important AppManifest ACF Fields Explained
Appmanifest content is readable text, but not every field should be guessed. The safest checks are identity and location: appid must match the store entry, name should match the intended app, and installdir should match the existing directory under steamapps/common.
StateFlags describes local state as a numeric bit field. A commonly seen installed value is 4, but copying it blindly cannot rebuild missing depot and build information. buildid and InstalledDepots may change after updates. LastUpdated and SizeOnDisk describe local state, not an authoritative promise about the current public release.
Steam may rewrite the file after launch, verification, or an update. That is normal. Treat a generated file as a bootstrap aid, not as a permanent source of truth. Once Steam recognizes the app, let the client inspect and update the record.
"appid" "730"
"name" "Counter-Strike 2"
"installdir" "Counter-Strike Global Offensive"
"StateFlags" "4"| Field | What it tells Steam | Repair note |
|---|---|---|
| appid | Which Steam app the record belongs to | Must be exact; do not use a DLC, demo, or soundtrack AppID |
| installdir | Folder name below steamapps/common | Must match the real directory name |
| StateFlags | Current local app state | Useful symptom, not a complete repair by itself |
| buildid | Build recorded for the local installation | May be stale and should be refreshed by Steam |
| InstalledDepots | Depot records attached to the installation | Do not invent depot manifest IDs |
| SizeOnDisk | Recorded local size in bytes | A zero placeholder can be temporary; verification should recalculate state |
What Missing, Stale, or Mismatched AppManifest Files Look Like
The classic symptom is an installed game showing an Install button. Steam may also rediscover files only after you select the same library, begin installation, or run verification. A copied library can look empty when the common folder arrived but the matching appmanifest files did not.
A stale file can cause a different pattern: Steam sees the game but queues an unexpectedly large update, remains in validating or updating state, or fails to reconcile files after a drive move. Those symptoms do not prove the ACF is the only problem; interrupted downloads, low disk space, permissions, library registration, and damaged game files can produce similar behavior.
A mismatched record is more dangerous than a missing one because it looks plausible. The filename can use one AppID while the content or install directory points elsewhere. Always compare filename, appid, installdir, actual folder, and the Steam store URL before allowing a repair to continue.
| Symptom | Likely appmanifest angle | First safe check |
|---|---|---|
| Game files exist but Steam says Install | Missing ACF or wrong library | Confirm common folder and matching appmanifest in the same library |
| Game appeared after moving drives, then vanished | Library root or ACF was not moved/registered correctly | Re-add the library and inspect libraryfolders.vdf |
| Very large download starts | Steam does not trust the recorded state | Pause, preserve files, and choose the existing folder before verification |
| Wrong title or edition appears | AppID mismatch | Check the store URL, DLC/demo IDs, and filename |
| Update loops or validation fails | Stale metadata may be one factor | Check disk space, permissions, cache state, and client logs as well |
Safe Recovery Workflow for a Missing Steam AppManifest
Use a reversible order. The goal is to preserve installed files and evidence before Steam starts changing the library. If a transfer or update is active, pause it first. A rushed launch can rewrite state or begin allocating a new download.
The preferred repair is to let Steam recognize and verify existing files. A generated ACF is a fallback for cases where the client cannot begin that process despite a confirmed AppID, correct directory, registered library, and complete local files. Even then, expect Steam to rewrite the generated fields.
- Exit Steam completely
Pause active downloads, use Steam > Exit, and confirm the client is no longer writing to the library.
- Back up the evidence
Copy the existing appmanifest file if present and record the full common-folder path, folder size, AppID, and drive.
- Confirm the exact AppID
Use the official store URL or a trusted AppID reference. Separate the base game from DLC, demos, tools, soundtracks, and test apps.
- Confirm the library is registered
Open Steam Storage settings and make sure the drive/library root is available before changing files.
- Start discovery in the same folder
Choose Install for the same app and the same library. Steam may detect existing data and move into verification instead of downloading everything.
- Generate only if discovery cannot start
Create a minimal appmanifest with the exact AppID and installdir, place it in the matching steamapps directory while Steam is closed, then restart and verify.
- Stop if Steam targets the wrong path
Do not let a guessed manifest overwrite or replace a known-good folder. Restore the backup and recheck the AppID, library, and install directory.
Verification is the finish line
A replacement ACF is successful only when Steam recognizes the correct app and validates the existing files. The generated text itself is not proof that the installation is healthy.
When Should You Use an AppManifest Generator?
Use an AppManifest Generator when you understand the missing record and have already verified the identity and location of the files. It is useful for creating a readable starting file with the correct filename, AppID, name, install directory, size placeholder, and state flag.
Do not use a generator to invent current depot manifests, build IDs, ownership, licenses, or a claim that a game is fully installed. Those facts belong to Steam's account, content, and verification systems. A generated file cannot grant access and should not be presented as an official or latest manifest.
The site's AppManifest Generator runs in the browser and downloads a plain .acf file. Review it before saving. If your actual goal is to find a game number, use the AppID Finder; if your goal is a depot manifest package, use the separate Manifest Downloader workflow.
| Your goal | Best page or action | Why |
|---|---|---|
| Understand why Steam lost an installed game | This guide | Explains diagnosis and safe recovery order |
| Create appmanifest_<AppID>.acf | AppManifest Generator | Produces a transparent local text file |
| Find the correct AppID | AppID Finder | Avoids base-game, DLC, demo, and edition mix-ups |
| Download depot manifest/Lua package | Steam Manifest Downloader | Different file type and intent |
| Fix an active download or preload | Steam client troubleshooting | Do not replace metadata while content is being written |
AppManifest Repair Mistakes to Avoid
Do not download an ACF file from a random mirror simply because the filename matches. The content may point to another install directory, old build, language package, beta branch, or unrelated app. Plain text is inspectable, so compare it before use.
Do not delete the common folder to make Steam start over until you have decided that redownloading is acceptable. If the payload is intact, discovery and verification can save substantial bandwidth. Likewise, do not delete appmanifest files in bulk; each one represents a different locally managed app.
Do not edit while Steam is open. The client can overwrite your changes or capture a half-finished state. Do not claim a generated file is official, current, safe, or complete merely because Steam parses it. The client and your account still determine entitlement, content availability, current depot state, and final validation.
Finally, keep appmanifest repair separate from save recovery. Save files may live under userdata, Documents, AppData, the game directory, or cloud synchronization. Recreating an ACF file does not restore deleted saves.
Make one controlled change at a time
Keep backups, restart Steam after each meaningful change, and verify that the app, library, and folder still match before continuing.
Steam AppManifest FAQ
Official and technical references
- Steamworks Documentation — Applications and Depots — Valve's official explanation of applications, depots, and content organization.
- Steamworks Documentation — Building and Publishing — Official context for SteamPipe builds, depots, manifests, and client troubleshooting.
- Valve Developer Community — Add non-Steam game files to Steam — Technical community documentation illustrating how local Steam library state and appmanifest files interact.
- PCGamingWiki — Steam — Community technical reference for Steam file locations, library behavior, and troubleshooting context.
Last updated: July 30, 2026