10 min readNovember 4, 2026

Steam libraryfolders.vdf: Find Steam Library Paths

A read-only guide to Steam library locations, AppID entries, and games that disappear after a drive is added or moved.

Quick answer: Steam libraryfolders.vdf is a client-managed KeyValues file that describes registered Steam library folders and can list app IDs associated with them. Use Steam's Storage settings first, then compare the library path with the game's steamapps/common folder. Read the file only as supporting evidence; do not copy entries between libraries or edit its values to force recognition.

A game can remain on disk while Steam shows Install or an empty library, especially after adding, reconnecting, or cloning a drive. First identify which library contains the files and whether Steam still registers it.

Steam libraryfolders.vdf offers supporting clues about library paths and app entries. It is not the game, a depot download, or a repair form. Use Steam Storage first and treat the file as read-only evidence.

Paths vary by installation and client version. Keep the files unchanged until Steam recognizes and verifies the correct library.


What Does Steam libraryfolders.vdf Record?

Steam uses Valve KeyValues-style files for nested named values. libraryfolders.vdf has numbered library entries; an entry can include a path and an apps section containing app identifiers. It is structured client configuration, not a simple folder list.

The path and matching AppID can help locate a game across drives. They do not prove that files are complete, accessible to an account, or safe to repair by editing the entry.

Steam manages this configuration and may update it as libraries change. Treat copied or older files as potentially stale. Use Storage to add, remove, or move a library; read the file only to understand the current state.

Use it as evidence, not as a repair command

A path or AppID entry helps identify a library. It does not replace Steam's registration and verification workflow.


Where libraryfolders.vdf Fits in a Steam Library

A library root commonly contains steamapps, with installed games below steamapps/common. appmanifest_<AppID>.acf records one app's local state; libraryfolders.vdf describes library locations and related app entries. They are related, not interchangeable.

A VDF path points to a library root, not always the final game folder. Follow it to steamapps/common and compare the game directory with the matching AppID record. Drive letters vary.

ItemRoleUseful check
libraryfolders.vdfRegistered library paths and related app entriesDoes the path correspond to a library shown by Steam?
steamapps/common/<Game>Installed game filesIs the expected folder present on that drive?
appmanifest_<AppID>.acfLocal state record for one appDoes the filename match the intended app?
depotcacheStaged or cached download dataIs a download or update still in progress?
steamapps/contentRaw depot download output for some workflowsWas this output meant to be a normal installed game?

A library path is not the game path

Start at the library root, then check the app-specific location and record in the same library.


How to Read Paths and AppID Entries

A numbered entry can contain a library path and an apps block with AppID keys. Other values are client-maintained; do not copy them from another entry.

Quoted Windows paths may show doubled backslashes as escape sequences. Use the path shown in Steam Storage to inspect folders; do not rewrite a path based on how it looks in a text editor.

Confirm the game's AppID, then compare its entry, common folder, and appmanifest filename in the same library. A missing match may mean the wrong library or stale state, not that the VDF should be edited.

Match identity and location together

The AppID, library root, game folder, and appmanifest should tell a consistent story before any repair is attempted.


Use Steam Storage Settings Before Inspecting the File

Steam Storage shows the libraries the current client recognizes and provides controls to add or move them. Start there, especially if a removable or cloned drive received a new letter.

If a drive is missing, check that the operating system can open it. If Steam lists it as empty, compare the selected root with its steamapps/common folder. Pause downloads and do not alter files during updates or verification.

Use Steam to select an existing folder and let the client inspect it. If an unexpected full download appears, pause and confirm the library path rather than deleting metadata.

  1. Open Storage

    Note each library location shown in Steam Settings.

  2. Confirm the drive

    Check that the operating system can open the expected library folder.

  3. Match the game

    Compare its AppID, appmanifest filename, and common folder.

  4. Use Steam

    Add, locate, or verify the installation through the client.

  5. Stop on a mismatch

    Pause an unexpected full download and re-check the path.

Let Steam change its own registration

The Storage interface is designed for library management and avoids guessing at client-maintained fields.


