Where Steam Installs Games by Default

Steam's default install location is C:\Program Files (x86)\Steam\steamapps\common\<game name>. For Unturned™, the path becomes C:\Program Files (x86)\Steam\steamapps\common\Unturned. This reference, written for 57 Studios™ Knowledge Base readers, explains why Steam picks this location, how the Steam library-folder model works, how to add library folders on additional drives, and how professional modders typically structure their drives for serious development work. Understanding these rules is essential because mod-development workflows often involve multiple drives, junction points, and large asset directories that benefit from being separated from the operating-system drive.

The default install path is a starting point rather than a destination. Active modders typically build out a multi-drive layout over time as their library and their mod projects grow. The decisions covered in this article are the foundation for that long-term layout. Time spent thinking about drive layout up front is time saved when migration becomes necessary later.

Pro tip

Even if you accept the default install location for now, set up a second Steam library folder on a secondary drive before installing additional large games. Migrating later is possible but is easier to plan up front.

Prerequisites

You need Steam installed and Unturned installed (covered in previous articles). The article assumes you can open File Explorer and navigate standard Windows directory structures.

What you'll learn

By the end of this article you will be able to:

• State Steam's default install path from memory
• Explain why Steam selects this location
• Add a second Steam library folder on a different drive
• Move installed games between library folders
• Choose a sensible drive layout for active mod development
• Understand the role of the appmanifest file in Steam's library system
• Compare drive types for their suitability as a Steam library folder

The default install path

Steam's installer places the Steam client itself at C:\Program Files (x86)\Steam on a default Windows installation. Inside this folder, Steam creates a subdirectory named steamapps, and inside steamapps it creates a subdirectory named common. Each game installed through Steam receives a folder under common, named after the game.

C:\
└── Program Files (x86)\
    └── Steam\
        ├── Steam.exe
        ├── steamapps\
        │   ├── appmanifest_304930.acf
        │   ├── common\
        │   │   ├── Unturned\
        │   │   ├── Counter-Strike Global Offensive\
        │   │   └── <other installed games>\
        │   ├── downloading\
        │   ├── shadercache\
        │   └── workshop\
        ├── userdata\
        └── logs\

The ASCII tree above shows the canonical layout of a default Steam install. The two locations of particular interest to modders are steamapps\common\Unturned (the install folder, covered in the previous article) and steamapps\appmanifest_304930.acf (the manifest file Steam consults during verification).

Did you know?

The number 304930 in the manifest filename is Unturned's Steam App ID. Every game on Steam has a unique App ID, and the App ID appears in many internal Steam files including manifests, configuration entries, and command-line parameters.

The path components explained

The default install path has four meaningful components, each with its own role.

Component	Purpose
C:\	The drive letter; the operating-system drive by default
Program Files (x86)\	The standard Windows directory for 32-bit applications
Steam\	The Steam client install directory
steamapps\	The Steam library folder root for this Steam install
common\	The subdirectory containing per-game install folders
Unturned\	The Unturned-specific install folder

The path component table above shows the layered structure. Each layer has a different owner and a different purpose; understanding the layers is the foundation for understanding the library folder model.

The appmanifest file

Inside steamapps/ sits an appmanifest file for every installed game. The file is a plain-text Steam-internal format describing the install state: the game's App ID, the install location, the install size, the last update timestamp, and a list of installed depots. Steam consults the appmanifest at every operation that touches the game.

"AppState"
{
    "appid"     "304930"
    "Universe"  "1"
    "name"      "Unturned"
    "StateFlags"    "4"
    "installdir"    "Unturned"
    "LastUpdated"   "1715712000"
    "SizeOnDisk"    "6291456000"
    "buildid"   "..."
    "...other fields..."
}

The example structure above shows the high-level shape of an appmanifest. Steam reads and writes these files as needed; manual editing is not supported and can break Steam's tracking of the install.

Common mistake

Never edit an appmanifest file manually. Steam tracks every install through these files, and a malformed appmanifest can cause Steam to consider the install corrupted. Use Steam's UI for every install operation; the UI updates the appmanifest correctly.

Why Steam picks this location

Windows has historically separated the operating system drive (C:) from data drives, and applications have traditionally installed under Program Files. Steam follows this convention with one notable adjustment: it installs under Program Files (x86) rather than Program Files. The reason is historical.

