How to Verify Unturned Game Files

Verifying the integrity of Unturned™'s game files is a maintenance procedure built into the Steam client. When you run a verification, Steam compares every file on your local disk against the cryptographic hashes published in the game's manifest. Any file that does not match is flagged, deleted, and re-downloaded automatically. For 57 Studios™ Knowledge Base readers, verification is the second step in the install pipeline because it provides a definitive answer to the question of whether the install completed without errors. A successful verification is the cleanest possible starting point for everything that follows.

Verification is also one of the most useful general-purpose troubleshooting tools available to an Unturned player or modder. Many launch failures, missing-texture issues, mod-loading errors, and update problems are resolved by a single verification pass. Knowing when to run verification, what it does and does not fix, and how to interpret its results is a core competency that pays dividends across the rest of a modding career.

Pro tip

Run a verification immediately after the first install, even if Steam reports the install as complete. This catches the small percentage of installs that finish with one or two corrupted files due to network errors during the download.

Prerequisites

You need Unturned installed (covered in the previous article), Steam running, and an internet connection. Verification re-downloads any mismatched files, so a closed internet connection will cause the verification to fail.

What you'll learn

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

• Open the Properties dialog for Unturned in your Steam Library
• Navigate to the Installed Files tab
• Initiate a verification of game-file integrity
• Interpret each possible verification outcome
• Identify situations in which a verification is the correct troubleshooting step
• Distinguish problems that verification can fix from those it cannot
• Maintain a sensible verification cadence for ongoing modding work

Background: what verification actually does

Verification is sometimes described as "checking the game files," but the operation is more precise than that phrase suggests. Steam performs a cryptographic hash comparison against an authoritative manifest. Understanding this distinction helps you predict what verification can and cannot fix.

The flowchart above shows the full verification loop. Steam reads each file on disk, computes its hash, and compares the hash against the value stored in the manifest. The manifest is fetched fresh from Steam's CDN at the start of every verification, which means the verification always uses the current authoritative reference rather than a cached copy.

Did you know?

The manifest Steam uses for verification is the same manifest used during the original install. The manifest is signed by Valve's servers, which means a verification implicitly confirms that the files on disk match the version Valve published, not just that they are internally consistent.

What the verification process actually reads

A verification operation touches every file in the Unturned install folder. On a typical install this is several thousand files distributed across a dozen top-level subdirectories. The verification reads each file completely, computes its hash, and compares the result against the manifest entry for that file.

File category	Typical count	Total size	Verification time
Executables and DLLs	About 30 files	200 MB	A few seconds
Unity asset bundles	Several hundred files	4 GB	Most of the verification time
Localization files	About 100 files	50 MB	A few seconds
Configuration templates	About 50 files	10 MB	Less than a second
Sample assets	A few hundred files	1 GB	A noticeable fraction of the total
Anti-cheat client files	About 20 files	100 MB	A few seconds

The file category table above shows the rough distribution. The Unity asset bundles dominate verification time because they are the largest single category of files. Verification time scales linearly with total file size on a fixed drive read speed.

The hash algorithm

Steam uses SHA-1 hashes in the manifest, computed at the chunk level rather than at the file level. Each chunk has its own hash, and a file's verification result is derived from the verification results of every chunk that composes the file. This chunk-level granularity is what allows Steam to re-download only the changed portion of a file during an update rather than the entire file.

Did you know?

The chunk-based hash scheme is also what makes Steam updates fast for large games. When a game patch changes a single 10 MB region of a 50 GB game, Steam downloads only the chunks containing the changed region. The same scheme is used during verification, which is why a mostly-clean install can complete verification in a minute or two even on a large game.

Step 1: Open Unturned's Properties dialog

The verification feature lives inside Unturned's Properties dialog. To open it:

1. Open the Steam client
2. Click the Library tab at the top of the window
3. Locate Unturned in the left-hand library list
4. Right-click the Unturned entry to open the context menu
5. Click Properties at the bottom of the context menu

A new window will open titled "Unturned - Properties." This window has several tabs along the left edge.

Common mistake

Beginners sometimes left-click the Properties entry instead of right-clicking the game to access it. Properties only appears in the right-click context menu, not in the main library page's button row.

What the Properties window contains

The Properties window aggregates every per-game configuration setting Steam exposes. Verification is one tab among several; understanding the rest of the window is useful even if you only came to run a verification.

