Save Game Compatibility: Versions, DLC and Mods Explained

A matching game title is the beginning of a compatibility check, not the end. Two players can own the same game while using different editions, builds, storefronts or mod environments. A good save description makes those differences visible before anyone replaces a working checkpoint.

Start with a precise identity

Record the game title, edition and platform, followed by the actual build and storefront where relevant. Replace vague phrases such as “latest patch” with an exact version that remains meaningful later. State the source of the information: uploader notes, in-game details or your own test.

Do not treat undocumented information as a confirmed match. When a package does not identify its build or dependencies, mark them as unknown. That is more useful than silently assuming the most convenient answer.

Compare DLC and mods explicitly

List the additional content and mods the save provider identifies as required. Distinguish “not used” from “not documented.” A statement that no mods were used is a specific claim; an empty field does not establish the same thing.

For a modded save, record the relevant versions and profile details. Avoid concluding that two setups match because they contain a similar number of mods. Names, versions and the documented environment matter more than a broad label such as “modded.”

Preserve the complete package

Compatibility checking is harder when the files have already been separated or renamed. CD PROJEKT RED’s Cyberpunk 2077 support instructions, for example, request several files from a save directory rather than just a screenshot or a single convenient filename. Keep the package structure intact until the role of each component is understood. 1

An archive’s descriptive text should stay with the files during your test. Keep an unchanged original alongside the working copy so that the test can be explained or repeated later.

Use a simple comparison record

Record each important item as a source value, destination value and result: matched, different or unknown. Include the edition, game build, storefront, DLC, mods and active profile. Add the checkpoint you intend to test and the location of your rollback copy.

This is a decision aid, not an automated compatibility engine. A matched checklist narrows uncertainty, but it does not prove that every quest or long-term play session will behave correctly.

Test a narrow, reversible claim

1. Back up the destination’s current saves outside their active location.
2. Import one identified checkpoint using the documented structure.
3. Load it and inspect the expected character, quest or world state.
4. Record any warnings, missing content or unexpected behavior.
5. Create a separate test save and load it again.
6. Report the exact environment and checks performed.

A responsible description might say that a checkpoint loaded and re-saved on one specified setup. It should not become “works on all versions” without evidence covering that claim. Keep unresolved requirements visible and retain your original progress while testing.

Frequently asked questions