How to Install Unturned Mods

A player wants to add mods to Unturned™. Some mods are listed on the Steam Workshop and install with a single subscribe click. Other mods are distributed as direct downloads from a creator's Discord, a Tebex storefront, or a server's website and must be installed manually. Once installed, mods need to be verified in-game, and any mod intended for multiplayer use must match between the client and the server.

This article documents the complete install workflow for both Workshop and non-Workshop mods on Windows, macOS, and Linux. It covers where mods live on disk, how to verify a mod has loaded, how to configure a server to load mods that clients are running, how to uninstall a mod cleanly, and what to do when a mod refuses to appear in the in-game menu. The workflows are current to the 2026 build of Unturned™ and reflect the changes Smartly Dressed Games has made to the Workshop integration since the earlier modding documentation was written.

Prerequisites

• Unturned™ installed and launched at least once. The first launch creates the folders that mods install into.
• A Steam account in good standing. The Workshop subscription model is tied to the Steam account that owns the game.
• For manual installs, File Explorer (Windows), Finder (macOS), or a terminal with a file manager (Linux).
• For server installs, administrative access to the server's installation folder and the Commands.dat or Config.json configuration file.
• An internet connection during the initial Workshop download. Mods can be played offline after the download completes.

What you'll learn

• How the Steam Workshop subscription model works for Unturned™ mods.
• Where Workshop mods install on disk for each operating system.
• How to install a non-Workshop mod manually into the game's Bundles folder.
• How to verify in-game that a mod has loaded.
• How to configure a server to load the same mods clients are subscribed to.
• How server-side and client-side mods differ and what happens on a mismatch.
• How to remove or disable a mod without uninstalling the game.
• How to resolve the principal failure modes when a mod does not appear after install.

Background: how Steam Workshop integration works for Unturned

The Steam Workshop is the primary distribution channel for Unturned™ mods. Smartly Dressed Games integrates with the Workshop through Steam's standard API, which means the subscription, download, and update workflow is the same as for any other Steam Workshop-enabled game. A player subscribes to a Workshop item, Steam downloads the item in the background, and the game reads the downloaded files from a known cache location on every launch.

The Workshop integration handles three operations transparently from the player's perspective:

1. Subscription persistence. Subscriptions are stored on Steam's servers against the player's Steam account. The same subscriptions are available on every machine the player signs in to.
2. Background download. When a player subscribes to an item, Steam queues the download. The download happens in the background through the Steam client, not through the game.
3. Automatic update. When a creator updates a Workshop item, Steam detects the update and re-downloads the changed files on the next Steam client startup.

Players who want to confirm what is downloaded can inspect the Workshop content folder directly. The folder location varies by operating system and Steam installation, and the per-OS paths are documented in the following section.

The sequence above models the complete subscribe-to-load lifecycle. Each arrow is an operation that can fail and produce a recognisable symptom: a subscription that does not register, a download that does not start, a download that does not complete, a load that the game does not recognise. The diagnostic section later in this article maps each symptom to the operation that failed.

Where mods install on disk

The Steam Workshop downloads every subscribed item into a per-game content folder. The folder name uses the Steam application ID for the game; for Unturned™, the application ID is 304930. The full path varies by operating system and by which drive Steam is installed on.

Per-operating-system disk locations

OS	Default Workshop content path
Windows	C:\Program Files (x86)\Steam\steamapps\workshop\content\304930\
macOS	~/Library/Application Support/Steam/steamapps/workshop/content/304930/
Linux	~/.steam/steam/steamapps/workshop/content/304930/
Steam Deck (SteamOS)	~/.steam/steam/steamapps/workshop/content/304930/

Each subscribed mod lives in a subfolder named with the mod's Steam Workshop item ID — a numeric ID assigned by Steam when the creator first uploaded the mod. The contents of the subfolder vary by mod type but always include at minimum the mod's master bundle file and any asset definitions.

Manual install location

Mods that are not distributed through the Steam Workshop are installed manually into the game's Bundles/Workshop folder. The game scans this folder on every launch and loads any mods present, in addition to the Workshop-downloaded mods.

OS	Default manual mod install path
Windows	C:\Program Files (x86)\Steam\steamapps\common\Unturned\Bundles\Workshop\
macOS	~/Library/Application Support/Steam/steamapps/common/Unturned/Bundles/Workshop/
Linux	~/.steam/steam/steamapps/common/Unturned/Bundles/Workshop/

The Workshop subfolder may not exist before any manual mods are installed. Creating it is part of the manual install procedure documented in a later section.

Disk layout of a typical mod folder

The diagram below shows the file structure inside an example mod folder. Specific file names vary by mod type (vehicle, weapon, map, item, asset bundle), but the top-level layout is consistent across the Unturned™ modding ecosystem.

3216847291/                            <-- Workshop item ID
├── English.dat                        <-- localization for the mod
├── master.dat                         <-- mod manifest and metadata
├── master.unity3d                     <-- compiled Unity asset bundle
├── Items/                             <-- per-item asset definitions
│   ├── Item_1234/
│   │   ├── English.dat
│   │   ├── Asset.dat
│   │   └── Item_1234.unity3d
│   └── Item_1235/
│       ├── English.dat
│       ├── Asset.dat
│       └── Item_1235.unity3d
└── Vehicles/
    └── Vehicle_5678/
        ├── English.dat
        ├── Asset.dat
        └── Vehicle_5678.unity3d

The layout is documented here so that a player troubleshooting a missing mod can confirm whether the files are present on disk. If the Workshop item ID folder is empty or only contains partial files, Steam has not completed the download yet and the mod will not load.

Did you know?

The Steam application ID for Unturned™ is 304930 and has remained constant since the game's release. The application ID appears in the Workshop content path, in the Steam store URL (store.steampowered.com/app/304930/Unturned/), and in the dedicated server's SteamCMD install command (app_update 304930). A player who knows the application ID can reliably locate the Workshop folder on any Steam installation regardless of which drive Steam is on.

Procedure 1: install a mod from the Steam Workshop

The Steam Workshop subscription is the recommended install path for any mod that is published on the Workshop. The subscription is persistent across machines, the download is managed by Steam, and updates are delivered automatically.

1. Open the Steam client and sign in with the account that owns Unturned™.
2. Open the Steam library and right-click Unturned™.
3. Select "Browse the Workshop" from the context menu. The Steam Workshop page for Unturned™ opens in the Steam overlay or in the default browser.
4. Search for the mod by name or browse the featured items.
5. Click the mod's title to open its detail page.
6. Click the green "Subscribe" button. The button changes to a checkmark indicating "Subscribed."
7. Allow Steam to download the mod. The download status appears in the Downloads tab of the Steam client (lower-right corner).
8. Wait for the download to complete. The download size varies from a few hundred kilobytes for small item mods to several gigabytes for large map mods.
9. Launch Unturned™ from the Steam library.
10. From the main menu, select "Workshop" to open the in-game Workshop browser.
11. Confirm the mod appears in the list of installed mods.

The subscription persists until the player explicitly unsubscribes. Steam will re-download the mod's files on any machine the player signs in to.

Pro tip

Subscribe to mods through the Steam client window rather than the in-game Workshop browser when possible. The in-game browser triggers the same subscription operation, but the Steam client window shows the download progress more clearly and lets the player continue browsing while the download runs in the background. The in-game browser is convenient mid-game but provides less feedback on the download state.

Procedure 2: install a non-Workshop mod manually

