VERIFY THE FILEA save download should arrive with a clear description of its contents and requirements. Before placing it beside your own progress, inspect the archive and preserve a backup. A checksum can help detect an unexpected file change, but it cannot certify that a file is harmless or compatible with your game.
Check the source and description
Look for the exact game, intended checkpoint, supported environment and any required DLC or mods. Treat “safe,” “100%” and “tested” as claims that need details, not as substitutes for evidence. Avoid packages that demand unrelated software, an unfamiliar executable or disabled security controls merely to copy save data.
Keep the original downloaded archive unchanged. Extract a separate copy into a temporary folder and inspect the files before copying anything into an active save directory.
Display complete filenames
Windows can hide familiar filename extensions. Microsoft’s documentation explains common extensions and how to view them. Check the full filename so that a misleading display name does not cause you to mistake an executable or unrelated file for save data. 1
Do not rename an extension to make a suspicious file look like a save. Confirm what the game normally expects and preserve companion files whose purpose is documented. When the archive structure differs from the description, stop and investigate.
Calculate a SHA-256 hash
Microsoft’s Get-FileHash command can calculate a file hash. The following example uses SHA-256 explicitly. Replace the example path with the actual archive you downloaded; the command reads that file and returns its hash. 2
Get-FileHash -Algorithm SHA256 -LiteralPath "C:\Downloads\your-save-archive.zip"
Compare the entire hash with the value published for the exact same file. Check that you are hashing the archive when the reference describes the archive, rather than a file extracted from inside it. A single different character means the values do not match.
Understand the limit of the result
A matching hash establishes that the compared bytes match the reference hash, not that the file is safe to execute or appropriate for your installation. The value is only as trustworthy as the reference used for comparison. Do not treat a checksum displayed beside a download as an independent security review.
A mismatch is a reason to stop and investigate the file version, download integrity and reference. Do not replace the expected hash with the one you calculated merely to make the check pass.
Test only after preserving your own progress
Use your normal security checks, inspect the contents and verify the game’s requirements. Then back up your active saves independently and test one checkpoint with a rollback copy available. Check loading, expected progress and a separate save-and-reload cycle.
For an upload, publish the SHA-256 of the final archive actually distributed. Changing or repacking it changes the file being described and requires a corresponding new checksum. State what security or compatibility testing was genuinely performed rather than implying that a hash performed those tests automatically.
Frequently asked questions
Does a matching SHA-256 mean the archive is malware-free?
No. It is an integrity comparison against a reference, not a malware scan or a compatibility certificate.
Should I compare the ZIP hash with a hash for an extracted save?
No. Compare like with like: the same exact file described by the published reference.
Sources and scope
Reference paths and features can vary by edition, storefront and system configuration. The backup and testing checklists are SaveGamesDL editorial guidance; no downloadable save was tested for this article.
