How to Find Your Unturned Install Folder

Finding the Unturned™ install folder is a skill every modder uses constantly. The install folder contains every game asset, every configuration file, and every directory into which custom content can be dropped during mod development. The 57 Studios™ Knowledge Base assumes throughout the rest of its articles that you can locate this folder quickly and reliably. This reference covers the two primary methods for finding it: the Steam-managed shortcut through the Library context menu, and the manual File Explorer navigation path. Both methods produce identical results, but each is appropriate in different contexts.

The Unturned install folder is the source of truth for vanilla game assets. Every map, every item, every texture, every sound effect, and every configuration template that ships with Unturned lives somewhere inside this folder. Modders read these files constantly during development to understand how the vanilla game is structured and to use vanilla assets as the starting point for their own work. A modder who cannot navigate to the install folder confidently and quickly is at a permanent disadvantage relative to one who can.

Pro tip

Pin the Unturned install folder to your Windows Quick access list. This makes the folder a single-click destination in File Explorer's sidebar for the rest of your modding career.

Prerequisites

You need Unturned installed and verified (covered in previous articles) and a working Steam client. The Quick access pinning recommended in this article requires File Explorer, which is covered in the next section of the knowledge base.

What you'll learn

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

• Open the Unturned install folder in two distinct ways
• Recognize each major subdirectory inside the install folder
• Map each subdirectory to its modding-related purpose
• Understand the difference between the install folder and the user-data folder
• Pin the install folder for quick future access
• Navigate the install folder confidently from memory
• Identify which subdirectories are read-only and which are safe to modify

Method 1: Steam's Browse local files shortcut

The fastest method to open the Unturned install folder is through Steam's built-in Browse local files shortcut. This method works regardless of where Steam installed the game, which makes it the recommended approach for beginners.

The sequence diagram above shows the click path. The steps in detail:

1. Open the Steam client and click Library
2. Locate Unturned in the left-hand library list
3. Right-click Unturned to open the context menu
4. Hover over Manage to expand its submenu
5. Click Browse local files

A File Explorer window opens at the Unturned install folder. The address bar at the top of the File Explorer window shows the full path to the folder, which you should make a habit of reading and remembering.

Did you know?

The Browse local files command works for every game in your Steam Library, not only Unturned. You can use the same path to locate the install folder of any Steam-managed game.

Why this method is preferred

The Steam shortcut method has several advantages over manual navigation. It works regardless of which library folder Steam used; it works on machines where the user does not know the install path from memory; it works even after a library migration that changed the install location; and it requires only the Steam client to be installed, not any additional software.

Advantage	Why it matters
Works for any library folder	No need to remember which drive Unturned is on
Works after migration	Steam tracks the current path; you do not have to
One-click navigation	Faster than typing a multi-segment path
Same procedure for every game	The skill transfers to other Steam games
No File Explorer skills required	Beginners can use it without prior file-management experience

The advantage table above is the case for using Steam's shortcut as your default. The manual navigation method, covered next, is the appropriate choice in specific situations where the shortcut is unavailable.

Variations on the Steam shortcut

Different Steam client versions present the Browse local files command in slightly different places. The variations are all equivalent in effect; the navigation path differs only in where the menu entry lives.

Steam client version	Path to Browse local files
Current Steam client	Right-click to Manage to Browse local files
Older Steam clients	Right-click to Properties to Local files to Browse
Steam Big Picture mode	Game details page to Manage to Browse files
Steam Deck UI	Game page to gear icon to Properties to Installed Files
Mobile Steam app	Not available; mobile app cannot browse files

The variation table above shows the consistent presence of the shortcut across Steam's various UI surfaces. Only the mobile app lacks the feature, which is reasonable because mobile devices do not have a desktop file manager.

Method 2: Manual navigation through File Explorer

The manual navigation method is slower than the Steam shortcut, but it teaches the structure of Steam's library system and is the only method available when Steam is not running.

1. Open File Explorer (covered in detail in the next section)
2. Navigate to your Steam install drive (typically C:)
3. Enter the path Program Files (x86)\Steam\steamapps\common\Unturned

Common mistake

The folder name is Unturned with a capital U. Windows file paths are case-insensitive by default, so the wrong casing will still work, but matching the official casing avoids confusion when reading documentation written by other modders.