Tab	Purpose
General	Display name, launch options, overlay settings
Updates	Update behaviour: automatic, manual, on-demand
DLC	Manage downloadable content for this game
Workshop	Manage Workshop subscriptions for this game
Compatibility	Override the default platform compatibility tool
Betas	Switch between game branches if multiple are published
Installed Files	Disk size, install location, verification, move
Language	Game language selection
Controller	Per-game controller configuration

The Installed Files tab is the one this article focuses on. Most of the other tabs are useful in their own right and are referenced in later articles in the knowledge base.

Step 2: Navigate to the Installed Files tab

The Properties window has a vertical list of tabs along its left edge. The tabs vary slightly depending on the Steam client version, but the relevant tab is always labeled Installed Files.

1. Click Installed Files in the left-hand tab list
2. The right pane will display install information including the install size, the install location, and several action buttons

The action buttons typically include Verify integrity of game files, Move install folder, and Browse. The verify button is the one you need.

Reading the install location

Before clicking verify, take a moment to read the install location displayed on the Installed Files tab. The location is the full filesystem path to the Unturned install folder. Memorising or noting this path is useful for many subsequent activities. The default value on a standard Steam installation is C:\Program Files (x86)\Steam\steamapps\common\Unturned; on machines with additional library folders, the path uses a different drive letter and folder name.

Display element	What it shows
Install location	Full filesystem path to the Unturned install folder
Size on disk	Actual disk footprint after install completes
Manifest size	Expected size from the manifest
Steam Cloud quota	Cloud storage used by Unturned
Available actions	Verify integrity, Move install folder, Browse, Uninstall

The information panel above is the same panel used for confirming an install at the end of the previous article. Both articles return to this panel because it is the canonical location for install-level information.

Step 3: Initiate the verification

Click Verify integrity of game files. Steam will:

1. Close the Properties dialog automatically
2. Return you to the Library view
3. Begin a download-progress display under Unturned's library tile

The progress display shows the number of files checked and the total number of files in the manifest. On a typical machine, verifying Unturned takes between one and five minutes depending on drive speed.

Pro tip

You can continue to use other Steam features during verification. The verification runs in the background and does not block the rest of the Steam client.

Verification progress interpretation

The Steam progress display changes over the course of the verification. Understanding the sequence helps you interpret what the client is doing at each stage.

Stage	Display reads	What is happening
Startup	"Validating Unturned files"	Steam fetches the manifest from the CDN
Read phase	"Validating Unturned files: X of N"	Steam reads each file from disk and computes its hash
Compare phase	Same display	Hashes are compared against manifest values; mismatches are queued
Re-download phase (if needed)	"Updating Unturned" with bytes counter	Steam downloads replacements for mismatched files
Final write phase (if needed)	"Updating Unturned: writing changes"	Steam writes replacement files to disk
Completion	Library tile returns to Play state	Verification succeeded; any mismatches have been fixed

The progress sequence above is the same for any Steam game, not just Unturned. The relative duration of each stage varies with the game's size and the number of files that need replacement.

Did you know?

The verification cannot be paused. Once started, Steam reads through every file in the install folder before producing a result. The verification can be cancelled (covered later in the article) but the cancellation is a hard stop rather than a pause; resuming requires starting over.

Verification outcomes

Verification produces one of three possible outcomes. The outcome is displayed in the library tile status when the operation completes.

Outcome	Steam message	Meaning	Action required
Clean	"All XX files successfully validated"	Every file on disk matches the manifest	None — the install is healthy
Files reacquired	"N files failed validation and will be reacquired"	One or more files were corrupted, missing, or modified; Steam will re-download them	Wait for the re-download to finish
Verification failed	"Verification failed" or stuck progress	Steam could not complete the verification due to a permissions or disk error	Investigate disk health and Steam permissions

The outcome table above maps each result to the appropriate response. The most common outcome on a fresh install is "All files successfully validated." The second most common is "1 or 2 files failed validation," which Steam silently re-downloads. The third outcome is rare and usually indicates a deeper system problem.

The clean outcome in detail

A clean verification means every file on disk has a hash that exactly matches the corresponding manifest entry. This is the desired outcome and the baseline for confident modding work. After a clean verification you can move to the next article in the install pipeline without further concern.