The diagram above shows the bitness split. Steam was originally a 32-bit application, and 32-bit applications on 64-bit Windows install to Program Files (x86) by convention. Even though many modern games installed through Steam are 64-bit, they install under the Steam client's path, which means they inherit the (x86) suffix even when they would not naturally belong there. This is a quirk of Steam's history rather than a meaningful technical decision.

Common mistake

Beginners sometimes assume that the (x86) suffix means a game is 32-bit and therefore lower-performance. The suffix only reflects the path Steam chose during its own install years ago. It says nothing about the bitness of any individual game.

The history of the Steam client's bitness

Steam was originally released in 2003 as a 32-bit Windows application. At the time, 32-bit was the dominant Windows architecture and the choice was the standard one. Windows did not yet make a meaningful distinction between 32-bit and 64-bit application install paths.

When Windows added 64-bit support and the Program Files and Program Files (x86) distinction, the existing 32-bit Steam install fell on the Program Files (x86) side by default. Valve chose to keep the Steam client 32-bit for backward compatibility with older systems. The result is the current state: a 32-bit Steam client installed under Program Files (x86), with games of any bitness installed below it.

The Steam client has gradually adopted 64-bit components for specific subsystems while keeping the main client process 32-bit. The install path has not changed because changing it would break every existing installation worldwide.

Year	Steam client bitness	Default install path
2003	32-bit	C:\Program Files\Steam
2010	32-bit	C:\Program Files (x86)\Steam (after 64-bit Windows became common)
2020	32-bit (with 64-bit subsystems)	C:\Program Files (x86)\Steam
Current	32-bit (with growing 64-bit subsystems)	C:\Program Files (x86)\Steam

The history table above shows the path's stability. The (x86) suffix is a historical artefact rather than a current technical statement.

Adding a Steam library folder

A Steam library folder is a directory anywhere on disk that Steam treats as a valid install destination. The default library folder is the steamapps directory under the Steam install path. You can add additional library folders on any drive.

1. Open the Steam client
2. Click Steam in the top-left menu bar, then Settings
3. Click the Storage tab in the left sidebar
4. Click the + button (or the dropdown menu) near the top of the Storage panel
5. Select Add Drive and choose the drive you want to use
6. Steam creates a new SteamLibrary folder on that drive and registers it as a library folder

After the new library folder exists, every subsequent install prompts you to choose between the available library folders. You can also move existing games between library folders using Right-click to Properties to Installed Files to Move install folder.

Pro tip

Name your library folders consistently across drives. The default name SteamLibrary is fine, but some modders prefer drive-specific names like Steam-D or SteamLibrary-NVMe to make paths self-documenting.

The library folder configuration file

Steam tracks the list of library folders in a configuration file named libraryfolders.vdf, which lives in the config subdirectory of the Steam install. The file lists every registered library folder with its drive letter, path, and a list of the App IDs installed in that folder.

Field in libraryfolders.vdf	Purpose
path	Absolute filesystem path to the library folder
label	Optional human-readable name for the library
mounted	Whether the library is currently accessible (1) or disconnected (0)
apps	List of App IDs installed in this library, with their disk sizes

The configuration file is read by Steam at every startup. If a library folder is unavailable (because the drive is disconnected, for example), Steam marks the folder as unmounted and displays the games as unavailable until the drive returns.

Did you know?

You can inspect the libraryfolders.vdf file with any text editor. The file is human-readable and is useful for confirming Steam's view of your library configuration. Manual editing is supported in principle but Steam's UI is the recommended way to make changes.

Comparing drive types for library folders

Mod-development workflows are sensitive to drive performance because they involve frequent reads of asset bundles, frequent writes of compiled mod output, and large source-asset libraries. The drive you choose for your Steam library folder has real consequences.

Drive type	Suitability for Steam library	Notes
Primary NVMe SSD (system drive)	Good for the Steam client itself; acceptable for active games	Keep some headroom for the OS
Secondary NVMe SSD	Excellent for active modding	Recommended primary library for serious modders
SATA SSD	Very good	Solid choice for everyday installs
Internal 7200 RPM HDD	Acceptable for archived games	Discouraged for active mod work
Internal 5400 RPM HDD	Suitable only for cold storage	Avoid for active games
External USB SSD	Good for portability	Risk of disconnection during writes
External USB HDD	Discouraged	Slow and disconnection-prone
Network-attached storage	Not supported	Steam does not support network paths