If you have configured Steam library folders on additional drives (covered in the next article), the path will use a different drive letter and library-folder location. The pattern always ends in \steamapps\common\Unturned.

Address bar navigation

The fastest way to perform manual navigation is to type the full path directly into File Explorer's address bar rather than navigating through folders one click at a time. The address bar is the text field at the top of every File Explorer window; clicking inside it converts the breadcrumb display to an editable text path.

Address bar entry	Effect
C:\Program Files (x86)\Steam\steamapps\common\Unturned	Open the default install location
D:\SteamLibrary\steamapps\common\Unturned	Open an install on the D drive
%AppData%\Unturned	Open the user-data folder
%LocalAppData%\Steam	Open the Steam local data folder
steam://nav/console	Open Steam's hidden console interface

The address bar entries above are useful navigation shortcuts. Memorising the install path and the user-data path is a productivity gain for any modder who works on Unturned regularly.

When manual navigation is required

The Steam shortcut works in nearly every situation, but several specific scenarios call for manual navigation:

• Steam is not running and you need to inspect the install folder
• Steam has lost track of the install location and the shortcut produces no result
• You need to access the install folder from a script that does not have Steam access
• You are documenting a path for someone else and need the literal text
• You are configuring an external tool that requires the install path as a parameter

In each scenario the manual path is the supported approach. Knowing both methods gives you a fallback for the cases where the preferred method does not apply.

The structure of the Unturned install folder

After the install folder opens, you will see a list of subdirectories and a handful of files at the top level. The structure is consistent across every Unturned install.

Unturned/
├── Bundles/
│   ├── Assets/
│   ├── Effects/
│   ├── Localization/
│   ├── Maps/
│   ├── Music/
│   ├── Scenes/
│   ├── Sounds/
│   └── Workshop/
├── Cloud/
├── EasyAntiCheat/
├── EngineConfig/
├── ExampleAssets/
├── Extras/
├── Localization/
├── Maps/
├── Modules/
├── Sandbox/
├── Server/
├── StatusReports/
├── Unturned_Data/
├── Unturned_Headless_Data/
├── Unturned.exe
└── Unturned_Headless.exe

The ASCII tree above shows the canonical layout of the install folder. Each top-level entry has a specific purpose, and many of them will appear repeatedly in later sections of this knowledge base.

Subdirectory	Modding purpose
Bundles/	Compiled Unity asset bundles for the base game; modders read these to understand vanilla asset structure
Cloud/	Reserved for Steam Cloud synchronization data
EasyAntiCheat/	Anti-cheat client; modders should not modify these files
EngineConfig/	Boot configuration for the Unity engine
ExampleAssets/	Example mods and assets distributed by Smartly Dressed Games as a learning reference
Extras/	Bonus content and developer-supplied tools
Localization/	Translated strings for the base game; mod localization follows the same structure
Maps/	Base game maps; custom maps drop into this folder for testing
Modules/	Server modules and runtime extensions
Sandbox/	Sandbox-mode assets
Server/	Default server configuration template
StatusReports/	Diagnostic files generated by the game on crash
Unturned_Data/	Compiled Unity client data; rarely edited directly
Unturned_Headless_Data/	Compiled headless-server data; used by dedicated server operators

The table above maps each top-level subdirectory to its role in mod development. The Bundles, Maps, Modules, and ExampleAssets directories are the four you will visit most frequently.

Best practice

Treat the contents of EasyAntiCheat, Unturned_Data, and Unturned_Headless_Data as read-only. Modifications to files in these directories will be flagged by verification and re-downloaded, and modifications to anti-cheat files specifically can result in account flags.

Detailed subdirectory reference

The following sections cover each top-level subdirectory in more detail. The depth of coverage reflects the modding relevance: directories you will visit often get more space than those you rarely touch.

The Bundles directory

The Bundles directory contains compiled Unity asset bundles for the base game. Each subdirectory corresponds to a category of vanilla content: assets, effects, localization data, maps, music, scenes, sounds, and Workshop integration files. Modders read these bundles to understand how vanilla content is organised and to use vanilla assets as starting points for their own work.

Bundles subdirectory	What it contains
Bundles/Assets/	Compiled item, vehicle, and entity definitions
Bundles/Effects/	Particle systems and visual effect prefabs
Bundles/Localization/	Translated strings packed into bundles
Bundles/Maps/	Compiled bundles for the official maps
Bundles/Music/	Background music tracks
Bundles/Scenes/	Unity scene files for menus and gameplay
Bundles/Sounds/	Sound effects organised by category
Bundles/Workshop/	Workshop integration data