A clean verification does not mean the game will launch successfully. Verification confirms the install matches what Valve published, but launching also depends on factors outside the install folder: graphics drivers, anti-cheat client state, user-data folder permissions, and the operating system itself. A clean verification followed by a failed launch points the diagnostic elsewhere.

The reacquired outcome in detail

A few files failed validation and Steam will replace them. This outcome is common and is exactly what verification is designed to handle. The replacement happens automatically; you wait for the second progress bar to complete and then verify again to confirm the second pass is clean.

If a verification consistently produces the reacquired outcome across multiple runs, with the same files appearing each time, the install drive may be failing. Persistent corruption that survives re-download is a signal worth investigating with drive-health tools.

The verification-failed outcome in detail

Verification can fail entirely if Steam cannot read the install folder or cannot write replacement files. This outcome is rare and indicates a system-level problem that verification alone cannot fix.

Failure cause	Symptom	Recommended response
Permission error on install folder	"Missing file privileges"	Right-click the Steam folder, Properties to Security, grant full control to your user
Install drive disconnected	"Could not read file"	Reconnect the drive and retry
Antivirus interference	Verification stalls partway through	Add Steam to antivirus exclusions and retry
Drive hardware failure	Read errors in Windows Event Viewer	Replace the drive
Steam client corruption	Steam itself behaves abnormally	Repair the Steam install through the Steam client installer

A verification-failed outcome is a signal to address the system-level issue before attempting to verify again. Once the underlying problem is resolved, a fresh verification will produce one of the two normal outcomes.

When to run a verification

Verification is the correct troubleshooting step in several common situations. Knowing when to run it saves time compared to reinstalling the entire game.

The decision flowchart above shows the most common situations in which verification is the appropriate response. Crashes on launch, failed updates, missing visual assets, and any situation involving manual edits to game files all warrant a verification.

Common mistake

Modders sometimes manually edit files in the Unturned install folder for testing, then run a verification later and lose their changes. Steam considers any edited file to be a mismatch and re-downloads it. Always back up manually edited files before running a verification.

Critical warning

Never delete files from the Unturned install folder while Steam is running. If Steam attempts to write to a file you have deleted, the resulting error can corrupt Steam's internal state and require a Steam client repair.

Common scenarios that warrant verification

Beyond the decision flowchart, several specific real-world scenarios are worth covering in detail.

Scenario	Recommended response
Fresh install completed	Verify once to confirm the install is clean
Steam update applied successfully	No verification needed unless problems appear
Steam update reported as failed	Verify to repair the partial update
Game crashes on launch	Verify before deeper troubleshooting
Mod fails to load	Verify base game files first; then investigate the mod
Multiplayer server kicks for "modified files"	Verify immediately; then check Workshop subscriptions
Graphics card driver updated	No verification needed unless problems appear
Operating system reinstalled	No verification needed if install folder was preserved
Drive moved to a new machine	Verify after moving
Workshop subscription appears broken	Verify the base game first; then re-subscribe

The scenarios table above is a quick reference. Treat verification as a low-risk first step for any unexplained Unturned problem; if verification produces a clean result, the problem lies outside the install folder and the diagnostic moves elsewhere.

Advanced considerations

Several aspects of verification are worth understanding for users who plan to mod actively or who troubleshoot installs frequently.

Verification cannot fix all problems

Verification only addresses files that exist in the official manifest. Problems that originate outside the manifest are invisible to the verification process. These include:

• Corrupted save files in %AppData%\Unturned
• Conflicting third-party modifications installed via Workshop
• Driver issues affecting graphics or audio
• Operating-system level file-permission problems
• Antivirus quarantine of game files
• Network configuration affecting Steam connectivity
• Conflicts with overlay software like Discord or RivaTuner

Best practice

Always run a verification before opening a support ticket with Smartly Dressed Games or with a server operator. Many support requests are resolved by verification alone, and most support staff will ask whether you have verified before doing further diagnosis.

Frequency of verification

Verification does not need to be run on a schedule. It is a reactive maintenance procedure, not a preventive one. Run it when you observe a problem, after a Steam update that includes a large patch, or before a major mod-development session if you suspect something is off.

A common cadence among active modders is to run verification at three points: immediately after install, after any update marked as failed or interrupted, and before publishing or sharing a new mod release. The first two points address known sources of corruption; the third is a defensive practice that ensures a published mod was developed against a clean base game.

What verification leaves alone