The table above compares each common drive type. The recommended layout for a dedicated modding machine is a primary NVMe SSD for the operating system and the Steam client, plus a secondary NVMe SSD as the primary Steam library folder. This gives the operating system its own performance headroom while providing fast access to game and mod files.

Drive performance impact on modding workflows

The drive choice has measurable consequences for specific modding workflows. The following table maps common modding tasks to their drive-speed sensitivity.

Modding task	Drive speed sensitivity	Impact of slow drive
Loading vanilla bundle for reference	High	Multiple seconds per bundle load
Compiling a custom map for testing	High	Compile time doubles or triples
Launching Unturned with mods	High	Launch time noticeably slower
Running Unity Editor on Unturned assets	High	Editor responsiveness degrades
Reading documentation files	Low	Negligible difference
Editing text-based mod files	Low	Negligible difference
Running a verification	High	Verification time doubles or triples
Steam updates	High	Update time scales with drive speed

The sensitivity table above shows where the drive choice matters most. Active modding work is concentrated in the high-sensitivity categories; a slow drive penalises the modder repeatedly throughout the day.

Pro tip

If you can afford only one performance-class drive, put the Steam library on it rather than the operating system. The OS drive's performance affects boot time and application launches; the library drive's performance affects every minute of active modding work.

Where professional modders actually store their libraries

Survey data from active modding communities suggests a strong preference for SSD-based library folders, with most professional modders using a secondary drive rather than the operating-system drive.

The pie chart above shows the approximate distribution. The reasoning behind the secondary-NVMe preference is practical: keeping game files off the OS drive isolates write activity, extends OS-drive lifespan, and provides a clean restore path if the OS drive ever needs to be wiped.

Best practice

Reserve the operating-system drive for the operating system, the Steam client, and small applications. Move large games and mod-source libraries to a secondary drive. This is the layout most professional modders converge on independently.

Typical layouts by user type

Different categories of users converge on different drive layouts. The following table summarises the patterns observed in practice.

User type	Typical drive layout
Casual player, single drive	Steam library on the OS drive; default location
Casual player, two drives	Steam library on the secondary drive; OS drive reserved for OS
Active modder, two drives	Steam library on the secondary NVMe; OS drive for OS only
Active modder, three drives	Primary NVMe for OS, secondary NVMe for active Steam library, mechanical drive for cold storage
Professional modder, three or more drives	Dedicated modding NVMe separate from gaming library
Server operator	Dedicated drive for Unturned headless server; isolation from client install
Multi-user household	Single shared NVMe library across user accounts

The layout patterns above are observed in practice; they are not the only valid configurations. The right layout depends on individual budget, available drives, and intensity of use.

Migrating an existing install to a new library folder

If you installed Unturned to the default location and later decide to move it to a different drive, the process is straightforward:

1. Add the new library folder using the Storage settings as described above
2. In the Library, right-click Unturned
3. Click Properties to Installed Files
4. Click Move install folder
5. Choose the new library folder and confirm

Steam copies the entire install folder to the new location, updates its internal records, and removes the old copy. The process takes proportional time based on the size of the install and the speed of both drives.

The flowchart above shows the migration sequence. A verification on the new copy is recommended after migration completes, as a defensive measure against the small chance of file corruption during the copy.

Common mistake

Do not move the install folder manually using File Explorer's cut and paste. Steam tracks every install through its manifest system, and a manual move leaves Steam pointing at the old location. Always use the Move install folder feature inside Steam.

Migration time estimates

The migration copies the entire install folder between drives. The duration depends on the source drive speed, the destination drive speed, and the total install size.

Source drive	Destination drive	Approximate migration time (6 GB install)
NVMe SSD	NVMe SSD	30 to 60 seconds
NVMe SSD	SATA SSD	1 to 2 minutes
NVMe SSD	7200 RPM HDD	2 to 4 minutes
SATA SSD	NVMe SSD	1 to 2 minutes
SATA SSD	SATA SSD	2 to 3 minutes
7200 RPM HDD	NVMe SSD	2 to 4 minutes
7200 RPM HDD	7200 RPM HDD	4 to 8 minutes
External USB drive	Any internal drive	5 to 15 minutes
Any internal drive	External USB drive	5 to 15 minutes

The migration time table above is a planning reference. Most migrations complete in a few minutes; only the worst-case combinations of slow drives and large installs take longer than 10 minutes.

Migration safety considerations

