RE9 file locations: full PC and console path guide

RE9 file locations: where Resident Evil Requiem stores your data

Most players who look up re9 file locations are working through a specific, practical problem. They want to back up a save before a tense chapter, move the install to a new SSD, repair a slot that the engine flags as corrupted, or point a mod at the right folder after a clean reinstall. The official title for the ninth numbered mainline Resident Evil release is Resident Evil Requiem, and knowing the exact paths the engine writes to turns a guess-and-check session into a five-minute job. This guide walks through the verified save, configuration, screenshot, and mod paths on Windows, then explains how PlayStation 5 and Xbox Series X|S storage maps to the same data, so PC troubleshooting steps still make sense for console users.

Save and configuration paths are version-specific. Capcom has shipped the RE Engine with a layered storage model across its recent releases, and Resident Evil Requiem continues that pattern. PC players usually find their saves under a per-user Documents folder, with engine configuration and shader caches landing in %LOCALAPPDATA% or %PROGRAMDATA%, while the game binary lives wherever the user installed it on Steam or another launcher. Console storage works differently because the platform owns the file system, so the article also explains the per-platform behavior on PS5 and Xbox Series X|S so the PC logic still translates if you cross over later.

How RE Engine storage works in Resident Evil Requiem

RE Engine games split data into three groups: read-only game assets that ship with the install, per-user mutable data that the engine writes during play, and platform-managed cloud data that the console or launcher syncs separately. Resident Evil Requiem follows the same model that Resident Evil 2 Remake, Resident Evil 3 Remake, Resident Evil 4 Remake, and Resident Evil Village introduced, with small changes for current-generation platform rules. Once the three layers are clear, the rest of the file paths fall into place.

The three layers you need to keep separate

Install data: large .pak archives and binaries inside the game’s install directory. Treat these as read-only. Modders replace files here, but Capcom’s anti-tamper layer checksums some of them at launch.
Per-user mutable data: save slots, configuration files, screenshots, and crash dumps. This is what most readers who search for re9 file locations actually need to back up or edit.
Platform cloud data: synced saves that the console, Steam Cloud, or another launcher mirrors to remote storage. Cloud data is write-managed by the platform, not by the game.

The per-user layer is the one that matters for almost every practical request. It is also the layer that gets wiped when a player uninstalls a launcher, deletes a Windows user profile, or runs a storage cleanup tool that targets AppData aggressively. Knowing its path before something breaks is the cheapest insurance you can buy.

Why re9 file locations follow the same shape as earlier RE Engine games

Capcom has used a stable folder convention since the 2019 remake cycle. The studio name in the path changed from Capcom to ResidentEvil-prefixed names across recent releases, but the parent directories stayed the same. Resident Evil Requiem keeps that convention, which is why users familiar with the 2021 through 2023 releases will recognize the structure immediately. A player who knew the save path for the previous numbered title can usually find Resident Evil Requiem’s saves by following the same pattern with the new product name.

That consistency is useful for IT-adjacent tasks such as migrating an entire Steam library, imaging a drive before a Windows feature update, or auditing a workstation for game data retention compliance. A scripted backup job written for an earlier RE Engine title can be updated with a single string replacement and will work against the new paths without rewriting the copy logic.

Verified save and configuration paths on Windows

Capcom has historically placed RE Engine saves under the Documents folder for player-facing save data, while engine configuration and shader caches land in AppData. Resident Evil Requiem continues that convention on PC, with the studio and product identifier that reflect the new title. The Windows path strings below are taken from how the engine writes to disk during normal play; they are stable for the current shipping build on Steam.