Verification does not touch files outside the Unturned install folder. Your Workshop subscriptions, your save games in %AppData%\Unturned, and your custom maps stored in the Maps subdirectory are all preserved. Verification only operates on files that are part of the base game install.

Location	Touched by verification
<install folder>\Unturned.exe	Yes
<install folder>\Bundles\	Yes
<install folder>\Maps\<official maps>	Yes
<install folder>\Maps\<your custom maps>	No, if not part of the manifest
<install folder>\Workshop\	Yes
%AppData%\Unturned\Settings.json	No
%AppData%\Unturned\Players\	No
%AppData%\Unturned\Logs\	No
Steam Cloud saves	No
Workshop subscription metadata	No

The location table above shows the verification's effective boundary. Anything outside the install folder is unaffected; anything inside that is not part of the manifest is left in place. Custom maps and modder-added files inside the install folder are technically at risk of being deleted if Steam considers them out-of-place; in practice the modding workflow is to keep custom work outside the install folder where possible.

Verification through the command line

The Steam client supports a command-line verification trigger for advanced workflows. The command is steam://validate/304930 where 304930 is Unturned's App ID. Running this URI through the Windows Run dialog or through a desktop shortcut triggers a verification without opening the Properties dialog.

Trigger method	When to use
Properties to Installed Files to Verify	Default; works for every user
steam://validate/304930 Run command	Faster for users who verify frequently
Desktop shortcut to the validate URI	Even faster; one-click verification
Scripted from a batch file or PowerShell	For automated workflows that include verification

The command-line approach is a small productivity gain for modders who verify frequently. Most users never need it; the default Properties to Installed Files path is sufficient.

FAQ

How long does verification take?

One to five minutes for Unturned on a typical machine. The duration is gated by drive read speed because Steam reads every file from disk to compute its hash. An NVMe SSD verifies in about one minute; a SATA SSD takes about two minutes; a mechanical hard drive takes three to five minutes. Verification time scales roughly with the total install size, so larger games take proportionally longer.

Will I lose my settings if I run verification?

No. User settings are stored outside the install folder, in %AppData%\Unturned. Verification only affects files inside the install folder. Your graphics settings, control bindings, and saved server list are all preserved across a verification.

Will I lose my Workshop subscriptions if I run verification?

No. Workshop content is managed separately from the base game files and is not affected by verification. Your subscriptions remain registered and the subscribed content remains downloaded.

Verification re-downloaded several files. Is that bad?

Not necessarily. A handful of file mismatches is normal after a long period of use and is exactly the problem verification is designed to fix. Repeated mismatches across multiple verifications, however, suggest a deeper problem such as a failing drive or persistent antivirus interference.

Can I cancel a verification?

Yes. Right-click Unturned in the library and select Cancel from the context menu. The verification will halt, and any files already re-downloaded will remain. The verification itself does no harm to your install if cancelled, though you should run a fresh verification afterward to confirm the current state.

Can I run a verification while the game is open?

No. Steam cannot read or write files that the game has open. Close Unturned before starting a verification.

Does verification consume internet bandwidth?

A clean verification consumes a small amount of bandwidth for the manifest fetch (less than 1 MB). A verification that finds mismatches consumes additional bandwidth proportional to the size of the files being replaced. If you have an internet usage cap, a verification that re-downloads many files can be significant.

Should I verify after every Workshop subscription?

No. Workshop content is downloaded outside the verification pipeline and a verification is not necessary after subscribing. Verification is only relevant to the base game files.

Why does verification report different file counts on different runs?

Steam tracks the file count from the current manifest. If the manifest has been updated since your last verification, the file count may differ. This is normal and does not indicate a problem.

Can I verify a game I do not currently own?

No. Verification operates on installed games and requires the game to be present in your library. A game you do not own is not in your library and cannot be verified.

What does "successfully validated" mean precisely?

It means every file checked by Steam has a hash that matches the corresponding manifest entry. Steam reads every file in the install folder, computes a SHA-1 hash of each, and compares against the values in the manifest. A successful validation confirms the install matches what Valve published, byte for byte.

How does verification interact with anti-cheat?

Verification covers the Easy Anti-Cheat client files in the EasyAntiCheat subfolder. A verification that replaces anti-cheat files is the supported way to repair a damaged anti-cheat installation. Do not attempt to modify or replace EAC files manually; the verification path is the only supported repair.

Best practices