When a Moved or Cloned Drive Looks Empty

After a clone, the drive letter or registered root may differ from the old setup. The game folder can also be nested one level away from the path Steam expects. Record the actual root before acting.

Check for the game under that library's steamapps/common folder and compare its AppID with appmanifest_<AppID>.acf. If both exist, select the correct library in Storage and let Steam verify it. If the ACF is missing, read the AppManifest guide; never copy one from another installation.

Forum posts sometimes suggest hand-editing VDF entries. That is a single user's experience, not a general repair method. The client owns numbered slots and nested values, which may vary. Back up important data and use Steam's controls for changes.

SymptomCheck firstSafer next step
Drive is missing in StorageCan the operating system open the drive?Reconnect it and use Steam to add its library root.
Library appears but shows no gamesDoes the selected root contain steamapps/common?Select the folder that actually contains the Steam library.
Files exist but Steam shows InstallDo AppID and appmanifest match in that library?Use Steam's existing-folder or verify flow.
A full download starts unexpectedlyIs the selected path one directory too high or low?Pause and verify the path before continuing.
Old and cloned drives are both connectedAre duplicate libraries confusing the selection?Identify each drive by its actual root; do not copy entries between them.

Do not use a forum edit as a universal fix

Anecdotal success on one client and drive layout does not establish a safe procedure for another installation.


Inspect libraryfolders.vdf Without Changing It

Locate the file through the active Steam installation. If inspection is needed, make a backup and open it in a plain-text editor without saving. Read the numbered paths and app identifiers; avoid auto-format or replace commands.

Note the drive, library root, AppID, ACF filename, and whether the game folder exists. Wait until downloads and verification finish so the file is not changing during inspection.

The Valve KeyValues reference explains format syntax; it is not advice to edit Steam's configuration. If the client still cannot recognize the library, use Steam's repair options or support rather than guessing at braces or slot numbers.

Read a copy and leave the original alone

A read-only check can help explain the mismatch while preserving Steam's current state for recovery.


Do Not Confuse Neighboring Steam Files

Steam file names are easy to confuse. libraryfolders.vdf concerns library locations; appmanifest_<AppID>.acf records one app's local state; depot .manifest describes a content snapshot; depotcache and steamapps/content have download roles.

For a missing library game, check Storage, the root, ACF, and game folder. For raw depot output or ACF fields, use the related guides below.

Your questionRelevant resourceWhat it does not replace
Which library contains the game?This libraryfolders.vdf guideSteam's own Storage registration
What does one ACF record mean?Steam AppManifest file guideA depot manifest or license
Where did raw depot output go?Steam depot downloads folder guideA normal installed game entry
Is a package available for an AppID?Steam Manifest FinderLocal library recognition or ownership

Fix the layer that is actually wrong

A library registration issue, an ACF issue, and a depot download issue require different evidence and different actions.


Steam libraryfolders.vdf FAQ

A Steam-managed KeyValues file associated with library folders and app entries. It can show recorded paths, but it is not a game file or a manual repair form.

The location varies by installation and client version. Use Steam Storage to identify the active libraries rather than relying on one copied path.

Entries can include app identifiers. Compare the AppID with the game folder and appmanifest in that library; this does not guarantee a complete install.

This guide does not recommend that. Use Storage and Steam's existing-folder or verification workflow because the client manages these values.

The drive letter, registered root, game folder, or ACF may no longer match. Confirm the path in Storage and let Steam inspect the files.

No. libraryfolders.vdf describes library locations; an appmanifest ACF records one app's local state. Do not copy either from an unrelated installation.

No. It describes library configuration. Installed files, depot manifests, cache data, and raw download output have separate roles.

Technical and user-source references

  1. Valve Developer Community — KeyValues — Technical background on Valve's nested KeyValues format; it is not end-user repair documentation.
  2. Steam Community — Steam not finding installed games on a cloned drive — A user report illustrating the moved-drive symptom; the reported manual edit is not endorsed as a general fix.
  3. GitHub — Steam library integration notes — A project implementation note used only as secondary context for library paths and AppID entries.