NieR Replicant stores its Steam PC data beneath a user-ID directory, which is useful because it keeps different Steam accounts separated but also makes casual copy/paste mistakes easier. Community troubleshooting shows that persistent completion state can survive in shared game-data files, so a single character slot is not a complete backup strategy. SaveEditor recommends copying the whole user-ID directory, keeping Steam Cloud state in mind, and restoring files from the same snapshot rather than mixing a new slot with old global data.
Known NieR Replicant ver.1.22474487139… save-file structure
The researched filename or folder pattern is Game and system data are stored inside the Steam-user-specific save directory; community reports commonly reference GAMEDATA among the persistent files.. File-extension context: No single extension is sufficient to identify every relevant save record. The documented format notes are: The remaster stores PC progress under a Steam user ID directory in Documents. Some persistent state can remain outside the currently selected character slot, so folder-level backup is safer than removing one file.
Why an extension is not enough
A save filename can identify a likely container, but it does not prove the internal schema, game version, checksum rules, encryption state, or editability. Persistent completion/system state may be stored alongside character saves. Deleting a file to reset one behavior can have broader consequences and cloud sync may restore it. SaveEditor therefore separates file identification from Tool compatibility and only labels a game-specific Tool Verified when its exact profile/version evidence passes the runtime gate.
Where the format is stored
PC save locations: Windows: %USERPROFILE%DocumentsMy GamesNieR Replicant ver.1.22474487139Steam<user-id>. Storefront context: Steam. The save directory is Steam-account-specific. Do not merge files from different user-ID folders without keeping a known-good copy of each set. This matters because two releases can use different containers or companion files even when the visible slot name is similar.
Back up before inspecting or editing
Close the game and Steam synchronization, then copy the entire user-ID directory. Keep a dated untouched copy before experimenting with GAMEDATA or individual slot files. A read-only viewer is lower risk than a writer, but the live save should still be copied first. Cloud context also matters: Steam Cloud can re-download deleted or replaced files when synchronization is enabled. Keep the original bytes available so any experiment can be reversed without relying on a cloud service or automatic backup.
What this reference does not claim
This page does not infer an undocumented checksum algorithm, encryption key, compression layer, or cross-store conversion from the file extension. Troubleshooting evidence: If deleted data reappears, check Steam Cloud. If a save is reported corrupt after a manual replacement, restore the full matching backup set instead of mixing files from different dates. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.
Verification context: Reviewed against current PCGamingWiki NieR Replicant save path and community reports describing persistent GAMEDATA/cloud behavior.