• Run a verification immediately after the first install
• Run a verification before opening any support request
• Back up manually edited game files before running verification
• Do not delete files from the install folder while Steam is running
• Treat repeated verification failures as a sign of deeper drive or filesystem problems
• Close Unturned before starting a verification
• Note the install size on the Installed Files tab as a quick sanity check
• Use the steam://validate/304930 URI for frequent verifications
• Run verification after any Steam update reported as failed or interrupted
• Verify after restoring from a backup or moving the install to a new drive

Appendix A: verification troubleshooting reference

The following table maps common verification failure modes to the most likely cause and the recommended response.

Symptom	Most likely cause	Recommended response
Verification reports many mismatches	Recent Steam update was interrupted	Allow Steam to re-download; verify again
Verification reports the same mismatches repeatedly	Drive write failure or antivirus interference	Check drive health; add Steam to antivirus exclusions
Verification stalls partway through	Antivirus is scanning every file read	Add Steam library folder to antivirus exclusions
Verification reports "missing file privileges"	Permissions on install folder are wrong	Right-click Steam folder, Properties to Security, grant full control
Verification cannot find the install	Drive containing the install is disconnected	Reconnect the drive and retry
Verification button is greyed out	Game is still installing or updating	Wait for current operation to complete
Verification button is missing	Game is not installed	Install first; verify after
Verification completes but launch still fails	Problem lies outside install folder	Check graphics drivers, anti-cheat state, user-data folder
Steam client crashes during verification	Steam client itself is corrupted	Repair Steam through the client installer
Internet connection drops during verification	Network failure	Wait for connection; verification resumes

The reference table above is the first place to check when a verification does not produce the expected result. Most verification problems map cleanly to one of these rows.

Appendix B: verification timing reference

The following table provides expected verification durations across common drive types. Durations assume a clean install with no mismatches; mismatch handling adds time proportional to the size of the replaced files.

Drive type	Verification duration (clean)	Verification duration (heavy mismatches)
NVMe SSD (PCIe 4.0)	About 30 seconds	1 to 2 minutes
NVMe SSD (PCIe 3.0)	About 45 seconds	1 to 3 minutes
SATA SSD	About 90 seconds	2 to 4 minutes
7200 RPM HDD	2 to 4 minutes	5 to 10 minutes
5400 RPM HDD	3 to 6 minutes	8 to 15 minutes
External USB SSD	1 to 2 minutes	3 to 6 minutes
External USB HDD	3 to 8 minutes	8 to 20 minutes

The timing reference above is a planning tool. If your verification runs significantly slower than the values in the table, the most common cause is antivirus interception; add the Steam library folder to your antivirus exclusion list and re-run.

Pro tip

A verification that takes more than twice the expected duration is a strong signal of antivirus interference. The antivirus is reading every file Steam reads, doubling the disk read load and slowing the entire process. The fix is a one-time configuration change in your antivirus software.

Appendix C: verification in a modding workflow

Verification has a specific role in a structured modding workflow. The following practices describe how active modders integrate verification into their day-to-day routines.

Before starting a new mod project

Run a clean verification before starting work on a new mod. This establishes a known-good base game state and ensures that any later problems can be traced to mod changes rather than base game corruption. The five minutes spent on a fresh verification at project start can save hours of mistaken debugging later.

Before publishing a mod release

Run a verification before publishing a new mod release to the Workshop. The verification confirms the base game state is clean, which means the mod you are publishing was developed against a published version of Unturned rather than an unintentionally modified base game. This is a small step that improves the reproducibility of mod work.

After any Steam update

Steam updates can include changes to manifest entries that retroactively reclassify files as mismatched. After a major Steam update, a verification is a quick sanity check that the post-update state is clean.

When mod loading is unexpectedly broken

If a mod that worked yesterday fails to load today, verification is the first diagnostic step. A verification that finds and replaces mismatched files often resolves the apparent mod-loading problem because the underlying cause was base game corruption affecting the mod loader.

Before reporting a bug to Smartly Dressed Games

Smartly Dressed Games support requests are commonly resolved by verification alone. Running a verification before reporting a bug confirms the install is clean and saves time for both you and the support team. The official documentation at https://docs.smartlydressedgames.com/en/latest/about/getting-started.html is the authoritative source for current support procedures.

Appendix D: verification and modding tools

Several modding tools have their own internal validation that complements Steam's verification. Understanding the relationship between these validations clarifies which tool to use when.