The Bundles directory is the reference library for vanilla content. Reading the bundle structure is the fastest path to understanding how Unturned organises its assets internally.

The Maps directory

The top-level Maps directory is distinct from Bundles/Maps. The Maps directory contains map source folders that the in-game editor reads directly; the Bundles/Maps directory contains compiled bundle versions of the same maps. Modders developing new maps work in the source format and place their work in the top-level Maps directory.

Maps location	What it contains
Maps/PEI/	Source files for the PEI map
Maps/Russia/	Source files for the Russia map
Maps/Washington/	Source files for the Washington map
Maps/Germany/	Source files for the Germany map
Maps/Yukon/	Source files for the Yukon map
Maps/<your map>/	Source files for your custom map

Custom maps placed in the top-level Maps directory are recognised by the in-game editor and can be loaded for testing. This is the standard development workflow for map authors.

The ExampleAssets directory

The ExampleAssets directory is one of the most important resources for new modders. Smartly Dressed Games ships example mods and asset definitions in this directory as a learning reference. Studying the examples is the fastest way to understand the conventions and file formats used in Unturned modding.

The example assets cover items, vehicles, environment objects, and several other content categories. Each example is a complete, working mod that demonstrates the structure required for that category of content.

The Modules directory

The Modules directory contains server modules and runtime extensions. Modders who develop server-side plugins read this directory to understand the module interface; players who run dedicated servers see modules installed here when they add server-side functionality.

The Unturned_Data and Unturned_Headless_Data directories

These two directories contain compiled Unity engine data for the client and the headless server respectively. They are technically modifiable but should not be modified in practice; any change is reverted by the next verification, and incorrect changes can prevent the game from launching.

Directory	Role
Unturned_Data/	Client engine data; required for normal launch
Unturned_Headless_Data/	Headless server engine data; required for dedicated server launch

Both directories are treated as read-only by every supported modding workflow.

The EasyAntiCheat directory

The EasyAntiCheat directory contains the Easy Anti-Cheat client files. These files are part of the anti-cheat system and must not be modified. Modifications to anti-cheat files can trigger account flags or bans; this is a real consequence to be aware of.

Critical warning

Never modify, delete, or replace files in the EasyAntiCheat directory. The anti-cheat system monitors its own files for tampering and reports anomalies to Valve. Tampering can result in game bans that affect your Steam account permanently.

Install folder versus user-data folder

A common confusion for new modders is the distinction between the install folder (covered in this article) and the user-data folder. They are separate directories with separate purposes.

The diagram above splits the two locations. The install folder, which lives under Steam's steamapps\common\Unturned directory, contains the game itself and is managed by Steam. The user-data folder, which lives under %AppData%\Unturned, contains your saves, your settings, and your logs and is managed by Windows on a per-user basis.

Pro tip

You can paste %AppData%\Unturned directly into File Explorer's address bar and press Enter to jump straight to the user-data folder. Windows expands the %AppData% environment variable automatically.

Side-by-side comparison

The differences between the install folder and the user-data folder show up in every aspect of mod development. The following table summarises the key distinctions.

Attribute	Install folder	User-data folder
Location	<library>\steamapps\common\Unturned	%AppData%\Unturned
Managed by	Steam	Windows on a per-user basis
Contents	Base game files	Saves, settings, logs, Workshop subscriptions
Modifiable	Mostly read-only; modifications get reverted	Modifiable; saves and settings live here
Affected by verification	Yes; verification restores to manifest state	No; verification leaves it alone
Affected by uninstall	Yes; uninstall removes it	Usually preserved; depends on uninstall flags
Shared across Windows users	Yes; one install per machine	No; one user-data folder per Windows user
Backed up by Steam Cloud	No	Selective; only files Smartly Dressed Games has enabled

The comparison table above is the canonical reference for the two locations. Modders refer to this distinction constantly during development because mod content can live in either location depending on how it interacts with the game.

Did you know?

The user-data folder's %AppData%\Unturned path expands to C:\Users\<your username>\AppData\Roaming\Unturned on a typical Windows installation. The Roaming portion of the path is a Windows convention; the directory roams with a domain user profile if your Windows account is part of an enterprise domain with roaming profiles. Most home users do not have roaming profiles, so the data stays on the local machine.