The migration operation is reliable in practice. Steam copies the files, verifies the copy, and only removes the source after the destination is confirmed intact. If the migration fails partway through, the original install remains usable; Steam does not delete the source until the destination is complete.

The recommended pre-migration steps are:

1. Confirm the destination drive has enough free space for the entire install
2. Close Unturned if it is running
3. Cancel any pending Steam downloads
4. Run a verification on the source install before starting the migration
5. Start the migration through the Move install folder feature

The recommended post-migration steps are:

1. Confirm the migration completed successfully (library tile shows Play)
2. Run a verification on the new copy
3. Launch Unturned briefly to confirm the new install works
4. Remove the old library folder if it is no longer needed

The pre- and post-migration steps above are defensive practices that catch the rare cases where something goes wrong. Most migrations complete cleanly without intervention.

Junction points and advanced layouts

Some modders create NTFS junction points or symbolic links to make a folder appear in two places on disk at once. This is occasionally useful when a mod tool expects assets at a specific path, but it is an advanced filesystem topic.

Critical warning

Do not create junctions or symbolic links inside the Unturned install folder without a clear reason. Steam's verification compares files at their canonical paths, and incorrectly configured junctions can cause verification loops in which Steam repeatedly re-downloads the same files.

For most modders, the default behavior (one install per game per library folder, with no junctions) is the correct choice. Junction points are appropriate only when a specific external tool requires a specific path that does not match the Steam-managed location.

When junctions are appropriate

Junction points are appropriate in a small number of specific scenarios. The following table maps the scenarios to their use cases.

Scenario	Junction use
External tool requires assets at a fixed path	Junction makes the install folder appear at the fixed path
Mod tool reads from a path different from Steam's location	Junction bridges the path difference
Shared assets between multiple game installs	Junction allows shared content to live in one location
Migration in progress; cannot complete in one step	Junction temporarily bridges old and new locations

In every other scenario, junctions are unnecessary and add complexity. The recommended default is no junctions; add them only when a specific tool's documentation requires them.

Advanced considerations

A handful of advanced points are worth knowing for users who plan to manage many installed games or many drives.

Steam's shadercache and downloading folders

Within steamapps there are two helper folders: shadercache and downloading. The shadercache folder holds pre-compiled shaders that speed up game launches, and the downloading folder holds in-progress downloads. Both folders are managed automatically by Steam and should not be touched manually. Each library folder has its own copies of these helper folders.

One game, multiple installs

Steam does not support installing the same game in two library folders simultaneously. If you need two independent installs of Unturned (for example, one stable and one experimental), the supported approach is to install the game once and create a second copy outside Steam's management, accepting that the second copy will not receive updates automatically.

Cloud saves and library folders

Cloud-synchronized saves are not stored in the install folder and are unaffected by library-folder changes. Moving Unturned between library folders does not affect your saves.

The userdata folder

Steam maintains a userdata folder at the root of its install. This folder contains per-user configuration for the Steam client itself, not for individual games. Library folder changes do not affect the userdata folder; it remains where Steam was originally installed.

Steam-level folder	Contents	Affected by library changes
steamapps/common/<game>	Game install files	Yes; this is what library folders contain
steamapps/appmanifest_*.acf	Per-game install metadata	Yes; moved with the game
steamapps/workshop/	Workshop subscriptions	Yes; managed per library folder
userdata/	Per-user Steam configuration	No; stays at original Steam install
logs/	Steam client logs	No; stays at original Steam install
config/	Steam client configuration	No; stays at original Steam install

The Steam-level folder table above shows which directories are part of the library folder model and which are part of the Steam client itself. Only the library-folder directories move with games; the rest stay where Steam was originally installed.

FAQ

Can I change Steam's default library folder?

Yes. In the Storage settings, click the three-dot menu next to a library folder and select Set as default. Future installs will default to that library folder.

How many library folders can I add?

Steam supports many library folders, far more than any practical layout requires. There is no published hard limit. Most modders end up with two to four library folders; more than that becomes difficult to manage.

Can I install Steam itself on a non-system drive?

Yes, but only at install time. The Steam client must be re-installed to move it after the fact. Most users leave Steam on C: and create additional library folders on other drives.

What happens to my saved games when I uninstall Unturned?

Saves are stored in %AppData%\Unturned, which is outside the install folder. Uninstalling the game leaves saves intact unless you explicitly delete the AppData folder.

