Uncover The Hidden Path Finding Your Game Files In Epic Games Launcher

Where Your Epic Games Actually Live on Disk

When you launch a game through Epic, it disappears into some folder that isn't obvious from the launcher itself. Most people try random guesses or dig through the start menu shortcut properties, which gives you a fragile path that breaks if you ever move the install directory. There's a straightforward way to get the exact location every time, and it doesn't require third-party tools or hunting through hidden system directories. The path you're looking for lives in the library view of the launcher. Open Epic Games, click on your game tile, and look for the three dots or Manage button below the title. There's a path string displayed right there — something like C:\Program Files\EpicGames\Fortnite\Binaries\Win64 — but it's not always the root of what you need. That path points to the binaries, not the actual install root where all the game data sits. If you right-click that path and select Open Folder, you drop into the game directory directly. I ran into a specific problem with Genshin Impact a while back where the launcher path was correct but the actual save data and resource files were split across two locations due to a cloud sync quirk Epic had enabled. The path in the launcher pointed to the CloudSaved directory, not the local resources. I had to close the launcher entirely, navigate to C:\ProgramData\Epic\EpicGamesLauncher\Data, and check the manifest.json file to find the true install_root value. The difference between the launcher-reported path and the real one was about 340 gigabytes of duplicated content eating my C drive. Once I switched the install location to D drive and cleaned up the leftover empty folders, it stopped being an issue. This is the kind of edge case that doesn't show up in any official documentation.

The manifest approach works universally across all Epic titles, not just that one game. The launcher writes a metadata file for each installed product, and the install root is stored as a string field. You can also find this information without opening any text editor by holding Shift while right-clicking the game tile in the library, which reveals an "Open Folder" context menu entry that points to the actual root rather than the binaries subdirectory. Most people don't know Shift modifies the right-click behavior in the Epic launcher. There's another route that's faster if you just need the path for scripting or mod installation purposes. Open Task Manager while the game is running, right-click the game process, and select Open file location. This gives you the live execution path, which is guaranteed to be correct because it's what Windows is using at that moment. It bypasses any launcher bugs or manifest discrepancies. The trade-off is you need the game running, which isn't always practical for large titles that take ten to fifteen minutes to boot. For command-line users, you can query the Epic Games Launcher registry keys directly. Navigate to HKEY_CURRENT_USER\Software\Epic Games\EpicGamesLauncher and look for the AppDataPath value, which points to the user-level configuration. From there, the installed games are listed under HKEY_CURRENT_USER\Software\Epic Games\UnrealEngine\InstalledGames on older installations, though newer launcher versions moved this to a less accessible location inside the AppData folder at %localappdata%\Epic\EpicGamesLauncher\Data\Manifests. Each .manifest file there contains the install path for one game, formatted as simple key-value pairs.

A few things to keep in mind before you start chasing these paths around. The Epic Games folder default location is on whichever drive the launcher was first installed to, and there's no built-in bulk-move feature for existing installations. If you installed games on C drive and later want them on D, you have to uninstall and reinstall each one — the launcher will try to preserve your saves if they're cloud-synced, but local saves that aren't synced get left behind. I've lost progress on a couple of occasions because of this exact assumption. Always verify cloud sync is enabled for a game before moving its install location. Some games also have their own sub-managers. Ubisoft Connect titles installed through Epic maintain a separate Ubisoft game folder structure underneath the Epic root, and Rockstar games create their own subdirectories. If you're looking for config files or mods, check the game's own documentation first rather than digging blindly through the Epic tree. The layout isn't consistent across publishers, and spending twenty minutes searching for a file that's in a completely different expected location is frustrating in a predictable way. If you need programmatic access to all installed Epic games at once, the Epic Web API doesn't expose a game inventory endpoint anymore after they deprecated the older service. The local manifest files remain the most reliable source, and parsing them takes about thirty lines of Python if you want to automate something like a mod backup script. I wrote one for myself once that scanned all manifest files in the Data folder, collected install roots, and generated a JSON inventory with sizes. It took me about forty-five minutes to write and debug because the manifest format changed slightly between launcher versions without any announcement.

The most common pitfall is confusing the Engine root with the Game root. Many Epic titles share the same Unreal Engine installation, so you'll see Engine folders scattered through the path. The engine folder contains shared binaries and tools, not your game's content. Mod files or config edits should go into the game-specific subdirectory, typically GameName\Content\Paks or GameName\Saved\Config\WindowsNoEditor. Putting things in the Engine folder either gets overwritten on the next update or does nothing at all because the game loads content from its own directory first. There's also the matter of verified installations. Epic has a built-in verify function accessible from the same Manage menu, and it's worth running it if your game files seem corrupted but the path looks right. Corrupted shader caches, missing pak files, and truncated textures all show up as normal path errors to beginners who haven't seen them before. The verify operation checks file hashes against Epic's CDN and re-downloads anything that doesn't match. It's not instant — a full verification of a 100-gigabyte game took me about twenty-two minutes on a 1gigabit connection — but it resolves more issues than people give it credit for. One more thing that trips people up: Epic Games Launcher sometimes reports the wrong drive letter if you use symbolic links or Junction points to redirect your game folders. Windows resolves the junction transparently for most applications, but the launcher reads the manifest literally and shows you the junction target path rather than the original. If you moved a game using mklink, the launcher path will show the symlink location, which is technically correct but confusing if you don't expect it. Check with fsutil reparsepoint query if you're unsure whether a folder is a real directory or a link.

I mostly use the manifest file approach now because it's scriptable and doesn't require the launcher to be open. For one-off lookups, the Shift-right-click trick is faster. Between those two methods, you can find the exact location of any game installed through Epic without guessing or browsing aimlessly through your drives.