Pinning the install folder for future access

Because you will return to the Unturned install folder constantly during mod development, pinning it to Windows Quick access saves significant time.

1. Open the Unturned install folder using either method above
2. Click the address bar in File Explorer to highlight the current path
3. In the File Explorer left sidebar, right-click the parent folder name (or the path crumb)
4. Click Pin to Quick access

A new entry appears in the Quick access section of the sidebar. Clicking this entry opens the install folder in a single click.

Did you know?

Quick access entries are stored in your Windows user profile. They persist across reboots and synchronize across machines if you sign in with the same Microsoft account on both, depending on your sync settings.

Additional pinning targets

Beyond the install folder itself, several other directories are worth pinning for ongoing mod development. The following list is the set of locations most modders end up pinning over the course of a project.

Pinned target	Why it is worth pinning
Install folder root	Primary navigation point
Bundles/Maps/ inside the install folder	Reference for compiled map bundles
ExampleAssets/ inside the install folder	Learning reference for mod conventions
Maps/ inside the install folder	Custom map development location
%AppData%\Unturned\	User-data folder for settings and saves
%AppData%\Unturned\Logs\	Log files for troubleshooting
Your personal mod project directory (outside the install folder)	Your working copy
The Steam library folder root	Useful for managing other Steam games

The pinning list above is a productivity investment. Each pinned location saves a few seconds per navigation; across a year of modding, the cumulative time savings are substantial.

Advanced considerations

Several advanced points are worth noting for users who plan to manage multiple Unturned installations or to develop mods across multiple drives.

Multiple Steam library folders

If you have configured additional Steam library folders on other drives, you can move Unturned to a different folder through Right-click to Properties to Installed Files to Move install folder. After moving, the Browse local files shortcut and File Explorer paths both update automatically. The next article in this section covers Steam library folders in detail.

Symbolic links and junctions

Advanced users sometimes create symbolic links or junction points that make the install folder appear at a second location on disk. This is supported but should only be set up by users who fully understand NTFS filesystem behavior. Mod development tools do not require symbolic links and beginners should avoid them.

Permissions and shared machines

On a shared computer with multiple Windows user accounts, the install folder may be shared but the user-data folder is unique to each account. This means each user sees their own saves and settings, but they all share the same base game files.

Read-only and read-write zones

The install folder has an internal structure of read-only and read-write zones. Understanding which zones are which prevents accidental modifications that get reverted by verification.

Zone	Read-only or read-write	Reason
EasyAntiCheat/	Read-only	Anti-cheat integrity
Unturned.exe, Unturned_Headless.exe	Read-only	Game executable integrity
Unturned_Data/, Unturned_Headless_Data/	Read-only	Unity engine data integrity
Bundles/	Read-only	Compiled bundles managed by Steam
Maps/ (vanilla maps)	Read-only	Vanilla content managed by Steam
Maps/<your custom maps>/	Read-write	Modder content
Modules/<your modules>/	Read-write	Modder content
Workshop/	Managed by Steam	Workshop subscription downloads

The zone table above is the working reference for what can and cannot be modified. Custom content placed in read-write zones survives verification; modifications to read-only zones are reverted by the next verification.

FAQ

I clicked Browse local files and nothing happened. What is wrong?

This usually indicates that Steam has lost track of the install location, often because the install drive was disconnected. Reconnect the drive, restart Steam, and try again. If the problem persists, run a verification.

Can I rename the Unturned install folder?

No. Steam expects the folder name to match the game's internal name. Renaming the folder will cause Steam to report the game as uninstalled and trigger a redownload.

Where do I put custom maps for testing?

Custom maps go in the Maps subdirectory of the Unturned install folder. This is covered in detail in the mapping section of the knowledge base. The in-game editor reads the Maps folder directly and any custom map placed there appears in the editor's map list.

What is the difference between Bundles\Maps and the top-level Maps folder?

Bundles\Maps contains compiled Unity bundles for the base-game maps. The top-level Maps folder contains map source folders that the editor reads directly. You will work with the top-level Maps folder during map development.

Can I delete the Cloud folder to save space?

No. The Cloud folder is required for Steam Cloud synchronization. Deleting it does not save meaningful space and breaks cloud-saved content.