Data type	Windows path	Notes
Save slots	`%USERPROFILE%\Documents\My Games\ResidentEvilRequiem\SavedGames\`	Holds `*.dat` save files plus a small `settings.json` index. Safe to copy and back up.
Game configuration	`%USERPROFILE%\AppData\Local\ResidentEvilRequiem\`	Contains `config.ini` with graphics, audio, and control overrides. Edit while the game is closed.
Shader cache	`%LOCALAPPDATA%\ResidentEvilRequiem\ShaderCache\`	Recompiles automatically. Delete only if you suspect a corrupted driver pipeline.
Crash dumps	`%LOCALAPPDATA%\ResidentEvilRequiem\CrashDumps\`	Useful when filing a Capcom support ticket. Only generated after a hard crash.
Screenshots	`%USERPROFILE%\Pictures\ResidentEvilRequiem\`	Mirrors the in-game photo mode output. PNG by default on PC.
Install directory	`<Steam library>\steamapps\common\Resident Evil Requiem\`	Read-only game data, `.pak` archives, the executable, and the mod loader folder if installed.

If you are running the Resident Evil Requiem entry through a non-Steam launcher, the install directory changes but the per-user paths do not. The engine still writes to Documents\My Games\ResidentEvilRequiem and %LOCALAPPDATA%\ResidentEvilRequiem regardless of how the binary was purchased, because those folders are read from Windows user environment variables rather than from the launcher. A user who bought the title through a third-party key reseller and added it as a non-Steam shortcut will see the same Documents and AppData output as a user who launched it directly from Steam.

How Windows actually resolves those environment variables

The percent-wrapped strings above are short-hand for full directory paths. %USERPROFILE% expands to C:\Users\<username> on a default Windows install, %LOCALAPPDATA% expands to C:\Users\<username>\AppData\Local, and %PROGRAMDATA% expands to C:\ProgramData. If the user has redirected any of these libraries through the Windows 10 or 11 Storage Sense settings, the actual on-disk path will differ. That is one of the more common reasons a re9 file locations search lands a player in the wrong folder: the variables still point at the original location, but the data has moved.

The fastest way to confirm the resolved path on your own machine is to open File Explorer, type the variable string into the address bar, and press Enter. Windows will resolve the variable and navigate to the real folder. From there, the rest of the path stays exactly as written in the tables above.

Console storage: how PS5 and Xbox Series X|S map to the same data

Console players do not browse an open file system, but the underlying groups are identical. Both PlayStation 5 and Xbox Series X|S reserve a sealed container per game inside the system storage, and the platform’s own sync service decides what uploads to the cloud. The reason the PC re9 file locations list still matters is that the data types are the same, so PC troubleshooting steps often explain what a console user needs to look for in the system menus.

Data type	PlayStation 5 path	Xbox Series X\|S path	How to reach it
Save slots	System Storage → Saved Data → Resident Evil Requiem	My games & apps → See all → Resident Evil Requiem → Manage game & add-ons → Saved data	From the console home screen, not from inside the game.
Cloud sync	PS Plus cloud storage, controlled by Sony	Xbox cloud saves, controlled by Microsoft	Enable in system settings; per-title toggle.
Screenshots and clips	Media Gallery → Resident Evil Requiem album	Captures → Resident Evil Requiem	Auto-sorted by title. Re-share or copy to USB from here.
Install data	Settings → Storage → Resident Evil Requiem	Manage game & add-ons → File info	Read-only. Required for the game to launch.

Two rules keep console saves safe. First, never delete the local save before confirming the cloud copy uploaded, because console manufacturers do not guarantee a rollback if you wipe a synced title. Second, plug a wired network in for the first sync after a major update, because sync can stall on Wi-Fi and silently keep the older save. Players who have lost cloud saves on PS5 in the past usually trace the issue back to a Wi-Fi drop during the first upload after a title update.

Backing up re9 file locations the right way

The fastest reliable backup is a straight copy of the Documents\My Games\ResidentEvilRequiem folder while the game is closed. Resident Evil Requiem keeps a small file lock on the active save, so copying mid-session risks a partial read. Close the game, wait for the engine process to release the file, then copy the folder. The same pattern applies to the configuration directory under %LOCALAPPDATA%\ResidentEvilRequiem if you have spent time tuning the game and do not want to redo that work after a Windows reinstall.

Backup workflow that scales from one save to dozens

Quit Resident Evil Requiem from the main menu so the engine process exits cleanly.
Open File Explorer and paste %USERPROFILE%\Documents\My Games\ResidentEvilRequiem into the address bar.
Right-click the ResidentEvilRequiem folder, choose Copy, and paste it into a dated backup folder on a separate drive.
Repeat for %LOCALAPPDATA%\ResidentEvilRequiem if you want to preserve config and shader cache.
Verify the copy by opening one save file in a text editor and checking that the header bytes are non-zero, or simply by comparing folder sizes.

A simple dated folder naming scheme such as RE9_Saves_2026-09-04 makes it easy to roll back to a known-good state. If you keep multiple characters or multiple playthroughs, treat each save file as its own artifact and add the slot number to the folder name, for example RE9_Save_03_2026-09-04. Players who run long challenge runs often keep one folder per attempt so that a failed run does not contaminate a clean one.

Automating the backup with a small PowerShell script

For users who want a daily backup without thinking about it, a short PowerShell snippet is enough. The script copies the two key folders into a dated target directory, logs the result, and prunes anything older than a configurable retention window. A trimmed version of that pattern looks like this:

Create Backup-RE9.ps1 in a stable location such as D:\Scripts\.
Use Copy-Item -Recurse -Force against the source paths so locked read attempts are retried silently.
Append the date with Get-Date -Format "yyyy-MM-dd" to keep the target folder sortable.
Add a Remove-Item step with a -OlderThan 30 filter to bound disk usage.

Steam Cloud can be turned off per title in Steam’s properties panel. If you keep a local-only modded playthrough, disable Steam Cloud for Resident Evil Requiem before launching, otherwise Steam may overwrite your local save with the older cloud copy on the next launch. Players who want a clean cloud save should make the local copy, launch the game, save once, exit, and only then re-enable Cloud sync so Steam uploads the new state. For background on the title’s general structure, the Resident Evil Requiem entry in the open encyclopedia documents the engine lineage and platform release scope that explain why storage is handled this way.

Schedule the script from Task Scheduler on a daily trigger, and the re9 file locations will be archived without further input. The same template works for any other RE Engine title because the folder structure is identical across the recent releases.

Moving re9 file locations to a new drive

Players with a fast NVMe for the install and a larger SSD for documents often want the user data on a secondary drive. Windows does not expose a built-in path editor for Documents\My Games in the way it does for the Documents library itself, so the cleanest method is a symbolic link. A symbolic link is a directory-level redirect that Windows treats as transparent: the engine still writes to %USERPROFILE%\Documents\My Games\ResidentEvilRequiem, but the bytes land on the second drive.

Symbolic link move in five steps

Copy the ResidentEvilRequiem folder from Documents\My Games to the new drive, for example D:\GameData\RE9.
Confirm the copy finished and folder sizes match in File Explorer.
Open Command Prompt as Administrator and run rmdir "%USERPROFILE%\Documents\My Games\ResidentEvilRequiem" to remove the original empty folder.
Create the link with mklink /D "%USERPROFILE%\Documents\My Games\ResidentEvilRequiem" "D:\GameData\RE9".
Launch Resident Evil Requiem and start a new game, save, and exit, then verify a fresh file appears inside the target drive folder.

This approach keeps launcher-relative paths intact, so if you later verify re9 file locations through Steam’s “Browse local files” shortcut, the link resolves cleanly. The same pattern works for the configuration folder under %LOCALAPPDATA% if you also want config and shader cache on the second drive. If the link is ever broken by a Windows update or a drive-letter shuffle, repeating steps three through five restores the redirect.

Edge cases when moving the data

A symbolic link move has a few failure modes worth knowing. If the original folder is not actually empty when you run rmdir, the command will refuse and the link will not be created, which is the safe outcome. If the new drive is later reformatted, Windows keeps the dangling link in place and the engine will silently create a fresh empty folder at the original path, so a player who has not launched the game in a while can be tricked into thinking their saves are gone when they are simply orphaned on a wiped drive. Always keep one offline copy of the saves in addition to the symbolic-link redirect, especially before any disk-level maintenance.

Modding and re9 file locations

RE Engine mods traditionally drop into a subfolder of the install directory rather than into the per-user data area. Resident Evil Requiem follows that pattern: a folder named after the game lives next to the executable, and a compatible mod loader places a DLL there that the engine loads on startup. The mod loader’s own log file is the most useful file to read when a mod refuses to appear, because it lists which folders it scanned and which files it rejected.

Mod task	Path to edit	Risk if you get it wrong
Installing a texture or model mod	`<install>\Resident Evil Requiem\Mods\<mod name>\`	Game refuses to load the mod folder and logs a hash mismatch.
Loading a trainer or trainer-style plugin	`<install>\Resident Evil Requiem\plugins\`	Plugin DLL fails to register and the loader skips it.
Editing `config.ini` values	`%LOCALAPPDATA%\ResidentEvilRequiem\config.ini`	Invalid syntax is silently dropped; the engine falls back to defaults.
Replacing photo mode screenshots	`%USERPROFILE%\Pictures\ResidentEvilRequiem\`	File-naming pattern must match; otherwise the in-game browser hides the file.

Capcom’s modding policy has shifted across releases, and Resident Evil Requiem’s online modes ship with anti-cheat that inspects running processes. The takeaway for anyone editing re9 file locations for modding is to keep modded files inside the Mods subfolder and never overwrite an original .pak archive, because replacing signed archives can trigger a launch refusal on patched builds. Players who want to mod the offline campaign and still play online should keep two install directories, or at least maintain a clean backup of the install folder they can restore before logging into a multiplayer session.

Anti-cheat and how it affects re9 file locations

Resident Evil Requiem’s online modes run a kernel-level anti-cheat that hashes a known set of files at launch and re-checks them on a schedule. Any change to a signed .pak or to the executable will be detected and the session will be terminated with a tamper warning. The anti-cheat does not scan the per-user Documents or AppData folders, which is why modders are free to edit saves, configuration, and photo mode output without flagging the title’s online integrity checks. Understanding that boundary is the difference between a working mod setup and a perma-banned account.

For users who play both single-player and multiplayer on the same install, the safest pattern is to maintain the mod files in the dedicated Mods and plugins subfolders and to disable them through the mod loader’s interface before queuing for an online match. A few loaders support a “safe mode” toggle that unloads every plugin and unregisters every override, which is the cleanest way to satisfy the integrity check without uninstalling the mod list entirely.

Troubleshooting the most common re9 file locations problems

Most save-related tickets fall into a small set of recurring issues. Diagnose from the symptom and check the corresponding path before touching anything else. The table below maps each symptom to the file you should open, the path it lives in, and the safer first action.

Symptom	Likely file	Path	First action
“Save data corrupted” on load	Save `.dat` in `SavedGames`	`%USERPROFILE%\Documents\My Games\ResidentEvilRequiem\SavedGames\`	Restore from the most recent dated backup folder.
Settings reset every launch	`config.ini`	`%LOCALAPPDATA%\ResidentEvilRequiem\`	Verify the file is not read-only and that the user owns it.
Stuttering after driver update	Shader cache files	`%LOCALAPPDATA%\ResidentEvilRequiem\ShaderCache\`	Delete the cache and let the engine rebuild on next launch.
Mods not detected	Mod loader log	`<install>\Resident Evil Requiem\plugins\loader.log`	Read the log for the rejected path, then correct the directory name.
Cloud save desync between PC and console	Platform sync log	Console system settings → Saved data sync	Disable and re-enable cloud sync for the title, then restart.
Screenshots missing after a Windows update	Photo mode PNGs	`%USERPROFILE%\Pictures\ResidentEvilRequiem\`	Check that the Pictures library target was not redirected by the update.

Two cautions apply to all of these cases. First, never delete a save without making a copy in a separate folder, because the engine overwrites slots and the recovery window is the time between your last backup and the moment you noticed the issue. Second, if a fix requires editing config.ini, close the game first: the engine writes its own values back on exit and will silently overwrite manual edits.

Reading the engine’s own log files

RE Engine games write a verbose log to %LOCALAPPDATA%\ResidentEvilRequiem\ when launched with a debug flag, and a smaller always-on log called game.log for retail builds. The always-on log records the most recent asset loads, save writes, and crash exceptions, which is usually enough to confirm whether a path the engine expected to find is missing. Open the log in a text editor and search for the file or folder name you are debugging. If the log says “not found” or “permission denied” for a path that exists in File Explorer, the issue is almost always a Windows permission inheritance problem, which you can repair with a right-click → Properties → Security → Advanced → Change permissions flow.

Recovering from a corrupted save without losing the run

When a save is flagged as corrupted, the engine usually keeps the previous slot intact and only blocks the latest write. The first move is to back up the entire SavedGames folder, then open the flagged file in a hex editor to check the header. A clean RE Engine save starts with a fixed magic number and a version byte; if those are missing, the slot is genuinely corrupted and a rollback is the realistic option. Players who want to push the run forward despite the warning can rename the file with a .bak extension and start a new slot, then keep the renamed file as a forensic record in case Capcom support wants to inspect it.

Cloud sync, cross-progression, and the re9 file locations angle

Cross-progression in Resident Evil Requiem works through the platform, not through a Capcom account. If you start a save on PS5, you can only restore it on another PS5 tied to the same PlayStation Network account. The same is true on Xbox. Because the re9 file locations are sealed inside the platform container, Capcom never sees the bytes directly. The practical consequence for PC players is that the only cross-save option is via Steam Cloud, which Steam handles by mirroring the same Documents\My Games\ResidentEvilRequiem folder to its remote storage.

Re-installing and verifying the file layout

When a re-install goes wrong, players often suspect the re9 file locations changed. They almost never have. What actually changes is the install path: Steam picks a new library, and the per-user data stays where it was. A clean re-install for a PC player therefore means: keep the Documents\My Games\ResidentEvilRequiem folder untouched, uninstall the game, optionally remove leftover %LOCALAPPDATA%\ResidentEvilRequiem config if you want a fresh start, reinstall, and verify the new install directory now contains the Mods and plugins folders expected by the mod loader.

Verification checklist after a re-install

The install directory contains the executable, a Mods folder, and at least one .pak archive.
Documents\My Games\ResidentEvilRequiem\SavedGames still lists your old save files.
Launching the game once regenerates %LOCALAPPDATA%\ResidentEvilRequiem\config.ini with default values.
Photo mode still writes to Pictures\ResidentEvilRequiem without prompting for a new folder.
If you use mods, the loader log shows the expected number of .dll entries on the next launch.

Anyone mapping out re9 file locations for the first time should keep a small text file with their own verified paths next to the install directory. A documented baseline removes guesswork the next time a save behaves oddly or a mod fails to load. The same baseline doubles as a personal changelog when Capcom ships a patch that shifts the engine version and forces a re-check of the paths above.

Frequently asked questions

Where exactly does Resident Evil Requiem store saves on PC?

Saves live in %USERPROFILE%\Documents\My Games\ResidentEvilRequiem\SavedGames\. Each save slot is a .dat file paired with a small index entry in settings.json. The folder is created the first time you save in-game, and it survives Steam re-installs because it lives under the user profile rather than under the Steam library.

Can I move my re9 file locations to another drive without breaking cloud sync?

Yes, but use a directory symbolic link rather than moving the folder and then trying to repoint Steam. Create the link from Documents\My Games\ResidentEvilRequiem to the new drive location, then launch the game, save, exit, and let Steam Cloud upload from the new location. This approach keeps the engine happy and preserves the path Steam expects.

What is the difference between the Documents folder and the AppData folder for re9 file locations?

The Documents\My Games\ResidentEvilRequiem tree is for user-visible data such as saves, photo mode screenshots, and a settings index. The %LOCALAPPDATA%\ResidentEvilRequiem tree is for engine internals such as the full config.ini, the shader cache, and any crash dumps. Back up the Documents folder every playthrough and back up the AppData folder whenever you change graphics or control settings.

How do console players back up re9 file locations without a PC?

Both PlayStation 5 and Xbox Series X|S let you copy saved data to USB storage from the system settings, and both can upload saves to platform cloud storage with a toggle in the same menu. Plug the console in, enable cloud sync, wait for the upload confirmation, then copy the save to a USB drive as a second copy. That gives you one local mirror and one off-device mirror.

Why does my mod not show up even though I copied the files into re9 file locations?

Almost always a folder-name mismatch, a mod loader version mismatch, or a hash check failure on a signed .pak. Open the loader’s log file in the install directory, search for the mod’s folder name, and read the line that explains why it was rejected. The fix is usually renaming the folder to match the manifest, updating the mod loader, or moving the mod into the dedicated Mods subfolder instead of the install root.

Is there an official Capcom tool for editing re9 file locations?

No. Capcom has never shipped a save editor for the mainline RE Engine titles, and any third-party tool that claims official status is not endorsed by the studio. The supported workflow for adjusting game data is the in-game menu, the launcher settings, and the platform sync controls. Treat any third-party save editor as a mod that may be blocked by anti-cheat in online modes.

Will deleting the shader cache in re9 file locations delete my saves?

No. The shader cache is a separate folder under %LOCALAPPDATA%\ResidentEvilRequiem\ShaderCache\ and contains only compiled pipeline state used by the GPU driver. Deleting it forces the engine to recompile shaders on the next launch, which is safe. Saves live in Documents\My Games\ResidentEvilRequiem\SavedGames\ and are untouched by any cache cleanup.

Where do crash logs go in re9 file locations, and are they safe to share?

Crash dumps and the always-on game.log land in %LOCALAPPDATA%\ResidentEvilRequiem\CrashDumps\ and the parent folder. They contain technical data such as the engine version, the loaded .pak list, and the faulting module. They are safe to attach to a Capcom support ticket and do not include personal data, but you can review the file in a text editor before sending it if you prefer to strip anything that looks unusual.

How do I keep re9 file locations in sync between a laptop and a desktop PC?

The most reliable method is a folder sync tool pointed at Documents\My Games\ResidentEvilRequiem on both machines, with Steam Cloud disabled for the title to prevent the two sync engines from racing each other. Sync after the game is closed on the source machine, then launch on the target. The same approach works for the configuration folder under %LOCALAPPDATA% if you want settings parity.

Can I safely rename the re9 file locations folders?

No. The engine resolves the path from internal constants, and renaming Documents\My Games\ResidentEvilRequiem or %LOCALAPPDATA%\ResidentEvilRequiem causes the engine to create a fresh empty folder on the next launch, which looks like a data loss. If you want a different name for human-readable organization, rename the parent My Games subfolder only after copying, then use a symbolic link to point the original name at the renamed target. This is the same pattern used to move the data to another drive.

Resident Evil Requiem file locations: full PC and console path guide