Local Steam appmanifest ACF helper

AppManifest Steam Generator

Create a clean appmanifest_*.acf starter file in your browser, then copy or download it before checking the real Steam library path.

Numbers only. The AppID is also used in appmanifest_730.acf.

Use the visible Steam library name when you know it.

This should match the folder under steamapps/common when possible.

Use bytes when known. Leave 0 for a starter file you will verify later.

4 is a common installed-state starter value; verify after Steam scans the library.

Edit the fields or use the sample values, then generate the ACF preview.

appmanifest preview 
Your appmanifest preview will appear here.
Find the AppID first Check manifest availability Download manifest packages

How to Use the AppManifest Steam Generator

The generator is intentionally narrow: it creates a readable ACF starter file, not a fake depot manifest or a full game download.

1

Enter a real AppID

Start with the Steam AppID from the store URL, SteamDB, or your own library. The downloaded filename becomes appmanifest_APPID.acf.

2

Match the install folder

Use the folder name from steamapps/common when you are repairing a local library. A mismatched installdir can make Steam ignore the files.

3

Copy or download the ACF

Review the generated text, save it as appmanifest_APPID.acf, and place it in the steamapps folder for the same library root.

4

Let Steam verify

Restart Steam or trigger library verification. Steam may rewrite timestamps, depot blocks, build IDs, and size fields after it scans real files.

Example AppManifest Input and Output

The preview stays crawlable and editable, so you can inspect every field before saving the file.

Sample input

  • AppID: 730
  • Name: Counter-Strike 2
  • Install folder: Counter-Strike Global Offensive
  • Size on disk: 0 for a starter file, or a real byte value when you have one
  • StateFlags: 4 for an installed-state starter value

Generated starter ACF

"AppState"
{
    "appid"        "730"
    "Universe"        "1"
    "name"        "Counter-Strike 2"
    "StateFlags"        "4"
    "installdir"        "Counter-Strike Global Offensive"
    "LastUpdated"        "1760000000"
    "SizeOnDisk"        "0"
    "InstalledDepots"
    {
    }
}

What the AppManifest Fields Mean

These fields help Steam identify an installed app, but they do not replace depot metadata, ownership, or file verification.

Field Meaning Practical note
appid The numeric Steam application identifier. Use the same number in the filename, for example appmanifest_730.acf.
name The display name Steam can show for the app. This is helpful for reading the file, but AppID and folder placement matter more.
installdir The local folder under steamapps/common. If this folder is wrong, Steam may not connect the manifest to the installed files.
StateFlags A numeric state value used by the Steam client. The tool uses 4 as a practical starter, then Steam can update the file after scanning.
InstalledDepots A block Steam can populate with depot-specific records. This generator leaves it empty because depot IDs and manifests must come from real app data.
SizeOnDisk The byte count Steam records for the installed app. 0 is safer than guessing; use a measured value only when you can verify it.

Limits, Safety Notes, and Edge Cases

A generated ACF can help with local recovery notes, but it is not proof that Steam owns, downloads, or validates the app.

No ownership bypass

The appmanifest steam generator does not unlock games, bypass Steam access rules, or replace account ownership. It only creates local text.

Not a depot manifest

Steamworks depot manifests list files inside a depot build. A local appmanifest_*.acf file is a Steam client state file and has a different job.

Library path matters

Place the ACF in the steamapps folder that owns the matching common folder, not inside the game folder itself.

Steam may rewrite it

After a scan or verification, Steam can update fields such as buildid, LastUpdated, SizeOnDisk, and InstalledDepots.

Sources and Version Freshness Check

This is a browser utility page, not an app download page, so there is no software version or APK package to update.

Checked July 10, 2026. The page does not claim a latest app version, file size, official download, or safety scan. Official and reference sources were used only to define depots, manifests, and local appmanifest placement.

AppManifest Steam Generator FAQ

Short answers for users creating, repairing, or inspecting appmanifest_*.acf files.

What is an appmanifest steam generator?

It is a browser tool that creates a starter appmanifest_*.acf text file from an AppID, app name, install folder, size, and state flag. It helps you prepare local Steam library metadata for review.

Is appmanifest_*.acf the same as a Steam depot manifest?

No. A local appmanifest ACF file helps the Steam client track installed app state. A Steamworks depot manifest is a file list for a depot build. They use similar words but solve different problems.

Where should I put appmanifest_730.acf?

Put it in the steamapps folder for the same Steam library that contains the matching steamapps/common game folder. Do not put it inside the game folder.

Can this tool recover a missing Steam game instantly?

Not by itself. It can create a starter file, but Steam still has to scan the library, verify files, and confirm access. Use it as a repair aid, not a guarantee.

Why does the generator leave InstalledDepots empty?

Depot records depend on real app, branch, and build data. Guessing them can make the file less reliable, so the tool leaves the block empty and lets Steam update what it can verify.

Should I use this or the Steam Manifest Downloader?

Use this page when you need a local appmanifest_*.acf file. Use the Steam Manifest Downloader when you want a downloadable manifest package by AppID.