Can I move individual files inside the install folder?

Yes, in read-write zones. Files in the read-only zones will be restored by the next verification. The supported pattern is to keep custom mod work in dedicated subdirectories that do not conflict with manifest entries.

How do I find the install folder if Steam is uninstalled?

The install folder lives on disk independently of Steam. Use File Explorer to navigate to the path manually. The default location is C:\Program Files (x86)\Steam\steamapps\common\Unturned; on a machine with a separate library folder, the path uses a different drive and library name.

Can I open multiple File Explorer windows on the same install folder?

Yes. Each Browse local files click opens a new File Explorer window. This is useful for comparing two subdirectories side by side or for dragging files between locations.

Does the install folder change after a Steam update?

No, the location does not change. Individual files within the folder may change as a result of the update, but the folder itself remains at the same path.

What is the role of the StatusReports folder?

The StatusReports folder collects diagnostic files generated by the game when a crash occurs. The contents are useful when reporting bugs to Smartly Dressed Games. The official documentation at https://docs.smartlydressedgames.com/en/latest/about/getting-started.html describes the report format for users who want to include status reports in bug submissions.

Can I run two copies of Unturned from one install folder?

No. The Steam client supports launching a single copy of Unturned at a time. To run two independent copies (such as a client and a headless server), the headless executable in the same install folder is the supported path. The two executables share files but run as separate processes.

How do I find the install folder for a headless server install?

A headless-server install uses the same install folder as the client install. The two executables (Unturned.exe for the client and Unturned_Headless.exe for the headless server) live in the same folder. Steam does not maintain a separate install for the headless server.

Best practices

• Use Browse local files in Steam as your default method for opening the install folder
• Pin the folder to Quick access on the first visit
• Memorize the canonical install path for your machine
• Distinguish between the install folder and the user-data folder
• Treat the contents of EasyAntiCheat and *_Data directories as read-only
• Open File Explorer windows for both the install folder and the user-data folder during active modding sessions
• Keep custom mod work in dedicated subdirectories rather than mixed into vanilla folders
• Never rename the install folder
• Use the address bar for fast navigation to remembered paths
• Pin secondary locations such as Maps/ and Bundles/Maps/ for frequent access

Appendix A: install folder navigation cheat sheet

The following table is a quick reference for common navigation tasks. Each row maps a goal to the fastest path.

Goal	Fastest path
Open install folder from Steam	Right-click Unturned to Manage to Browse local files
Open install folder from File Explorer	Type the path into the address bar
Open user-data folder	Type %AppData%\Unturned in File Explorer address bar
Open Steam library folder root	Right-click any Steam game to Manage to Browse local files, then go up one level
Open the Logs folder	Type %AppData%\Unturned\Logs in File Explorer address bar
Open the Maps source folder	Open install folder, click Maps subdirectory
Open the Bundles folder	Open install folder, click Bundles subdirectory
Open the EasyAntiCheat folder	Open install folder, click EasyAntiCheat subdirectory (read-only)
Open the Steam logs folder	Open Steam install folder, click logs subdirectory
Open the AppData root	Type %AppData% in File Explorer address bar

The cheat sheet above is worth printing or pinning as a quick reference for the first few weeks of active modding. The paths become automatic after about a month of regular use.

Appendix B: directory ownership reference

The following table documents which entity owns each subdirectory of the install folder. Ownership determines whether a directory survives verification and whether modifications are supported.

Directory	Ownership	Survives verification
Bundles/	Smartly Dressed Games	Yes; modifications reverted
Cloud/	Steam	Yes; managed by Steam Cloud
EasyAntiCheat/	Easy Anti-Cheat	Yes; modifications reverted; tampering risks ban
EngineConfig/	Smartly Dressed Games	Yes; modifications reverted
ExampleAssets/	Smartly Dressed Games	Yes; modifications reverted
Extras/	Smartly Dressed Games	Yes; modifications reverted
Localization/	Smartly Dressed Games	Yes; modifications reverted
Maps/<vanilla maps>/	Smartly Dressed Games	Yes; modifications reverted
Maps/<custom maps>/	The modder	No; modder retains custom content
Modules/<vanilla modules>/	Smartly Dressed Games	Yes; modifications reverted
Modules/<custom modules>/	The modder	No; modder retains custom modules
Sandbox/	Smartly Dressed Games	Yes; modifications reverted
Server/	Smartly Dressed Games	Yes; modifications reverted
StatusReports/	The game runtime	No; persistent diagnostic data
Unturned_Data/	Smartly Dressed Games and Unity	Yes; modifications reverted
Unturned_Headless_Data/	Smartly Dressed Games and Unity	Yes; modifications reverted