Does Steam compress games on disk?

Steam decompresses every file during install and stores them uncompressed afterward. Compression-only filesystems like NTFS compression can be applied at the OS level, but this is rarely worthwhile for modern drives.

Can I have a library folder on a network drive?

No. Steam does not support library folders on network-attached storage (NAS) or other network paths. Steam requires direct filesystem access for performance and reliability reasons.

What happens if I plug in an external drive with an existing Steam library folder?

Steam detects the library folder at the next startup and mounts it automatically. Games installed in the external library appear in your Steam library and can be launched directly from the external drive. This is the supported pattern for portable Steam libraries.

Can I share a library folder between two computers?

Not simultaneously. A Steam library folder is locked to one Steam client at a time. If you move the drive to a second computer and start Steam there, the second Steam client claims the library. Returning the drive to the first computer requires Steam there to re-detect and re-mount the library.

What is the appmanifest file and should I edit it?

The appmanifest is Steam's internal record of an install. It is a plain-text file with the game's metadata. You should not edit it manually; Steam's UI is the supported way to change install state. Reading the file is fine for diagnostic purposes.

Why does my library folder show as "unmounted"?

This usually means the drive containing the library folder is disconnected. Reconnect the drive and Steam will mount the library at the next startup. If the drive is connected but Steam still shows unmounted, restart Steam.

Can I rename a library folder?

The SteamLibrary folder itself can be renamed before Steam registers it, but renaming after registration breaks Steam's tracking. The supported way to change a library folder's name is to remove it from Steam's list, rename the folder, then add it back as a new library.

How do I know which library folder contains a given game?

Right-click the game in the Steam Library, click Properties, click Installed Files. The install location at the top of the panel shows the full path including the library folder.

Best practices

• Memorize Steam's default install path: C:\Program Files (x86)\Steam\steamapps\common\<game name>
• Add a secondary library folder on a fast drive before installing additional large games
• Use Steam's Move install folder feature, never manual file moves
• Reserve the system drive for the OS and small applications
• Avoid junction points and symbolic links unless a specific tool requires them
• Name library folders consistently across drives for clarity
• Run a verification after every library folder migration
• Keep at least 20 percent free space on every library folder drive
• Do not edit appmanifest files manually
• Use Steam's Storage settings as the canonical interface for library management

Appendix A: library folder layout reference

The following layouts are observed patterns among Unturned modders. Each layout is appropriate for a specific user profile.

Layout 1: single-drive casual

A casual player with a single internal drive uses the default Steam install location. No additional library folders are needed.

C:\
└── Program Files (x86)\
    └── Steam\
        └── steamapps\
            └── common\
                └── Unturned\

This is the simplest valid layout. It is appropriate for users who play one or two games and do not anticipate growing their library substantially.

Layout 2: two-drive separation

A user with an OS drive and a games drive keeps the OS drive uncluttered and installs games to the secondary drive.

C:\                          D:\
└── Program Files (x86)\     └── SteamLibrary\
    └── Steam\                   └── steamapps\
        └── (Steam client only)      └── common\
                                         └── Unturned\

This is the recommended layout for most active modders. It separates the OS from the games and provides clear performance isolation.

Layout 3: three-drive professional

A professional modder with an OS drive, an active games drive, and a cold-storage drive uses three library folders.

C:\                          D:\                          E:\
└── Program Files (x86)\     └── SteamLibrary-NVMe\        └── SteamLibrary-HDD\
    └── Steam\                   └── steamapps\                  └── steamapps\
        └── (Steam client only)      └── common\                     └── common\
                                         └── Unturned\                   └── (archived games)
                                         └── (active games)

This layout provides dedicated performance for active mod work while keeping cold-storage games available without filling up the fast drive.

Layout 4: portable external

A modder who works across multiple computers uses an external USB SSD as the library folder. The external drive contains every game and every mod-related file.

<External USB SSD>:\
└── SteamLibrary\
    └── steamapps\
        └── common\
            └── Unturned\

This layout enables portable modding work. The external drive moves between computers with all installed games and Workshop subscriptions intact.

Appendix B: drive layout selection guide

The following decision tree maps user requirements to the recommended drive layout.

The decision tree above is the simplified selection guide. Most modders pick Layout 2 or Layout 3; Layout 1 is appropriate for casual users who do not modify the game, and Layout 4 is a specialised choice for users who need portability.