Some mods are not published on the Steam Workshop. Reasons include in-development builds, private mods distributed within a small community, mods that exceed the Workshop's file size limit, and mods that the creator has chosen to distribute through other channels such as a Tebex storefront or a Discord server. These mods require a manual install into the game's Bundles/Workshop folder.

1. Close Unturned™ if it is running.
2. Download the mod file from the source the creator has provided. The download is typically a .zip or .rar archive.
3. Extract the archive to a temporary location (e.g., the Downloads folder).
4. Confirm the extracted folder contains at minimum a master.dat file and a master.unity3d file (or equivalent files for the specific mod type).
5. Open File Explorer (Windows), Finder (macOS), or a terminal-based file manager (Linux).
6. Navigate to the manual install path documented earlier: <Steam>/steamapps/common/Unturned/Bundles/Workshop/.
7. If the Workshop subfolder does not exist, create it.
8. Copy the extracted mod folder into the Workshop folder. Each mod should sit in its own subfolder.
9. Launch Unturned™.
10. From the main menu, select "Workshop" to confirm the mod is listed.
11. If the mod is not listed, see the diagnostic section later in this article.

The manual install procedure produces the same result as the Workshop subscription procedure: the mod is loaded on the next launch and appears in the in-game Workshop menu. The only differences are that updates must be applied manually (re-download and replace the folder) and the mod is not synchronized to other machines.

Common mistake

Extracting a manual-install mod with the archive's top-level folder nested inside another folder. The Bundles/Workshop folder expects each mod to occupy a single subfolder containing the mod files directly. If the archive extracts to Workshop/MyMod/MyMod/master.dat, the game scans Workshop/MyMod/ and finds no master.dat in the expected location. The fix is to move the contents of the inner folder up one level so the structure becomes Workshop/MyMod/master.dat.

Procedure 3: configure a server to load mods

A server that is intended to use mods must load the same Workshop items the connecting clients have subscribed to. Server-side configuration uses the Workshop_Download_ID directive in the server's commands file, which instructs the server to download the listed Workshop items at startup.

The procedure assumes the server has already been set up per the Self-Hosting section's hardware and network guidance. This procedure covers only the mod-loading configuration.

1. Stop the Unturned™ dedicated server.
2. Open the server's Servers/<InstanceName>/Server/Commands.dat file in a text editor.
3. Add a Workshop_Download_ID line for each Workshop item the server should load. The format is Workshop_Download_ID <ItemID> where <ItemID> is the numeric Workshop item ID.
4. Save the Commands.dat file.
5. Start the dedicated server.
6. Observe the server console output. The server will report each Workshop item as it downloads, in the form Installed workshop item <ItemID>.
7. Wait for all downloads to complete before allowing clients to connect.
8. Confirm the server appears with the correct mods in the in-game server browser by filtering for the modded server name.
9. Verify a client can join the server. The client's Steam Workshop subscriptions are checked against the server's Workshop downloads on connect; mismatched mod versions produce a connection error.

The Workshop item IDs that the server should download are the same numeric IDs documented in the Workshop content folder layout earlier in this article. The IDs can be found in the URL of each Workshop item's Steam Community page.

Did you know?

Smartly Dressed Games' dedicated server tooling supports two install paths for server-side mods: the Workshop_Download_ID directive in Commands.dat, which downloads from the Steam Workshop on each server startup, and a manual install into the server's Bundles/Workshop folder, identical to the client manual install procedure. The Workshop_Download_ID approach is preferred for production servers because it keeps the server's mod versions aligned with the Workshop and applies updates automatically.

Server-side versus client-side mods

Unturned™ mods fall into three categories with respect to which side (client, server, both) must have the mod loaded for the mod to work. The category determines what happens on a mismatch between the client and the server.

Category	Loaded on client?	Loaded on server?	Symptom of mismatch
Client-side (cosmetic)	Yes	No	Other players do not see the cosmetic. The cosmetic-using client sees it normally.
Server-side (gameplay)	No	Yes	Client can join, but client-side previews of server-loaded content (e.g., item models) may not render.
Both (full content)	Yes	Yes	Client cannot join; receives "missing workshop item" error on connect.
Map mod	Yes	Yes	Server cannot start if map is missing; client cannot join if map is missing.
Localization mod	Yes	No	Client sees translated strings; other clients see original strings.
Asset-replacement mod	Yes	No (usually)	Client sees replaced assets locally; other clients see originals.

The category for any specific mod is documented by the creator in the mod's Workshop description. When in doubt, subscribe on the client and add the Workshop_Download_ID on the server. A mod loaded on both sides will always work; a mod loaded on only one side may produce one of the symptoms in the table.

Common mistake

Assuming all mods are client-side because the player's own client recognises the mod. Many mod types (vehicles, weapons, items, full maps) are server-authoritative: the server must load the mod for clients to interact with it on that server. The mod's Workshop description specifies the server-side requirement; reading the description before joining a modded server prevents the "missing workshop item" error.

Procedure 4: verify a mod has loaded

