Jump to content
Setting up an AI agent? ReverseEngineering.wiki skill (works from the command line, no configuration): https://reverseengineering.wiki/skill/rewiki/SKILL.md · setup for every client, including MCP: https://reverseengineering.wiki/llms.txt · REWiki:Connect

Format:Steam client data files

From ReverseEngineering.wiki
Format
On this wiki Facts · Code · Notes · Topics

Overview of the Steam client's on-disk metadata files (appmanifest_*.acf, libraryfolders.vdf, shortcuts.vdf, appinfo/packageinfo caches) and which KeyValues flavor each uses.

Overview

All are Format:KeyValues1 (VDF, ACF): text for appmanifest_<appid>.acf (steamapps folder) and libraryfolders.vdf, binary for shortcuts.vdf (per-user config folder) and the appcache files described in Format:Steam appinfo and packageinfo. Depot layouts are in Format:Steam depot manifest. Games ship the runtime described in Library:Steamworks API.

Per-file notes

Checked against Lutris (GPL-3.0, commit 3307967, lutris/util/steam/appmanifest.py and config.py) and Steam ROM Manager (GPL-3.0, commit f68289a, src/lib/vdf-shortcuts-file.ts); source read, not run.

  • appmanifest_<appid>.acf (in a steamapps folder): root key "AppState" (Lutris reads it with appmanifest_data.get("AppState")) with name, installdir (the game lives in steamapps/common/<installdir>), StateFlags and a nested UserConfig block (name can also come from there), and the app id (Lutris writes it as appID; case varies, compare keys case-insensitively). StateFlags is a bit mask: Lutris decodes bit n into a state name table and treats "Fully Installed" as installed; a freshly written stub uses 1026. Unverified: buildid, LastUpdated, SizeOnDisk and InstalledDepots (not read in any source here).
  • libraryfolders.vdf: found at <Steam>/config/libraryfolders.vdf (Lutris), root "libraryfolders" with numbered child blocks, each with a path; newer files also carry mounted (Lutris only uses a library when mounted is "1") and a contentstatsid key at the top level that Lutris pops. Older Steam used BaseInstallFolder_N keys in config.vdf instead. Unverified: the label field and the per-library apps table (appid to size).
  • shortcuts.vdf: in <Steam>/userdata/<user id>/config/shortcuts.vdf (Steam ROM Manager builds exactly that path); binary KeyValues with root "shortcuts" and one numbered child per non-Steam game. Fields seen in the Steam ROM Manager code: appid, AppName/appname, Exe/exe, StartDir, LaunchOptions, icon, tags, plus IsHidden, AllowOverlay and LastPlayTime. Key casing is inconsistent (the code says Steam writes "AppName"/"Exe" when a game is added through Steam itself), so match keys case-insensitively. In the ValvePython/vdf writer a binary file begins with 00 + key + 00 (root key "shortcuts") and every nested object is closed by 08, so a normal file ends with the nested end plus the root end, 08 08.

The binary node types are documented and read from source on Format:KeyValues1 (VDF, ACF); a Python reader (ValvePython/vdf, MIT, commit d762926) offers binary_load for shortcuts-style files.

Code & repositories

  • https://github.com/ValvePython/vdf @ d76292623e326fb165fe3bdb684832cdf30959d4 · license: MIT
    MIT Python text and binary VDF parser
    Tested on: source read, not run: source read · checked 2026-10-18; last activity 2024-06-30