Appendix C: library folder maintenance

Library folders accumulate state over time. Periodic maintenance keeps the library tidy and the disk usage predictable.

Removing unused games

Games no longer played can be uninstalled to free space. The uninstall is reversible; the game can be re-installed at any time from the Steam library. The uninstall affects only the install folder, not the saves and settings in %AppData%.

Auditing library folder sizes

The Steam Storage panel shows the disk usage of each library folder and the breakdown by installed game. Auditing this panel monthly is a small habit that catches unexpected disk usage growth before it becomes a problem.

Defragmenting library folders

NVMe SSDs do not benefit from defragmentation; modern Windows skips SSDs automatically. Mechanical HDDs do benefit from occasional defragmentation, but the benefit is small for modern Steam installs because game files do not change frequently. Periodic defragmentation of an HDD library folder every few months is reasonable.

Drive health monitoring

Monitor the SMART attributes of every drive that holds a Steam library folder. A drive showing degraded SMART status should be replaced before it fails. Tools like CrystalDiskInfo on Windows provide the SMART reading.

Maintenance task	Frequency
Audit library folder sizes	Monthly
Remove unused games	Every few months
Defragment HDD library folders	Every few months (HDD only)
Check SMART status	Monthly
Verify recently-played games	After updates
Back up custom modding work	After every modding session

The maintenance schedule above keeps the library in good shape over the long term. Most of the tasks take a few minutes; the cumulative time investment is small relative to the time spent modding.

Appendix D: Smartly Dressed Games documentation references

The Smartly Dressed Games official documentation at https://docs.smartlydressedgames.com/en/latest/about/getting-started.html covers several library-folder-adjacent topics. The 57 Studios Knowledge Base complements but does not replace the official documentation.

Relevant official documentation sections include:

• Filesystem layout requirements for mod development
• Path conventions for custom maps and modules
• Server installation paths for dedicated server operators
• Workshop content directory structure

Bookmark the official documentation alongside the knowledge base. Both resources are designed to be read in parallel.

Appendix E: library folder mental model

The library folder model is a tree with two distinct levels: the Steam client install at the root, and the library folders as children. Each library folder is independent of every other library folder; games can be moved between them but only one library folder holds a given game at a time.

                              The Steam library folder mental model


                                      +-------------------+
                                      |                   |
                                      |  STEAM CLIENT     |
                                      |  (one install)    |
                                      |                   |
                                      +-------------------+
                                              |
                              +---------------+---------------+
                              |               |               |
                              v               v               v
                  +-------------------+ +-------------------+ +-------------------+
                  |                   | |                   | |                   |
                  |  LIBRARY FOLDER 1 | |  LIBRARY FOLDER 2 | |  LIBRARY FOLDER 3 |
                  |  (default)        | |  (secondary)      | |  (cold storage)   |
                  |                   | |                   | |                   |
                  +-------------------+ +-------------------+ +-------------------+
                          |                       |                       |
                          v                       v                       v
                      Game A                  Game C                  Game E
                      Game B                  Game D (Unturned)       Game F

The mental model diagram above shows the tree structure. One Steam client, many library folders, many games distributed across the library folders. Understanding this structure is the foundation for every library folder decision.

Level	What lives here	How many
Steam client	The Steam executable and its supporting files	One per machine
Library folder	A collection of installed games	One or more per machine
Game install	A single installed game	Many per library folder
Workshop content	Subscribed Workshop downloads	Per library folder

The level table above is the canonical reference for the library folder tree.

Appendix F: glossary of library folder terms

The following terms appear throughout this article. The working definitions provided here align with Steam's published documentation.

• App ID — Unique numeric identifier Steam assigns to each game. Unturned's App ID is 304930.
• appmanifest — Steam-internal file recording the install state of a game. Lives in the steamapps directory.
• Default library folder — The library folder Steam pre-fills in the install dialog. Can be changed in Storage settings.
• Game folder — The subdirectory under steamapps/common that holds a single installed game.
• Junction point — NTFS feature that makes a folder appear at a second location on disk. Not generally recommended inside library folders.
• Library folder — A directory anywhere on disk that Steam treats as a valid install destination. Each library folder has its own steamapps/common structure.
• libraryfolders.vdf — The Steam configuration file that lists every registered library folder.
• Mounted — A library folder that is currently accessible. Library folders on disconnected drives show as unmounted.
• steamapps — The directory inside each library folder that holds appmanifest files and the common subdirectory.
• Workshop content — Subscribed Workshop downloads, stored per-library-folder under steamapps/workshop.