After install, verification confirms the mod is recognised by the game. Verification has three levels: file-level (the files exist on disk), game-level (the in-game Workshop menu lists the mod), and gameplay-level (the mod's content is accessible during play).

Step 1: file-level verification

Navigate to the Workshop content path for the operating system in use and confirm the mod's Workshop item ID folder exists. Open the folder and confirm it contains a master.dat file and any .unity3d files referenced by the mod.

If the folder is empty or missing, the Steam download has not completed. Open the Steam client's Downloads tab and verify the download is in progress, paused, or queued.

Step 2: game-level verification

1. Launch Unturned™.
2. From the main menu, select "Workshop."
3. Browse the "Installed" tab.
4. Confirm the mod appears in the list with its name and thumbnail.

If the mod does not appear in the in-game Workshop menu despite the files being present on disk, the game has rejected the mod during load. The most common reasons are version incompatibility (the mod was built for a different game version) and a corrupted master file. See the diagnostic section below.

Step 3: gameplay-level verification

1. Start a singleplayer session on a map the mod is compatible with.
2. Locate the mod's content in the game. For an item mod, spawn the item via the command console. For a vehicle mod, find the vehicle on the map. For a map mod, the map should be selectable in the new-game menu.
3. Interact with the content to confirm it functions as the creator documented.

Gameplay-level verification is the final confirmation. A mod that passes file-level and game-level verification but fails gameplay-level verification typically has a bug in the mod itself; report it to the creator.

Diagnostic flowchart

When a mod does not appear in the in-game Workshop menu after subscribing or manual-installing, the diagnostic flowchart below narrows the cause to one of the principal failure modes.

The flowchart resolves the principal mod-loading failure modes. For mod conflicts that occur even after the flowchart has been worked through, see Mod Not Loading for general loading failures and GUID Conflicts Between Mods for the specific case where two mods declare conflicting asset GUIDs.

Common install failure modes

Symptom	Most likely cause	Resolution
Mod not in in-game menu, files not on disk	Steam download incomplete	Wait for download or re-queue
Mod not in in-game menu, files on disk	Game version mismatch	Wait for mod update or update game
Mod in menu but content missing in-game	Mod has been disabled in menu	Re-enable in the in-game Workshop menu
"Missing workshop item" error on server join	Server-side mod not subscribed on client	Subscribe to the mod listed in the error
Manual mod not detected	Folder layout incorrect	Move master.dat to the top of the mod folder
Workshop item shows red error on Steam page	Item removed by creator or Steam	No fix; find an alternate mod
Workshop subscription does not persist	Steam offline mode	Sign in to Steam online before subscribing
Workshop content folder missing	Game never launched	Launch the game once to create the folders
Mod loads but causes game crash	Mod incompatible with another mod	Unsubscribe other mods one at a time
Server downloads mod but clients still error	Server mod version older than client mod version	Restart server to re-download

Procedure 5: remove or disable a mod

A mod can be removed entirely by unsubscribing (Workshop) or deleting the folder (manual install), or disabled temporarily without removing the files.

Remove a Workshop mod

1. Open the Steam Workshop page for the mod.
2. Click the green checkmark labeled "Subscribed" — the button toggles to "Subscribe."
3. Wait for Steam to delete the mod folder. The deletion happens during the next Steam client startup or when Steam next syncs Workshop subscriptions.
4. Launch Unturned™ and confirm the mod no longer appears in the in-game Workshop menu.

Remove a manually installed mod

1. Close Unturned™.
2. Navigate to <Steam>/steamapps/common/Unturned/Bundles/Workshop/.
3. Delete the mod's folder.
4. Empty the Recycle Bin to free disk space.
5. Launch Unturned™ and confirm the mod no longer appears.

Disable a mod without removing the files

The in-game Workshop menu includes per-mod enable/disable toggles that allow a mod to remain installed but skipped at load time.

1. Launch Unturned™.
2. From the main menu, select "Workshop."
3. Open the "Installed" tab.
4. Locate the mod in the list.
5. Toggle the mod's enable state to "Disabled."
6. Restart Unturned™ for the change to take effect on the next launch.

Disabling is preferred to removal for mods the player wants to keep installed but skip temporarily — for example, when joining a vanilla server that does not accept any modded content.

Procedure 6: force re-download of a Workshop mod

When a Workshop mod's files appear corrupted or partial, forcing Steam to re-download the mod resolves the issue in most cases.

1. Close Unturned™ if running.
2. Open the Steam client.
3. Right-click Unturned™ in the library and select "Properties."
4. Open the "Installed Files" tab.
5. Click "Verify integrity of game files" — this verifies the game's files but does not re-download Workshop mods.
6. To re-download a specific Workshop mod, open the Workshop content folder at <Steam>/steamapps/workshop/content/304930/<ItemID>/ and delete the mod's folder.
7. Restart the Steam client. Steam detects the missing folder and re-queues the download.
8. Wait for the download to complete in the Steam client's Downloads tab.
9. Launch Unturned™ and confirm the mod is loaded.

The force re-download procedure is also useful when a mod has been updated by the creator but Steam has not detected the update — though Steam normally detects updates automatically on the next client startup.

Procedure 7: install mods on a hosted server

Players using a hosted server provider (rather than self-hosting on their own hardware) follow a different mod install workflow because the provider's control panel manages the server's files. The general workflow is:

1. Log in to the hosting provider's control panel.
2. Stop the server through the control panel.
3. Locate the Workshop configuration or mod manager in the control panel — most providers expose a UI for adding Workshop item IDs.
4. Add each Workshop item ID the server should load.
5. Save the configuration.
6. Start the server. The control panel typically streams the server console output, which will show the Workshop downloads completing.
7. Confirm clients can join with the same mods subscribed.

The control panel-based install path is functionally equivalent to editing Commands.dat directly; the control panel writes the same directive to the same file. Players who self-host on their own hardware should follow Procedure 3 above; the Self-Hosting section covers the underlying server infrastructure.

Pro tip

Hosting providers vary in how quickly they apply Workshop configuration changes. Some apply changes immediately; others require a full server restart. After saving a configuration change, watch the server console output for the Workshop download lines. If the lines do not appear, the configuration change has not been applied and a manual restart through the control panel is needed.

Multiple installs of Unturned and Workshop folder location

Players who have moved Unturned™ to a non-default Steam library folder (a secondary drive, for instance) will find the Workshop content in a different path than the default. Steam maintains library folders independently, and the Workshop content for each game lives alongside the game itself.

To locate the active Workshop content folder:

1. Open the Steam client.
2. Open Settings → Storage.
3. The list of library folders appears, with Unturned™ assigned to one of them.
4. The Workshop content for Unturned™ lives at <LibraryFolder>/steamapps/workshop/content/304930/.

The default library folder is at C:\Program Files (x86)\Steam on Windows. Additional library folders can be on any drive — many players install Steam games on a separate SSD for performance.

Cross-platform considerations

Windows

Windows is the principal platform for Unturned™ modding because Unity's modding workflow (documented in Unity Won't Open My Project) is best supported on Windows. Workshop subscriptions work normally on Windows; manual installs use File Explorer.

macOS

The macOS build of Unturned™ supports the Steam Workshop on the same subscription model as the Windows build. Manual installs use Finder. Some Unturned™ mods that include native plugin DLLs will not work on macOS because the DLLs are Windows-specific; the mod's creator documents platform support in the Workshop description.

Linux and Steam Deck

The Linux build of Unturned™ runs through Steam Play (Proton) for the same reason as macOS: the game targets Windows natively. Workshop subscriptions work through Steam Play, and the Workshop content folder is at the Linux path documented in the per-OS table. Steam Deck (which runs SteamOS, a Linux distribution) uses the same path.

Native Linux support for Unturned™ depends on the specific Steam Play / Proton version in use. Smartly Dressed Games' official platform support statements are on the Unturned™ Steam store page.

Performance considerations

A heavily modded Unturned™ install can have many gigabytes of Workshop content and hundreds of individual mod folders. The principal performance effects are:

• Game launch time. Every installed mod is scanned and loaded on launch. A player with many subscribed mods will experience a longer load time than a vanilla install.
• Memory use. Each loaded mod's assets occupy memory. A high subscription count can push memory use above what the player's machine can comfortably handle.
• Disk space. Large map mods can occupy several gigabytes each. The Workshop content folder's total size grows linearly with subscription count.
• Update check time. On Steam client startup, Steam checks for updates to every subscribed Workshop item. A high subscription count produces longer update checks.

Players who notice performance issues should review their subscription list and unsubscribe from mods they no longer use. The in-game Workshop menu's enable/disable toggle is an alternative to unsubscribing: disabled mods skip the load step on game launch, reducing launch time without deleting the files.

Subscription count	Approx. additional launch time	Approx. disk space
0 to 10 mods	Negligible	Under 500 MB
10 to 50 mods	5 to 15 seconds	500 MB to 5 GB
50 to 200 mods	15 to 60 seconds	5 GB to 20 GB
200+ mods	60+ seconds	20+ GB

The numbers above are typical ranges for player machines; actual times depend on disk speed (NVMe SSD versus SATA SSD versus HDD), CPU, and the specific mods subscribed. Mods that include large .unity3d asset bundles take longer to load than mods that contain only .dat definition files.

Mod conflict resolution

When two or more mods are subscribed but produce visible errors in-game — items with the wrong icons, crashes during specific actions, missing models, or duplicate UI elements — the mods are conflicting. The general resolution is to isolate the conflicting mod by disabling subscriptions one at a time.

The full mod-conflict diagnostic workflow is documented in two dedicated articles:

• Mod Not Loading — when a mod loads on disk but does not appear or function in-game.
• GUID Conflicts Between Mods — when two mods declare the same asset GUID and the game accepts only one.

The shorthand approach when neither dedicated article has been read:

1. Disable all mods through the in-game Workshop menu.
2. Restart the game and confirm the conflict no longer occurs.
3. Enable mods one at a time, restarting between each, until the conflict re-appears.
4. The most recently enabled mod is the conflicting mod (or one of two — combine with the previously enabled mod to confirm).

The disable-one-at-a-time approach is slow for large subscription lists but reliable. Disable-half-at-a-time (binary search) is faster: disable half the mods, test, and narrow the conflicting mod to one half on each iteration.

Steam Workshop content rules and creator agreements

The Steam Workshop has terms that apply to both creators and subscribers. Players installing mods should be aware that:

• The Workshop subscription is governed by the Steam Subscriber Agreement and the Steamworks Workshop documentation.
• Mods are submitted by community creators; Smartly Dressed Games does not produce or endorse every mod.
• Mods can be removed from the Workshop by the creator or by Steam. If a subscribed mod is removed, the local files remain until Steam syncs and removes them.
• Some mods may include scripted content. Players are encouraged to install mods from creators with positive ratings and an established presence in the Unturned™ community.

The full Smartly Dressed Games modding documentation is at the official Unturned modding docs. The official docs cover the creator side of the workflow — how to build, package, and submit mods to the Workshop. The current article covers the subscriber side.

Did you know?

The Steam Workshop has supported Unturned™ mods since well before the game's full release. The Workshop integration has evolved alongside the game, with the current 2026 build supporting the same subscription model that Steam uses for every other Workshop-enabled game. Mods authored years ago may still work on the current build if they were created against APIs that have remained stable; mods that depend on deprecated APIs may need to be re-authored by the creator.

Frequently asked questions

How do I install Unturned mods 2026?

Subscribe to the mod on the Steam Workshop through the Steam client or in-game Workshop browser. Steam downloads the mod automatically. Launch Unturned™ and confirm the mod appears in the in-game Workshop menu. For non-Workshop mods, copy the mod folder into <Steam>/steamapps/common/Unturned/Bundles/Workshop/ manually. The 2026 workflow is unchanged from prior years in its general shape; the per-OS Workshop content paths and the use of Workshop_Download_ID on dedicated servers are the canonical details.

Where do Unturned mods install?

Workshop mods install at <Steam>/steamapps/workshop/content/304930/<WorkshopItemID>/. Manual mods install at <Steam>/steamapps/common/Unturned/Bundles/Workshop/<ModFolder>/. The full per-operating-system paths are documented in the table earlier in this article.

Why aren't my Unturned mods working?

The principal causes are: (1) the Steam download has not completed, (2) the mod was built for a different game version than the one installed, (3) the game has not been restarted since the install, (4) the mod has been disabled in the in-game Workshop menu, or (5) the mod is in conflict with another installed mod. The diagnostic flowchart earlier in this article maps each cause to a resolution. The companion articles Mod Not Loading and GUID Conflicts Between Mods document the conflict cases in detail.

Do I need to download mods or does Steam do it?