The ownership table above is the canonical reference for what survives verification. Modders structure their custom work to live exclusively in modder-owned zones to prevent loss during routine maintenance.

Appendix C: install folder size reference

The install folder has a characteristic size profile. The following table shows the approximate disk footprint of each top-level subdirectory.

Subdirectory	Approximate size	Share of total
Bundles/	3 to 4 GB	About 60 percent
Maps/	800 MB to 1 GB	About 15 percent
Unturned_Data/	400 to 600 MB	About 9 percent
Unturned_Headless_Data/	300 to 500 MB	About 7 percent
ExampleAssets/	200 to 300 MB	About 4 percent
Modules/	100 to 200 MB	About 3 percent
EasyAntiCheat/	50 to 100 MB	About 1 percent
Other subdirectories	Less than 100 MB total	About 1 percent

The size table above shows where the disk footprint actually lives. The Bundles directory dominates because compiled Unity bundles are large; the Maps directory is the second-largest because the official maps include detailed terrain and asset data.

Did you know?

Adding custom maps and modules can increase the install folder size significantly. A modder working on three large custom maps may have an install folder twice the size of a vanilla install, with the custom content living in modder-owned subdirectories that do not appear in the table above.

Appendix D: install folder and Smartly Dressed Games documentation

The Smartly Dressed Games official documentation at https://docs.smartlydressedgames.com/en/latest/about/getting-started.html provides additional reference material for the install folder structure. The official documentation is the authoritative source for any topic on which it disagrees with this article.

The official documentation covers:

• Reference for the asset file format used in Bundles/Assets/
• Reference for the map source format used in Maps/
• Reference for the module API used in Modules/
• Guidance on publishing custom content through the Steam Workshop
• Reference for the example assets in ExampleAssets/

Bookmark the official documentation alongside this knowledge base. The two resources are designed to be read together; the knowledge base covers practical workflow patterns and the official documentation covers technical specifications.

Appendix E: install folder access patterns by modder type

Different categories of modders interact with the install folder in different patterns. The following table maps modder types to their primary access patterns.

Modder type	Primary subdirectories visited	Read or write
Map maker	Maps/, Bundles/Maps/, ExampleAssets/Maps/	Mostly write to Maps/; read from others
Item modder	ExampleAssets/Items/, Bundles/Assets/	Mostly read; write to dedicated mod folder
Vehicle modder	ExampleAssets/Vehicles/, Bundles/Assets/	Mostly read; write to dedicated mod folder
Server module developer	Modules/, ExampleAssets/Modules/	Read examples; write own modules
Localization contributor	Localization/, Bundles/Localization/	Read for reference; write to own localization folder
Workshop curator	Workshop/	Mostly read; managed by Steam
Bug reporter	StatusReports/, %AppData%\Unturned\Logs/	Read only; copy diagnostic files for reports
Server administrator	Server/, Modules/	Configure server; install modules

The access pattern table above is the working reference for understanding which parts of the install folder matter most to different modder types. New modders identify their primary type and use the table to focus their initial exploration of the install folder.

Appendix F: install folder mental model

The install folder can be thought of as a layered structure with three tiers: the executable layer, the data layer, and the modder layer.

                                The Unturned install folder mental model


                              +--------------------------------------+
                              |                                      |
                              |        EXECUTABLE LAYER              |
                              |        Unturned.exe                  |
                              |        Unturned_Headless.exe         |
                              |        EasyAntiCheat client          |
                              |                                      |
                              +--------------------------------------+
                              |                                      |
                              |        DATA LAYER                    |
                              |        Bundles                       |
                              |        Maps (vanilla)                |
                              |        ExampleAssets                 |
                              |        Localization                  |
                              |        Unturned_Data                 |
                              |        Unturned_Headless_Data        |
                              |        Modules (vanilla)             |
                              |                                      |
                              +--------------------------------------+
                              |                                      |
                              |        MODDER LAYER                  |
                              |        Maps (your custom maps)       |
                              |        Modules (your custom modules) |
                              |        Workshop (subscriptions)      |
                              |                                      |
                              +--------------------------------------+