The glossary above is the vocabulary used by Steam's UI and documentation. Familiarity with these terms makes the rest of the Steam ecosystem easier to navigate.

Appendix G: Steam library folders on different operating systems

The 57 Studios Knowledge Base is written for Windows users, but the Steam library folder model exists on macOS and Linux as well. The conceptual model is the same; the path conventions differ.

Operating system	Default Steam install	Default library folder location
Windows	C:\Program Files (x86)\Steam	C:\Program Files (x86)\Steam\steamapps
macOS	~/Library/Application Support/Steam	~/Library/Application Support/Steam/steamapps
Linux	~/.steam/steam	~/.steam/steam/steamapps
Steam Deck	~/.steam/steam	~/.steam/steam/steamapps

The cross-platform table above shows the path conventions. The library folder model is identical across platforms; only the filesystem paths and the operating system conventions differ.

Unturned is officially distributed for Windows. Users on macOS or Linux who want to play Unturned typically use Steam's Proton compatibility layer (Linux) or community-supported configurations (macOS). These paths fall outside the scope of the 57 Studios Knowledge Base; the Windows path is the supported configuration for the modding workflows documented here.

Appendix H: library folder failure modes

Library folders occasionally enter unexpected states. The following table documents the failure modes and their recovery procedures.

Failure mode	Symptom	Recovery procedure
Library folder drive disconnected	Library shows as unmounted; games unavailable	Reconnect the drive; Steam re-mounts automatically
Library folder drive failed permanently	Library remains unmounted; games unavailable	Remove library folder from Steam; install games to a different library
Library folder permissions lost	Verification fails; install fails	Repair NTFS permissions on the library folder root
Library folder configuration file corrupted	Steam does not see the library folder	Restore libraryfolders.vdf from a backup, or re-add the library
Library folder filesystem corrupted	Files report errors when read	Run Windows CHKDSK; recover or rebuild the library
Two library folders pointing at the same path	Steam behaves erratically	Remove one of the duplicate library folders
Library folder in use by another Steam client	Library shows as locked	Close the other Steam client; restart Steam
Library folder on read-only media	Installs fail with disk write errors	Move library to read-write media

The failure mode table above is the diagnostic reference for library folder problems. Most modders will never encounter these failure modes, but knowing the recovery procedures is useful when they occur.

CHKDSK and library folder recovery

If a library folder shows file read errors, Windows CHKDSK can repair filesystem corruption. The procedure is:

1. Open Command Prompt as administrator
2. Run chkdsk D: /f /r where D: is the drive containing the library folder
3. Allow CHKDSK to schedule a check at next boot if the drive is in use
4. Restart Windows; CHKDSK runs during boot
5. After boot, verify the affected games through Steam

CHKDSK can take a long time on large drives. The repair is most useful for mechanical hard drives; SSDs rarely benefit from CHKDSK because solid-state failure modes are different from mechanical failure modes.

Common mistake

Do not run CHKDSK on an SSD with the /r flag unless you suspect actual filesystem corruption. The /r flag includes a surface scan that puts unnecessary write load on the SSD. For SSDs, chkdsk D: /f without /r is the appropriate command.

Appendix I: library folder analytics

Steam provides several views of library folder usage through the Storage panel. Understanding what each view shows is useful for managing library folder size over time.

Storage panel view	What it shows
Library folder list	All registered library folders with drive and total size
Installed games per folder	Per-library breakdown of installed games
Game size details	Per-game disk usage including DLC and Workshop content
Workshop content size	Per-game Workshop content disk usage
Total Steam usage	Aggregate disk usage across all library folders
Free space per drive	Remaining capacity on each drive containing a library folder

The Storage panel is the canonical view of library folder state. Browsing the panel monthly catches unexpected growth and identifies candidates for archival or removal.

Reading the Steam usage breakdown

The Storage panel shows disk usage with the following hierarchy:

Total Steam Library Usage
  └── Per-library breakdown
      └── Per-game breakdown
          ├── Base game install
          ├── DLC content
          ├── Workshop subscriptions
          └── Save data (when applicable)

The hierarchy above is the breakdown shown in the Storage panel. Each level can be expanded or collapsed for a quick overview or a detailed view.

Identifying large items