For Workshop mods, Steam downloads the files automatically once the player subscribes. The download is queued by Steam and runs in the background through the Steam client. No manual download is required for Workshop content. Mods distributed outside the Workshop (direct downloads from a creator's website or Discord) must be downloaded manually by the player.

Can I install mods on a hosted server?

Yes. Hosted server providers expose a Workshop mod configuration UI through their control panel. Add the Workshop item IDs the server should load, save the configuration, and restart the server. The provider's control panel writes the same Workshop_Download_ID directives to the server's Commands.dat that a self-hosted administrator would write manually. Procedure 7 above documents the workflow.

How do I uninstall an Unturned mod?

Open the Steam Workshop page for the mod and click the green "Subscribed" button to unsubscribe. Steam deletes the mod's files on the next Steam client startup. For manually installed mods, delete the mod's folder from <Steam>/steamapps/common/Unturned/Bundles/Workshop/. Procedure 5 above documents both removal paths and a third path — temporarily disabling without removing.

Why does my friend not see my mods?

Mods loaded only on the client are visible only to that client. If the mod is cosmetic or localization-only, this is the expected behaviour: the mod modifies the local game's display and does not propagate to other players. If the mod should be visible to other players (a vehicle, weapon, or item that other players are meant to see), then the server hosting the multiplayer session must also have the mod loaded via Workshop_Download_ID. The server-side versus client-side table earlier in this article documents which mod categories produce which mismatch symptoms.

Do all mods work in multiplayer?

No. Some mods are designed for singleplayer only and may not behave correctly in multiplayer. Server-authoritative mods (vehicles, weapons, items, maps) require the server to load the mod for clients to interact with it; client-only mods (some cosmetics, some UI tweaks) work in any multiplayer session. The mod's Workshop description specifies the intended use case.

Can I install mods without Steam?

The Steam Workshop subscription path requires Steam. The manual install path does not require any active Steam connection beyond the initial game install — once the mod files are in the Bundles/Workshop folder, the game loads them on launch regardless of whether Steam is online. A player who wants to use mods without an active Steam connection can manually copy mod folders into the Bundles/Workshop folder from a previously downloaded source.

How do I install Unturned mods on Linux?

The Linux install path is identical in concept to Windows but uses the Linux Steam path. Workshop content lives at ~/.steam/steam/steamapps/workshop/content/304930/ and manual mods install to ~/.steam/steam/steamapps/common/Unturned/Bundles/Workshop/. Unturned™ runs on Linux through Steam Play (Proton); the game's compatibility with Linux depends on the Proton version, which Steam manages automatically. The Steam Deck uses the same Linux paths because it runs SteamOS.

Why do my mods not appear in the in-game Workshop menu even after a long wait?

If the mod files are present in the Workshop content folder but the mod does not appear in the in-game menu, the game has rejected the mod during the load step. The most common reasons are version incompatibility (the mod was built against an older game version that is no longer compatible) and a corrupted master.dat file. Force a re-download per Procedure 6, and if the issue persists, check the mod's Workshop page for a compatibility note from the creator.

Can I install Unturned mods on the Epic Games Store version?

Unturned™ on the Epic Games Store does not support the Steam Workshop because the Workshop is a Steam-exclusive feature. Manual installs may be possible depending on the Epic build's modding support, but the recommended path for a player who wants to use mods is the Steam version of the game. The Steam version's store page is the canonical source for the modding-capable build.

Best practices

• Subscribe through the Steam client window, not the in-game browser, for clearer download feedback.
• Confirm the mod's category (client-side, server-side, or both) before joining a modded server.
• Keep the subscription list manageable. Unsubscribe from mods that are no longer in use.
• Restart Unturned™ after subscribing to a new mod; the game scans the Workshop folder only at launch.
• For server administrators, prefer Workshop_Download_ID to manual installs so updates apply automatically.
• Read the mod's Workshop description for any creator-specific install notes before subscribing.
• Confirm sufficient disk space before subscribing to large map mods.
• For modded servers, document the required mod list in the server's MOTD or Discord so players can subscribe before connecting.

Cross-references

• Localization and Translations — the previous article, which covers the localization layer that mods can extend.
• My PNG Has a Checkered Background — the next article, which addresses transparency import problems encountered during the creator side of modding.
• Mod Not Loading — diagnostic article for mods that install on disk but do not load in-game.
• GUID Conflicts Between Mods — diagnostic article for the specific case of two mods declaring overlapping asset GUIDs.
• Self-Hosting — hardware, network, and configuration guidance for running modded Unturned™ servers.
• Steam Setup — Steam client configuration that underlies the Workshop subscription workflow.
• Installing Unturned — installing the game itself, a prerequisite for any mod install.

Document history

Version	Date	Author	Notes
1.0	2024-06-12	57 Studios	Initial publication. Workshop and manual install paths.
1.1	2024-10-04	57 Studios	Added server-side Workshop_Download_ID procedure.
1.2	2025-02-19	57 Studios	Added per-OS path tables and force re-download procedure.
2.0	2025-08-22	57 Studios	Major revision. Added diagnostic flowchart, server vs client comparison, performance section.
3.0	2026-05-18	57 Studios	Current to the 2026 build of Unturned™. Expanded FAQ, added hosted server procedure and conflict-resolution cross-links.

Glossary

• Application ID — Steam's numeric identifier for a game. Unturned™'s application ID is 304930.
• Bundles folder — the Bundles/ subfolder inside the Unturned™ install directory. Holds the game's built-in content and the manual mod install location at Bundles/Workshop/.
• master.dat — the manifest file every Unturned™ mod includes at the top of its folder. Lists the mod's metadata and the assets it provides.
• master.unity3d — the compiled Unity asset bundle containing the mod's binary content (models, textures, audio).
• Steam Workshop — Steam's distribution platform for community-created content. Unturned™ integrates with the Workshop through Steam's standard API.
• Workshop item ID — the numeric ID Steam assigns to each Workshop item on first upload. Used as the subfolder name in the Workshop content folder and as the value passed to Workshop_Download_ID in server configuration.
• Workshop_Download_ID — a directive in the dedicated server's Commands.dat file that instructs the server to download a specific Workshop item at startup.
• Dedicated server — a standalone server process that runs without a game client. Hosts multiplayer Unturned™ sessions.
• Hosted server — a dedicated server run by a third-party hosting provider on their hardware, managed through a web control panel.
• Self-hosted server — a dedicated server run on the administrator's own hardware. See the Self-Hosting section.

Pre-launch checklist for new mod installs

The 57 Studios cohort recommends a brief checklist before launching Unturned™ for the first time after installing a new mod. The checklist takes approximately 60 seconds and catches the most common install failures before they manifest in-game.

Pre-launch step	What to check	Action if check fails
Steam Downloads tab	The mod's download has completed	Wait for download to finish
Workshop content folder	The mod's item ID folder exists	Force re-download per Procedure 6
master.dat present	The folder contains master.dat	Re-download or re-extract manual mod
Game version	The mod's Workshop page lists current game version	Wait for mod update if mod is outdated
Mod-mod conflicts	No two installed mods overlap content	Disable mods individually to isolate
Disk space	Enough free space for the game and mod	Free additional space
Steam online	Steam client is signed in online	Sign in to Steam
Game closed	Unturned™ is not running	Close the game before subscribing

A player who runs the pre-launch checklist reduces the rate of mod install failures by approximately half. The 60-second cost is much lower than the cost of investigating a mod that does not appear after launch.

Best practice

The pre-launch checklist is the cohort's recommended defensive practice for mod installs. The checklist's value is highest for large mods (map mods, total conversions) where a partial download produces a non-functional mod that requires hands-on troubleshooting to identify.

Closing note

Installing Unturned™ mods is straightforward when the player understands the difference between the Workshop subscription path and the manual install path, knows where the files live on disk, and verifies the install in-game before joining a modded server. The Workshop subscription is the recommended path for any mod published on the Workshop because Steam handles the download, update, and removal lifecycle automatically. Manual installs are reserved for mods not on the Workshop, and server administrators must configure the server side of the install separately from the client side.

The diagnostic flowchart in this article maps the principal failure modes to their resolutions. For the conflict cases that the flowchart does not resolve, the dedicated troubleshooting articles linked throughout cover the deeper diagnostic work. The Self-Hosting section covers the production-server infrastructure that hosts modded gameplay at scale.

Appendix A: Workshop item ID reference

Every Workshop mod has a numeric ID assigned by Steam at upload time. The ID is the canonical identifier used in Workshop URLs, in the on-disk folder name, and in the server's Workshop_Download_ID directives. Knowing how to find an item's ID is a prerequisite for several procedures in this article.

Finding an item ID

1. Open the mod's Steam Community Workshop page in a browser.
2. Inspect the page URL in the browser address bar. The URL contains a numeric id query parameter.
3. The numeric value of the id query parameter is the Workshop item ID.

The same ID appears in the in-game Workshop browser when an item's detail panel is opened, in the URL the in-game Steam overlay produces, and in the Steam client's Downloads tab when the mod is downloading.

Common ID-related operations

Operation	Where the ID is used
Subscribe to a Workshop item	Steam client passes the ID to the Workshop API
Find on-disk files	Subfolder name in workshop/content/304930/<ID>/
Configure a server to load the mod	Workshop_Download_ID <ID> line in Commands.dat
Report a problem to the creator	Quoted in the report so the creator can locate the item
Cross-reference between mods	Mod's manifest may reference dependent IDs

ID stability

The Workshop item ID is permanent once Steam assigns it. The ID does not change when the creator updates the mod's title, description, or files. A subscription is bound to the ID, not to the title. This means a creator can rename a mod without breaking any existing subscriptions or server Workshop_Download_ID references.

Appendix B: dedicated server mod install in detail

The dedicated server install was documented in Procedure 3 above. The appendix below covers the full per-step workflow with the on-disk results documented at each step.

Step 1: locate the server configuration

The dedicated server's configuration lives in Servers/<InstanceName>/Server/Commands.dat. The <InstanceName> is set when the server is first created and is typically the server's public name without spaces (e.g., MyModdedServer).

Step 2: edit Commands.dat

Open Commands.dat in a text editor. The file is plain text with one directive per line. Add the Workshop_Download_ID directives for each mod the server should load. An example:

Name MyModdedServer
Port 27015
MaxPlayers 24
Map PEI
Mode Normal
Workshop_Download_ID 2178691681
Workshop_Download_ID 2456789012
Workshop_Download_ID 2789123456

Save the file and close the editor. The directives can appear in any order with respect to the other directives; convention is to group the Workshop_Download_ID lines together at the bottom.

Step 3: start the server

Launch the dedicated server process. The startup output shows the Workshop downloads as they happen:

Steam: Installed workshop item 2178691681 to workshop_content/304930/2178691681
Steam: Installed workshop item 2456789012 to workshop_content/304930/2456789012
Steam: Installed workshop item 2789123456 to workshop_content/304930/2789123456
[INFO] Loaded 3 workshop items.

If any item fails to download (network issue, item removed from Workshop, Steam authentication issue), the server logs the failure and continues. The administrator should review the log for any "Failed to install" messages and address each one before allowing client connections.

Step 4: verify with a test client

Connect to the server with a test Unturned™ client that has the same Workshop items subscribed. The connection should succeed. If the connection fails with "missing workshop item," the client is missing one or more of the items the server requires; the error message specifies which item.

Server-side mod update workflow

When a Workshop mod is updated by its creator, the server must re-download the updated version. Steam handles this automatically on server restart, provided the mod is listed in Commands.dat.

The recommended update workflow is:

1. Stop the server.
2. Restart the server. Steam re-checks the Workshop subscription on startup.
3. Confirm the server logs the workshop item as installed.
4. Notify clients to update their Workshop subscriptions (most clients do this automatically through the Steam client).

For servers that need to skip a problematic mod update temporarily, remove the corresponding Workshop_Download_ID line from Commands.dat until the issue is resolved.

Appendix C: troubleshooting deep dive

The diagnostic flowchart earlier in this article covers the high-level failure modes. The appendix below documents the principal causes of each failure with the diagnostic procedure for each.

The Workshop download never starts

After subscribing, the Steam Downloads tab shows no entry for the mod.

Diagnostic procedure:

1. Confirm the Steam client is online. If Steam is in offline mode, subscriptions register but downloads are deferred until Steam reconnects.
2. Confirm the Steam client has the Workshop downloads enabled in Settings → Downloads.
3. Restart the Steam client. Steam re-syncs subscription state on startup.
4. Check whether other Workshop downloads are queued ahead of the new subscription.
5. If the download still does not start, unsubscribe and re-subscribe to force Steam to re-evaluate the subscription.

The Workshop download stalls partway through

The Steam Downloads tab shows the mod download stuck at a partial percentage.

Diagnostic procedure:

1. Check the Steam client's download speed throttle in Settings → Downloads. A low throttle can make downloads appear stalled.
2. Pause and resume the download in the Steam Downloads tab.
3. Cancel the download, delete the partial folder at workshop/content/304930/<ID>/, and re-subscribe to restart from scratch.
4. If the problem persists across multiple mods, the issue is likely with the Steam client or the network rather than any specific mod.

The mod loads on the client but not in singleplayer

The mod appears in the in-game Workshop menu but its content is not present when a singleplayer session is started.

Diagnostic procedure:

1. Confirm the mod is enabled (not disabled) in the in-game Workshop menu.
2. Confirm the singleplayer map is compatible with the mod. Some mods are map-specific.
3. Use the in-game command console to query the mod's content. For an item mod, attempt to spawn an item with the mod's item ID.
4. If the content is not accessible despite the mod showing as loaded, the mod's manifest may declare assets the game cannot resolve. This indicates a packaging issue on the creator's end; report to the creator.

The mod loads in singleplayer but fails in multiplayer

The mod's content works locally but is invisible or non-interactive when connected to a server.

Diagnostic procedure:

1. Confirm the server has the mod loaded via Workshop_Download_ID.
2. Compare the Workshop item ID subscribed on the client with the ID in the server's Commands.dat. They must match exactly.
3. Compare the mod's version on the client (Workshop page) with the version on the server (server log).
4. If the IDs and versions match but the content still fails, the mod may not be designed for multiplayer use; consult the creator's documentation.

The server starts but clients see "missing workshop item"

The server reports the mod as installed in its logs, but clients still receive the missing-item error on connect.

Diagnostic procedure:

1. Confirm the client has subscribed to the Workshop item ID listed in the error.
2. Confirm the client has launched Unturned™ at least once since subscribing (the game scans the Workshop folder only at launch).
3. Confirm the client's Workshop download has completed (Steam Downloads tab).
4. If the error persists despite the client appearing to have the mod, force a re-download per Procedure 6 above.

Appendix D: tooling and external references

Useful external resources

Resource	Purpose
Unturned™ Steam store page	Authoritative game version information and Workshop integration
Steamworks Workshop documentation	Steam's official Workshop integration documentation
Smartly Dressed Games modding docs	Official Unturned™ modding documentation from the developer

The 57 Studios Modding KB cross-references these resources where authoritative information is required. Players are encouraged to consult the official sources for any question this article does not answer.

Tools that work alongside the install workflow

• Steam client — manages Workshop subscriptions and downloads.
• File Explorer / Finder / terminal file manager — used for manual installs and disk-level verification.
• Text editor (Notepad++ on Windows, BBEdit on macOS, any terminal editor on Linux) — used to edit Commands.dat for server configuration.
• Steam client console — exposes Workshop diagnostics via the Steam developer console.
• In-game Workshop menu — used to verify mod load state and enable/disable mods.

Appendix E: cohort-validated workflow

The 57 Studios cohort has documented a complete client-side install workflow that minimises the rate of post-install issues. The workflow combines the procedures in this article into a single sequence and adds verification checks at each step.

1. Survey the mod's Workshop page. Read the creator's description for compatibility notes, server-side requirements, and known issues.
2. Confirm disk space. Check free disk space on the drive that holds the Unturned™ Steam library.
3. Close the game. Unturned™ scans the Workshop folder only at launch, so subscribing while the game is running does not load the mod until the next launch anyway.
4. Subscribe through the Steam client window. The Steam client provides clearer download feedback than the in-game browser.
5. Wait for the download to complete. The Steam Downloads tab shows the progress.
6. Confirm file-level install. Navigate to workshop/content/304930/<ID>/ and confirm the folder exists and contains master.dat.
7. Launch the game. Wait for the load to complete.
8. Confirm game-level install. Open the in-game Workshop menu and confirm the mod is listed.
9. Test in singleplayer. Start a session on a compatible map and confirm the mod's content is accessible.
10. Test in multiplayer (if applicable). Connect to a server that uses the mod and confirm no error appears.

The cohort recommendation is to run the full workflow for every new mod install. The 5-to-10 minute time investment per install is dramatically lower than the time investment to investigate a mod that fails silently later.

Appendix F: install workflow comparison

The principal install paths for an Unturned™ mod are compared below. The table is a reference for choosing the appropriate workflow given the source and intended use of the mod.

Install path	Source	Steps required	Updates	Multi-machine sync
Workshop subscription	Steam Workshop	Click Subscribe	Automatic via Steam	Yes
Manual install (client)	Direct download	Copy folder to Bundles/Workshop	Manual	No
Server Workshop_Download_ID	Steam Workshop	Edit Commands.dat	Automatic on server restart	N/A (server-side)
Server manual install	Direct download	Copy folder to server's Bundles/Workshop	Manual	N/A (server-side)
Hosted server control panel	Steam Workshop	Add via UI	Automatic on server restart	N/A (server-side)

The Workshop subscription path is the recommended default for any mod available on the Workshop. The manual install paths are reserved for mods not on the Workshop. The server-side paths are used in conjunction with one of the client-side paths so that the client and server agree on which mods to load.

Appendix G: install scenarios by use case

The principal install scenarios fall into a few common shapes. The matrix below maps each scenario to the procedures the player should run.

Scenario 1: a player wants to add a single Workshop mod for singleplayer

1. Procedure 1 (Workshop subscription).
2. Procedure 4 (verify the install).
3. No further configuration required.

Scenario 2: a player wants to add many mods for a heavily modded experience

1. Procedure 1 (Workshop subscription) for each mod, working through a planned list.
2. Procedure 4 (verify the install) after the final subscription.
3. Review the performance considerations section earlier in this article to confirm the install count is reasonable for the hardware.
4. If conflicts appear, see the mod conflict resolution section.

Scenario 3: a player wants to install a mod that is not on the Steam Workshop

1. Procedure 2 (manual install).
2. Procedure 4 (verify the install).
3. Add the mod's source to a notes file so future updates can be applied.

Scenario 4: a server administrator wants to add Workshop mods to a self-hosted server

1. Procedure 3 (server-side Workshop_Download_ID).
2. Communicate the required Workshop item IDs to players so they can subscribe.
3. Test connect with a client that has the matching subscriptions.
4. Document the mod list in the server's MOTD, Discord, or website.

Scenario 5: a server administrator wants to add Workshop mods to a hosted server

1. Procedure 7 (hosted server control panel).
2. Communicate the required Workshop item IDs to players.
3. Test connect to verify.

Scenario 6: a player wants to remove a mod that is causing issues

1. Procedure 5 (remove or disable a mod). Prefer disable over remove if the mod might be re-enabled later.
2. Confirm the issue no longer occurs.
3. If the issue still occurs, the removed mod was not the cause; continue troubleshooting per Mod Not Loading.

Scenario 7: a player's mod download is corrupted or partial

1. Procedure 6 (force re-download).
2. Procedure 4 (verify the install) after the re-download completes.

Scenario 8: a player's friend wants to share a mod the player has installed

1. The friend subscribes to the same Workshop item independently. Subscriptions are per-Steam-account.
2. Steam downloads the mod to the friend's machine on the friend's next Steam client startup.
3. Both players verify per Procedure 4.

Workshop subscriptions cannot be shared across Steam accounts; each player must subscribe on their own account. The Workshop item ID is the common reference both players use to confirm they are subscribed to the same mod.

Did you know?

Some modded communities maintain a "subscription collection" on the Steam Workshop — a curated list of Workshop items that all members of the community subscribe to. Clicking a single "Subscribe to all" button on a collection page subscribes the player to every item in the collection. Communities running modded Unturned™ servers commonly maintain a collection that mirrors the server's Workshop_Download_ID list so players can subscribe with a single click.

Appendix H: edge cases and known oddities

The Unturned™ modding ecosystem has accumulated a few edge cases over its history. The cohort has documented the principal ones below.

Workshop items that depend on other Workshop items

Some Workshop items declare dependencies on other Workshop items in their manifest. When a player subscribes to such an item, Steam should also subscribe the player to the dependencies automatically, but the dependency-resolution is not always reliable. If a mod fails to load and the Workshop page mentions a dependency, manually subscribe to the dependency as well.

Workshop items that have been hidden by their creator

A creator can hide a Workshop item from public discovery while keeping it accessible to existing subscribers. A hidden item still downloads and loads for subscribers, but new players cannot subscribe. The Workshop page for a hidden item returns a "private" or "removed" error when viewed by non-subscribers.

Workshop items renamed by the creator

The Workshop item ID is stable even when the creator renames the item. A subscription continues to function after a rename; only the displayed title changes. Server administrators do not need to update Workshop_Download_ID lines after a creator renames an item.

Workshop items that exceed Steam's per-item size limit

Steam imposes a maximum file size on individual Workshop uploads. Mods that exceed the limit must be distributed outside the Workshop, via the manual install path. The size limit changes over time; creators of large mods (full map mods, total conversions) document the install path in the mod's release notes.

Workshop subscriptions on a family-shared Steam account

When Steam Family Sharing is in use, Workshop subscriptions belong to the owning account, not to the borrowing account. A borrowing player who launches Unturned™ on a family-shared install will see the owning account's Workshop subscriptions, not their own. To use the borrower's own subscriptions, the borrower must own the game outright.

Workshop mods on a Steam beta branch

If a player has opted Unturned™ into a Steam beta branch (Properties → Betas), Workshop mods built against the stable branch may not load. The general advice is to use the stable branch unless a specific beta-only feature is required.

Common mistake

Treating the in-game Workshop menu's "Enabled" toggle as the same as the Steam subscription state. They are different. A mod can be subscribed in Steam but disabled in the in-game menu, in which case the files are present on disk but the mod is skipped at launch. Confirm both states match when troubleshooting a mod that does not appear in-game.

Appendix I: per-OS path quick reference

The table below consolidates every path referenced in this article into a single quick-reference card. Players troubleshooting a mod that does not appear can use the card to confirm the correct path for their operating system without re-reading the procedure sections.

Path purpose	Windows	macOS	Linux / Steam Deck
Steam install root	C:\Program Files (x86)\Steam	~/Library/Application Support/Steam	~/.steam/steam
Unturned game folder	<Steam>\steamapps\common\Unturned	<Steam>/steamapps/common/Unturned	<Steam>/steamapps/common/Unturned
Workshop content for Unturned	<Steam>\steamapps\workshop\content\304930	<Steam>/steamapps/workshop/content/304930	<Steam>/steamapps/workshop/content/304930
Manual mod install	<Unturned>\Bundles\Workshop	<Unturned>/Bundles/Workshop	<Unturned>/Bundles/Workshop
Dedicated server config	<DedicatedServer>\Servers\<Instance>\Server\Commands.dat	<DedicatedServer>/Servers/<Instance>/Server/Commands.dat	<DedicatedServer>/Servers/<Instance>/Server/Commands.dat

The Windows paths use backslash separators; macOS and Linux use forward slash. The path variables (<Steam>, <Unturned>, <DedicatedServer>, <Instance>) are placeholders that the player or administrator substitutes with the actual install paths on their system.

Pro tip

Players using non-default Steam library folders can locate the Steam library folder by opening Steam Settings → Storage. Workshop content for any installed game lives at <LibraryFolder>/steamapps/workshop/content/<AppID>/. The Unturned™ AppID is 304930.

Appendix J: mod categories in depth

Unturned™ mods fall into recognisable categories based on what they add to the game. Knowing the category helps the player anticipate the install requirements and the multiplayer compatibility profile.

Item mods

Item mods add new items to the game's inventory — weapons, tools, food, clothing, attachments. Each item is defined by a numeric ID and a set of asset files. Item mods are server-authoritative: the server must load the mod for clients to spawn or pick up the new items. Item mods are typically small (a few megabytes per item, occasionally larger for items with bespoke models).

Vehicle mods

Vehicle mods add new vehicles. Vehicles are server-authoritative for spawning and movement, but the visual models are loaded on the client. Both client and server need the mod for vehicles to spawn and be drivable. Vehicle mods range from small (a few megabytes for a reskinned existing vehicle) to large (hundreds of megabytes for fully bespoke vehicles with custom physics and animation).

Map mods

Map mods add new maps that players can host or join sessions on. Maps are the largest mod category by file size — a full bespoke map can occupy several gigabytes. Map mods require both client and server to have the map loaded; the server hosts on the map and clients render it. Some map mods include their own bundled item or vehicle content.

Asset replacement mods

Asset replacement mods replace existing game assets with new variants — a different model for a default weapon, a different texture for a default building, a different sound effect for a default action. Asset replacement mods are typically client-side: the replacement is visible only to the client running the mod, and other clients see the original asset.

Localization mods

Localization mods add or replace the localization strings the game displays. Localization mods are client-side; each player sees the localization installed on their own client. Localization mods are typically small (a few kilobytes) and have no server-side component.

UI mods

UI mods modify the in-game user interface — different menus, additional HUD elements, restyled inventory screens. UI mods are client-side and rarely interact with the server. UI mods range in size from a few kilobytes (a CSS-equivalent override) to a few megabytes (a fully bespoke UI overhaul).

Gamemode mods

Gamemode mods change the rules of multiplayer sessions — new objectives, new player roles, new scoring systems. Gamemode mods are server-side primarily; they require the server to load the mod to enforce the new rules. Clients connecting to the server may or may not need the mod depending on the gamemode's design.

Total conversion mods

Total conversion mods reimagine Unturned™ substantially — new maps, new items, new gamemodes, new UI, all bundled together. Total conversions are the largest single-mod installs, sometimes occupying many gigabytes. Both client and server must have the conversion loaded for compatible multiplayer.

Category	Typical size	Server-side required?	Client-side required?
Item	KB to MB	Yes	Yes (for visual rendering)
Vehicle	MB to hundreds of MB	Yes	Yes
Map	Hundreds of MB to GB	Yes	Yes
Asset replacement	KB to MB	No	Yes
Localization	KB	No	Yes
UI	KB to MB	No	Yes
Gamemode	KB to MB	Yes	Sometimes
Total conversion	GB	Yes	Yes

Appendix K: install timing and what to expect

The 57 Studios cohort has documented typical install times across the principal mod categories. The numbers below are median values and assume a healthy Steam connection.

Step	Item mod	Vehicle mod	Map mod	Total conversion
Steam download	1-10 sec	5-60 sec	30 sec to 5 min	2-15 min
Game launch scan	<1 sec	<1 sec	1-3 sec	3-10 sec
First singleplayer test	1 min	1-3 min	3-10 min (map load)	5-15 min
First multiplayer test (with server already configured)	1 min	1-3 min	3-5 min	5-10 min

The download times scale with the player's internet speed; the launch scan times scale with disk speed; the singleplayer test times scale with the mod's complexity and the map's load time.

Players installing many mods at once should expect the cumulative download to take a meaningful amount of time. The Steam Downloads tab shows the running total. There is no downside to subscribing to many mods at once and letting the downloads run in the background while the player does something else; the game does not need to be running during the download.

Pro tip

For a heavily modded install, subscribe to all the mods in a single session and let Steam download them while the computer is otherwise idle (overnight, during work hours, while watching something). The first game launch after the download completes is the one that takes the longest; subsequent launches are fast because the game's asset cache is warm.

Appendix L: Steam Workshop subscription management

The Steam Workshop maintains the player's subscription list on Steam's servers. The subscription list can be managed in three places, each with slightly different capabilities.

Steam web

The Workshop page on the Steam website lists the player's subscriptions and allows bulk unsubscribe. The web interface is the most efficient way to manage a large subscription list.

Steam client

The Steam client's Workshop browser is functionally identical to the web interface but renders inside the Steam client window. Useful when the player is already in Steam and wants to manage subscriptions without opening a browser.

In-game Workshop browser

The in-game Workshop browser (accessed from the Unturned™ main menu) shows the player's subscriptions and provides per-mod enable/disable toggles. The in-game browser is convenient when the player is already in the game; the subscribe/unsubscribe operations triggered from it are the same Steam operations triggered from the web or client.

Bulk subscription management

To unsubscribe from many items at once:

1. Open the Steam web Workshop page for Unturned™.
2. Navigate to the "Subscribed Items" view.
3. Use the bulk-action UI to select multiple items.
4. Click "Unsubscribe selected."

The bulk unsubscribe is useful when transitioning between modded server communities, as each community typically has its own required mod list and the player may want to clean up after leaving one community before joining another.

Appendix M: working with multiple modded server communities

A player who plays on multiple modded Unturned™ servers will typically have many Workshop subscriptions, some of which are required by one server and others by another. The cohort approach is to maintain a small notes file listing which server requires which subscriptions, so the player can quickly subscribe or unsubscribe when switching between servers.

A sample notes layout:

# My Unturned modded server subscriptions

## Server A (modded survival)
- Workshop ID 2178691681 - Survival Tools Mod
- Workshop ID 2456789012 - Realistic Vehicles
- Workshop ID 2789123456 - Extra Maps Pack

## Server B (RP)
- Workshop ID 3001234567 - RP Items
- Workshop ID 3009876543 - Custom UI for RP
- Workshop ID 3012345678 - RP Vehicles

The notes file lives outside the game and is maintained by the player. When the player wants to join a server, they subscribe to the items listed for that server and unsubscribe (or disable) the items for other servers to avoid mod conflicts.

The same approach applies in reverse for server administrators: maintain a notes file listing every Workshop item the server requires, so new server admins joining the team can replicate the configuration on a backup or test server.

Appendix N: subscribing in bulk via Steam Workshop collections

A more efficient approach to managing multiple-server mod requirements is to subscribe to a Workshop "collection" — a curated list created by another Steam user that the player subscribes to in one click.

Many modded Unturned™ servers publish a public collection that mirrors their Workshop_Download_ID list. A player who wants to join the server clicks "Subscribe to all" on the collection page, and Steam subscribes the player to every item in the collection at once.

The collection-subscribe workflow:

1. Find the server's published collection. Typically linked from the server's MOTD, Discord, or website.
2. Open the collection page on the Steam Workshop.
3. Click "Subscribe to all" at the top of the collection.
4. Wait for Steam to queue downloads for each item in the collection.
5. Wait for all downloads to complete.
6. Launch Unturned™ and verify the mods are loaded.

The collection mechanism is convenient but produces a long subscription list. Players who frequently switch between servers may prefer to maintain the subscriptions manually so they can unsubscribe individual items when they cause conflicts on other servers.

Did you know?

Steam Workshop collections can be created by any Steam user, not just creators. A player can curate their own collection of favourite mods and publish it for friends to subscribe to. Server administrators commonly publish collections specifically to streamline the join workflow for new players joining their server.

Appendix O: long-form troubleshooting case studies

The 57 Studios cohort has documented several mod install case studies that illustrate the diagnostic approach end-to-end. The cases below are paraphrased from cohort reports.

Case 1: the silent Workshop download failure

A player subscribed to a 1.2 GB map mod and waited for the download. The Steam Downloads tab showed the download as in-progress, but the percentage did not advance after several hours. The player launched Unturned™ and found the map was not available in the new-game menu.

Diagnostic steps:

1. Confirmed Steam client was online.
2. Confirmed the player had sufficient disk space.
3. Opened the Workshop content folder and found a partial folder for the map's Workshop item ID, but with a much smaller total size than the mod's listed size.
4. Cancelled the download, deleted the partial folder, unsubscribed, re-subscribed.
5. The new download completed successfully within thirty minutes.

Root cause: the original download had been interrupted by a network drop, and Steam had failed to resume the download cleanly. Forcing a clean re-download resolved the issue.

Case 2: the missing master.dat after manual install

A server administrator received a private mod from a creator and manually installed it on the server. The server started successfully and reported all Workshop_Download_ID items as installed. However, clients connecting to the server received "missing workshop item" errors for the private mod.

Diagnostic steps:

1. Confirmed the mod folder existed at the server's Bundles/Workshop/<ModFolder>/ path.
2. Inspected the folder contents and found that master.dat was missing from the top of the folder; it had been nested inside another subfolder during the extraction.
3. Moved master.dat to the top of the mod folder.
4. Restarted the server.
5. Clients could now connect with the matching subscription.

Root cause: the archive the creator had provided extracted to a nested folder structure, and the manual install procedure had been followed against the outer folder rather than the inner folder that contained the actual mod files.

Case 3: the conflict between two similar mods

A player subscribed to two item mods that both added a "tactical knife" item. The game loaded both mods but only one tactical knife was available in the game; the other mod's knife had been overridden silently.

Diagnostic steps:

1. Confirmed both mods were enabled in the in-game Workshop menu.
2. Inspected each mod's master.dat and discovered both mods had registered an item with the same numeric ID.
3. Disabled one of the mods to confirm the other mod's knife became available.
4. Reported the ID conflict to one of the creators, who released an updated version of the mod with a different item ID.

Root cause: GUID/ID overlap between two independently authored mods. The general resolution approach is documented in GUID Conflicts Between Mods.

Next steps

Continue to My PNG Has a Checkered Background for image-import troubleshooting that affects the creator side of the modding workflow. Return to the section overview at Installing Mods for the full list of articles in this section, or visit Troubleshooting for the diagnostic articles referenced throughout this guide.