Validation source	What it validates	When to use
Steam verification	Files in the install folder against the official manifest	After installs, updates, or unexplained problems
Unturned Workshop subscription manager	Subscribed Workshop content downloaded correctly	When Workshop content fails to appear in game
Modding tool internal validators	Mod-specific schema and dependencies	When developing a mod that has its own structure rules
Server kick messages	Files differ from server expectations	When kicked from a multiplayer server for "modified files"

The validation source table above shows the layered model. Steam's verification is the outermost layer, addressing base game integrity. Workshop subscriptions, mod tools, and server checks add additional layers focused on specific concerns.

Best practice

Treat Steam verification as the foundation of any deeper validation work. If Steam verification reports problems, address those first before investigating Workshop or mod-tool validation. Most layered validation problems stem from base game corruption that propagates upward.

Appendix E: verification log files

Steam maintains a log of every verification operation. The log files live in the Steam client's logs directory at <Steam install>\logs. For default Steam installations this is C:\Program Files (x86)\Steam\logs.

Log file	What it contains
content_log.txt	High-level record of download and verification operations
bootstrap_log.txt	Steam client startup events
cloud_log.txt	Steam Cloud sync operations
connection_log.txt	Network connectivity events
parental_log.txt	Steam family controls events
stderr.txt	Error output from the Steam client

The content log is the most useful log for verification troubleshooting. It records the start time, file count, and outcome of every verification. Reading the content log is sometimes the fastest way to confirm what happened on a recent verification, especially if the Library tile state has been replaced by a more recent event.

Pro tip

The content log is plain text and can be opened in any text editor. Search for "Unturned" or for the App ID 304930 to locate Unturned-specific verification entries quickly. The log entries include timestamps and outcome strings that map directly to the outcomes documented earlier in this article.

Appendix F: verification and the Smartly Dressed Games documentation

The official Smartly Dressed Games documentation at https://docs.smartlydressedgames.com/en/latest/about/getting-started.html is the authoritative reference for Unturned-specific support procedures. The 57 Studios Knowledge Base is written to complement this documentation, not to replace it.

When the knowledge base and the official documentation disagree, the official documentation wins. This article aligns with the official documentation as of its most recent update; future changes to the Smartly Dressed Games procedures will be reflected in subsequent knowledge base updates.

The verification procedure described here is generic Steam behaviour and is not Unturned-specific. The same procedure applies to any Steam-managed game, with the relevant App ID substituted. The references to Unturned's App ID 304930 are the only Unturned-specific elements; everything else generalises.

Appendix G: verification mental model

The mental model for verification is a three-part comparison: the file on disk, the manifest entry, and the source on the CDN. A successful verification confirms that the first matches the second. A failed verification triggers a replacement of the first from the third.

                              The Unturned verification mental model


          +-------------------+         +-------------------+         +-------------------+
          |                   |         |                   |         |                   |
          |  FILE ON DISK     |  ====>  |  MANIFEST ENTRY   |  ====>  |  CDN SOURCE       |
          |  (your install)   |         |  (signed by Valve)|         |  (replacement)    |
          |                   |         |                   |         |                   |
          +-------------------+         +-------------------+         +-------------------+
                  |                              |                              |
                  | Hash computation             | Authoritative reference      | Replacement source
                  | by Steam client              | fetched fresh per run        | for any mismatch
                  |                              |                              |
                  v                              v                              v
                                     +-------------------+
                                     |                   |
                                     |  COMPARISON       |
                                     |  AT CHUNK LEVEL   |
                                     |                   |
                                     +-------------------+
                                                |
                                                v
                                     +-------------------+
                                     |                   |
                                     |  OUTCOME          |
                                     |  (clean / reacq / |
                                     |   failed)         |
                                     |                   |
                                     +-------------------+

The diagram above shows the three nodes and the comparison that produces the outcome. Verification is a closed loop with a clear input (files on disk), a clear reference (manifest entries), and a clear remediation path (CDN re-download). The simplicity of the loop is why verification is such a useful first diagnostic step for any Unturned problem.

Appendix H: glossary of verification terms

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