For Unturned specifically, the Workshop content can grow substantially over time as you subscribe to maps, items, and other community content. The Storage panel makes it easy to identify Workshop content that has accumulated and that you no longer use.

Identifying signal	Recommended action
Workshop content larger than 5 GB	Audit subscriptions; unsubscribe from unused content
Workshop content larger than 10 GB	Significant cleanup opportunity
Game has not been played in 6+ months	Candidate for archival to cold storage
Game DLC larger than the base game	DLC may be unused; consider per-DLC review
Library folder is nearly full	Move some games to a different library folder

The audit signals table above is the practical reference for library folder cleanup. Most modders converge on a periodic audit cadence after their library grows past about 10 games.

Appendix J: scenarios for library folder configuration

The following scenarios are common starting points for library folder configuration. Each scenario describes the user's situation and the recommended configuration.

Scenario 1: new gaming PC with one drive

A new gaming PC has a single 1 TB NVMe SSD. The user has never used Steam before.

Recommended configuration:

1. Install Steam to the default location at C:\Program Files (x86)\Steam
2. Use the default library folder (no additional library folders needed)
3. Install Unturned and other games to the default location

This is the simplest configuration. The single drive provides both OS storage and game storage. If the drive fills up, add a secondary drive later and migrate older games.

Scenario 2: gaming PC with separate OS and games drives

A gaming PC has a 500 GB NVMe SSD as the OS drive and a 2 TB NVMe SSD as a dedicated games drive. Steam is not yet installed.

Recommended configuration:

1. Install Steam to the default location at C:\Program Files (x86)\Steam (on the OS drive)
2. Add a Steam library folder on the games drive at D:\SteamLibrary
3. Set the games drive library folder as the default for new installs
4. Install Unturned to the games drive library folder

This is the recommended configuration for an active modder. The OS drive holds the Steam client and a small footprint; the games drive holds the actual game files.

Scenario 3: laptop with limited internal storage

A laptop has a single 256 GB internal SSD. The user wants to install Unturned and several other games but is concerned about disk space.

Recommended configuration:

1. Install Steam to the default location at C:\Program Files (x86)\Steam
2. Install Unturned to the default library folder
3. Acquire an external USB SSD as supplementary storage
4. Add a Steam library folder on the external drive
5. Install additional large games to the external drive

This configuration balances the internal drive's limited capacity with the convenience of always-available core games. The external drive is mounted when needed for the larger games.

Scenario 4: shared family computer

A family computer has multiple Windows user accounts. Multiple users want to play different Steam games.

Recommended configuration:

1. Install Steam to the default location at C:\Program Files (x86)\Steam
2. Use the default library folder (shared across all Windows users)
3. Each Windows user runs their own Steam client signed in to their own Steam account
4. Each user's installed games appear in their own Steam library

The shared install location works because Steam licenses are per-account and library folders are per-machine. Each user sees their own games in their own Steam library, but the underlying install files are shared on disk.

Scenario 5: modder migrating from HDD to SSD

A modder has Unturned installed on a 7200 RPM HDD and has acquired a new NVMe SSD. The modder wants to move Unturned to the faster drive.

Recommended configuration:

1. Install the new NVMe SSD in the system
2. Add a Steam library folder on the new drive
3. Use Move install folder to migrate Unturned from the HDD to the NVMe
4. Verify the new install on the NVMe
5. Optionally remove the old library folder from Steam if the HDD will be repurposed

The migration is the supported way to move an existing install between drives. After the migration, the modder gets the performance benefit of the NVMe for all subsequent modding work.

Cross-references

• How to Install Unturned — the install procedure that uses the default library folder
• How to Verify Unturned Game Files — verification reads from the library folder
• How to Find Your Unturned Install Folder — locating the install folder inside the library folder
• How to Launch Unturned for the First Time — first launch reads from the library folder

Document history

Version	Date	Author	Notes
1.0	2024-09-18	57 Studios	Initial publication
1.1	2024-12-12	57 Studios	Added drive type comparison table and migration sequence
1.2	2025-04-15	57 Studios	Added junction point guidance and advanced layout examples
2.0	2026-05-17	57 Studios	Major expansion. Added library folder mental model, layout reference appendix, maintenance schedule, and glossary. Expanded FAQ from 5 to 12 questions.

Next steps

With library folders understood, proceed to How to Launch Unturned for the First Time to initialize the game's user-data files and prepare for mod development.