The three-layer model above is a useful way to think about the install folder. The executable layer is the smallest and most stable. The data layer is the largest and is managed by Steam. The modder layer is where custom work lives. Each layer has different ownership, different modification rules, and different verification behaviour.

Layer	Ownership	Modification policy
Executable	Smartly Dressed Games and Easy Anti-Cheat	Read-only; tampering risks bans
Data	Smartly Dressed Games	Read-only; modifications reverted by verification
Modder	The modder	Read-write; modder retains custom content

The layer table above summarises the three-tier mental model. Holding this model in mind clarifies every decision about where to put custom work and what to expect from verification.

Appendix G: glossary of install folder terms

The following terms appear throughout this article and across the knowledge base. The working definitions provided here align with Smartly Dressed Games' official documentation.

• Asset bundle — A compiled Unity file containing one or more game assets. Vanilla bundles live in Bundles/.
• Install folder — The directory on disk containing the base game files. Lives under <library>\steamapps\common\Unturned.
• Library folder — A directory anywhere on disk that Steam treats as a valid install destination. Each library folder has its own steamapps\common subdirectory.
• Modder layer — The portion of the install folder where modder-owned content lives. Survives verification because the manifest does not reference these files.
• Quick access — Windows feature for pinning frequently-visited folders to the File Explorer sidebar.
• Read-only zone — A subdirectory in which modifications are reverted by the next verification. Most of the install folder is a read-only zone.
• Read-write zone — A subdirectory in which modifications survive verification. Custom mod content is placed here.
• User-data folder — The per-user directory at %AppData%\Unturned containing settings, saves, and logs. Distinct from the install folder.

The glossary above is the vocabulary that the rest of the install pipeline articles build on.

Appendix H: install folder navigation by use case

The right way to open the install folder depends on what you intend to do once you arrive. The following table maps common modder use cases to the recommended starting point.

Use case	Recommended starting point	Why
Quick visual inspection	Steam Browse local files	Fastest entry; no commitment required
Active map development	File Explorer pinned to Maps/ subdirectory	Direct entry to the working directory
Module development	File Explorer pinned to Modules/ subdirectory	Direct entry to the working directory
Reading vanilla bundle structure	File Explorer pinned to Bundles/ subdirectory	Direct entry to reference content
Studying example mods	File Explorer pinned to ExampleAssets/ subdirectory	Direct entry to learning material
Diagnosing a crash	Steam Browse local files, then go to StatusReports/	Crash reports live here
Configuring a server	File Explorer pinned to Server/ subdirectory	Direct entry to server templates
Copying files to share	Steam Browse local files, then select and copy	Copying preserves file structure
Verifying file existence	Address bar with full path	Fastest way to check whether a known file is present
Comparing two installs	Two File Explorer windows side by side	Visual diff is fastest for spotting differences

The use case table above is the working guide for opening the install folder with intent. Picking the right starting point saves time across every modding session.

Appendix I: installation folder permissions reference

The Windows file permissions on the Unturned install folder follow standard Windows conventions. The following table documents the expected permissions on a default Windows install.

Path	Owner	Default permissions
C:\Program Files (x86)\Steam	TrustedInstaller	Read and execute for users; full control for administrators
C:\Program Files (x86)\Steam\steamapps\common\Unturned	TrustedInstaller	Read and execute for users; full control for administrators
C:\Program Files (x86)\Steam\steamapps\common\Unturned\*	TrustedInstaller	Read and execute for users; full control for administrators
Custom library folder root (e.g., D:\SteamLibrary)	Current user	Full control for the user who created it
Custom library folder Unturned subfolder	Current user	Full control for the user who created it
%AppData%\Unturned	Current user	Full control for the current user

The permissions reference above is the expected baseline. If your install folder has different permissions, it may have been modified by a previous administrator or by security software. A verification that reports permission errors is a signal to check the actual permissions against this baseline.

Common mistake

Some online tutorials suggest running Steam as administrator to work around permission issues. This is usually not the right answer. The correct fix is to repair the permissions on the install folder using Windows' built-in security tools. Running Steam as administrator can cause other problems and is not the supported configuration.

Repairing permissions

If the permissions on the install folder have been modified incorrectly, the following sequence restores them to the expected baseline:

1. Right-click the Steam folder in File Explorer
2. Click Properties
3. Click the Security tab
4. Click Advanced
5. Click Change next to the Owner field
6. Type your username and click Check Names
7. Click OK
8. Check the box labelled "Replace owner on subcontainers and objects"
9. Click Apply and then OK
10. Back in the Security tab, click Edit
11. Grant your user account full control
12. Click Apply and then OK

The sequence above is the supported way to repair permissions on the install folder. Most users will never need to perform this sequence; it is documented here for completeness.

Appendix J: install folder under non-standard configurations

Several non-standard configurations affect where the install folder lives. The following table documents each configuration and the expected install folder location.

Configuration	Install folder location
Default Windows, default Steam install	C:\Program Files (x86)\Steam\steamapps\common\Unturned
Steam installed to non-default location	<Steam install path>\steamapps\common\Unturned
Secondary library folder on D drive	D:\SteamLibrary\steamapps\common\Unturned
Custom library folder name	<drive>\<library name>\steamapps\common\Unturned
External USB drive library	<external drive>\SteamLibrary\steamapps\common\Unturned
Steam on Windows under non-default Program Files redirect	Wherever Windows redirects the path
Steam installed via a portable launcher	Path defined by the launcher; typically a USB drive
Steam on a multi-user machine	Path is shared; same location for every user

The configuration table above covers the common variations. In every case, the pattern \steamapps\common\Unturned holds; only the prefix differs.

Cross-references

• How to Install Unturned — the install procedure that creates the folder discussed here
• How to Verify Unturned Game Files — verification interacts with the install folder
• Where Steam Installs Games by Default — context for the default install folder location
• How to Launch Unturned for the First Time — first launch reads from this folder

Appendix K: install folder backup strategy

Modders working on long-term projects benefit from a backup strategy that protects custom work in the install folder. The following practices describe a sensible backup approach.

What to back up

Back up the modder-owned subdirectories rather than the entire install folder. The vanilla content can always be re-downloaded from Steam; the custom content cannot.

Backup target	Contents	Backup frequency
Custom maps in Maps/<your maps>/	Map source files	After every meaningful editing session
Custom modules in Modules/<your modules>/	Module source and built artefacts	After every meaningful coding session
Custom assets in dedicated mod directories	Mod source files	After every meaningful editing session
Configuration overrides	Custom Server config, launch options	After any configuration change

The backup target table above shows the recommended granularity. Full install folder backups are wasteful; targeted backups of custom work are efficient and easy to restore.

Where to back up

Choose a backup destination that is independent of the install drive. The point of backup is recovery from a drive failure; a backup on the same drive as the original does not protect against drive failure.

Backup destination	Suitability
Cloud storage (Google Drive, Dropbox, OneDrive)	Excellent for active work; automatic sync is a bonus
External USB SSD	Good for periodic backups; manual process
Secondary internal drive	Good for periodic backups; protects against single-drive failure
Same drive as install	Not recommended; does not protect against drive failure
Network-attached storage	Good for shared projects; slower than local

The destination table above is the practical reference. Most active modders use a cloud storage provider for the convenience of automatic sync; periodic external backups complement this for the rare case that cloud sync fails.

Restoring from backup

A restore from backup is a copy operation from the backup destination back into the install folder. The restore should target the same modder-owned subdirectories from which the backup was taken. The restore does not need to involve Steam; it is a pure filesystem operation.

After a restore, run a verification on the install folder. The verification confirms that the vanilla content is still in the expected state and that the restored modder content lives in the expected modder-owned zones.

Pro tip

Maintain a written description of your backup strategy in a text file alongside the backup. The description should list which directories are backed up, how often, and where they are backed up to. A future-you reading this description after a drive failure will appreciate the clarity.

Document history

Version	Date	Author	Notes
1.0	2024-09-16	57 Studios	Initial publication
1.1	2024-12-08	57 Studios	Added subdirectory reference table and pinning instructions
1.2	2025-04-02	57 Studios	Added install folder versus user-data folder comparison
2.0	2026-05-17	57 Studios	Major expansion. Added three-layer mental model, directory ownership reference, modder type access patterns, and glossary. Expanded FAQ from 5 to 12 questions.

Next steps

With the install folder located and pinned, proceed to Where Steam Installs Games by Default to understand the rules that determined this location and how to add additional library folders.