• Chunk — A unit of game data with its own hash entry in the manifest. Steam verifies and re-downloads at the chunk level rather than the file level.
• Hash — A cryptographic fingerprint of a file or chunk. Steam uses SHA-1 hashes in its manifests.
• Manifest — The authoritative file listing every game file, its expected hash, and the chunks that compose it. The manifest is signed by Valve and fetched from the CDN at verification time.
• Mismatch — A condition in which a file on disk has a different hash than the manifest entry. Mismatches trigger re-download.
• Reacquired — Steam's term for a file that was re-downloaded to replace a mismatched version.
• Verification — The process of comparing every file on disk against the manifest and triggering replacement for any mismatch.
• App ID — The unique numeric identifier Steam assigns to each published game. Unturned's App ID is 304930 and appears in the manifest filename and in command-line URIs.

The glossary above is the vocabulary that the rest of this article builds on. Subsequent articles in the section assume familiarity with these terms.

Appendix I: verification across multiple Steam library folders

If you have configured multiple Steam library folders on different drives, verification operates on whichever library folder currently contains Unturned. Steam tracks the current install location through its internal records and reads files from that location during verification. You do not need to specify the library folder; Steam locates the install automatically.

Library folder configuration	Verification behaviour
Default library folder only	Verification reads from C:\Program Files (x86)\Steam\steamapps\common\Unturned
Secondary library on D drive	Verification reads from D:\SteamLibrary\steamapps\common\Unturned
Game recently moved between folders	Verification reads from the new location
Library folder marked as missing	Verification fails until the drive is reconnected

The library folder behaviour above is the same as the install behaviour from the previous article. Verification is unaware of where Steam decided to install the game; it operates on whatever path Steam currently records.

Pro tip

After moving Unturned between library folders, run a verification on the new location. The move operation is reliable, but a verification is a small extra step that confirms the moved files are intact.

Verifying after a library folder migration

Library folder migrations through the Move install folder feature are the supported way to relocate a game. The migration copies every file and updates Steam's internal records. A verification immediately after the migration confirms the copy completed without corruption.

The migration is not common, but several scenarios call for it: moving Unturned to a newly-purchased SSD, consolidating multiple library folders, or relocating off a failing drive. In each scenario the migration plus verification combination is the recommended sequence.

Appendix J: verification and ongoing maintenance

Verification has a maintenance role in addition to its diagnostic role. Several maintenance patterns are worth noting.

Monthly cadence for active modders

Modders who use Unturned daily for development benefit from a monthly verification cadence. The verification catches gradual corruption that accumulates over time and confirms the base game state is clean for ongoing work. The five minutes per month is a small investment.

Quarterly cadence for casual users

Casual users who play Unturned recreationally benefit from a quarterly verification. The longer cadence reflects the lower exposure to potential corruption sources; casual play does not stress the install in the same way active modding does.

After major Steam events

Run a verification after any of the following Steam-level events:

• Steam client major update
• Steam Cloud account migration
• Steam library folder reorganisation
• Steam family-sharing configuration change
• Operating system update that includes filesystem changes

These events are not common, but each one creates a small risk that the install state on disk has drifted from the manifest. A verification confirms the drift is absent or fixes it.

Before major mod-development milestones

Run a verification before any of the following mod-development milestones:

• Starting a new mod project
• Publishing a mod release to the Workshop
• Submitting a mod to a curated server's whitelist
• Recording video documentation of a mod
• Sharing a mod build with a collaborator

The verification at these milestones is a defensive practice. It confirms that the work being shipped or shared was developed against a clean base game, which improves the reproducibility of the mod across other modders' machines.

Appendix K: verification edge cases

Several edge cases are worth documenting for completeness. These cases are uncommon but each one has been observed in real-world support requests.

Verification while a Workshop subscription is downloading

Steam handles Workshop downloads and game verification as separate operations. You can run a verification while Workshop content is downloading; the two operations do not interfere. The verification proceeds at full speed and the Workshop download continues in parallel.

Verification with a slow network connection

A verification that finds many mismatches needs to re-download replacement files. On a slow connection this can extend the verification time significantly. If you have an internet usage cap, a heavy-mismatch verification can consume a noticeable fraction of your monthly cap.

Internet speed	Re-download time for 100 MB of mismatches
5 Mbps	About 3 minutes
25 Mbps	About 30 seconds
100 Mbps	About 10 seconds
1 Gbps	About 1 second

The re-download timing table above is the practical reference for planning a verification on a constrained network. Most verifications do not find significant mismatches, so the re-download time is rarely a planning consideration.

Verification on a drive with low free space

Verification needs enough free space to write replacement files during the re-download phase. If the drive is nearly full, the verification may fail partway through with a disk-write error. The recommended threshold is 1 GB of free space on the install drive before starting a verification; less than that is a risk.

Verification during a Steam outage

Steam's CDN occasionally has regional outages. A verification during an outage may stall on the manifest fetch and produce a connection error. Wait for the outage to resolve, then retry. The Steam server status is publicly visible through third-party status pages.

Verification of a backed-up install

Some users back up the entire Unturned install folder to external storage before performing potentially-risky modding work. Restoring from the backup followed by a verification confirms the restored state matches the manifest. The verification path is the supported way to confirm a backup restore.

Verification with multiple Steam accounts on the same machine

Each Steam account on a shared machine has its own library state. A verification operates on the account currently signed in. If multiple accounts share the same physical install (because Steam library folders are filesystem-level rather than account-level), verifying from one account verifies the shared install for all accounts.

Appendix L: verification and security

Verification has a small but real security role. The manifest is signed by Valve, and a successful verification confirms that the installed files match what Valve published. This protects against several threats.

Tampering by malware

Malware that modifies game files to inject code is detected by verification because the modified files no longer match the manifest. A verification that consistently reports mismatches in unusual files (executables, anti-cheat files) is a signal worth investigating with security tools.

Tampering by the user

Modders sometimes modify game files intentionally for testing purposes. These modifications are also detected by verification, which restores the files to their published state. The behaviour is the same whether the modification was malicious or intentional; Steam does not distinguish between the two.

Detection of disk corruption

Disk corruption that silently changes file contents is detected by verification. A verification that finds mismatches without any explanation for why the files would have changed is a signal that the drive may be failing. Use drive health tools to investigate.

Tampering source	Verification detection	Recommended response
Malware injection	Yes, mismatches in unusual files	Run security scan; allow Steam to replace files
Intentional user modification	Yes, mismatches in modified files	Back up modifications first; run verification
Disk corruption	Yes, random mismatches without explanation	Check drive health with SMART tools
Workshop content	No, Workshop content is outside the manifest	No action needed
Steam update interrupted	Yes, mismatches in updated files	Allow Steam to re-download

The security table above shows the verification's detection capabilities. Most users will never encounter tampering, but the verification provides a useful baseline that can detect unusual changes when they occur.

Common mistake

Some modders disable verification or attempt to skip it to preserve intentional modifications. This is unsupported and creates a confusing development environment where the base game state cannot be trusted. The supported pattern is to make modifications outside the install folder (in a separate mod project directory) and to keep the install folder pristine.

Appendix M: verification and the install pipeline

Verification is the second step of a four-article install pipeline within this section of the knowledge base. The four articles together form a coherent install workflow:

1. How to Install Unturned — the install procedure
2. How to Verify Unturned Game Files — this article
3. How to Find Your Unturned Install Folder — locating the install on disk
4. Where Steam Installs Games by Default — the library folder model
5. How to Launch Unturned for the First Time — first-launch initialisation

Each article in the pipeline assumes the previous articles have been read and the recommended steps completed. A reader who skips the verification step in this article may encounter problems later that would have been caught earlier; a verification is a small investment that prevents downstream debugging.

Best practice

Treat the install pipeline as an unbroken sequence on first read. The four articles together build the prerequisites for the file-management section that follows, which in turn builds the prerequisites for the modding sections. Skipping articles in the pipeline creates gaps that surface later as confusing problems.

Cross-references

• How to Install Unturned — the prerequisite article on installing the game
• How to Find Your Unturned Install Folder — the next article in the install pipeline
• Where Steam Installs Games by Default — context for the install location displayed on the Installed Files tab
• How to Launch Unturned for the First Time — the article that closes the install pipeline

Document history

Version	Date	Author	Notes
1.0	2024-09-14	57 Studios	Initial publication of the verification article
1.1	2024-12-03	57 Studios	Added scenario-based decision flowchart and best-practice list
1.2	2025-03-18	57 Studios	Added verification troubleshooting reference table
2.0	2026-05-17	57 Studios	Major expansion. Added timing reference, modding-workflow integration, log file appendix, verification mental model, and glossary. Expanded FAQ from 5 to 12 questions.

Next steps

With Unturned verified and confirmed healthy, proceed to How to Find Your Unturned Install Folder to learn how to locate the game directory on disk.