Support

Gears of War: E-Day Saves and Roaming Progress

Understand officially advertised roaming saves, verify synchronization safely, preserve timestamps, and avoid invented local save paths before launch.

The E-Day Steam listing says optional account linking lets players carry progress with roaming saves across supported platforms. That is the verified pre-release feature. The exact local Windows save directory, Steam Cloud configuration, file format, synchronization timing, and conflict screen are not yet published, so this guide does not invent a path.

Safe save handling begins with account identity, normal exits, timestamp checks, and non-destructive backups after the shipping AppID 3010850 exposes its real files.

Know which account owns the progress

Confirm the Steam account and linked Microsoft/Xbox gamertag before beginning Campaign or multiplayer progression. If the wrong identity is active, stop before creating substantial progress and consult account support.

Beta AppID 4059240 is separate. Ordinary Beta progression does not carry into the full game; only specifically announced rewards can carry when the same Xbox account is used.

Do not copy Beta files into the base-game directory. Entitlements and roaming progress are service-controlled, not created by renaming folders.

Let synchronization finish

Exit through the game menu and wait for Steam/account synchronization indicators to complete before shutting down, suspending a handheld, or launching on another device. Avoid playing simultaneously on two platforms with the same progress identity.

On the second device, verify Player Level, Campaign checkpoint, customization, and timestamp before continuing. A cross-platform feature may roam some progress while local video/input settings remain device-specific.

If a sync warning appears, read both timestamps and device labels rather than choosing automatically.

Test roaming with a low-risk change

Before relying on cross-device play, make a small recognizable change: complete an early safe checkpoint, equip a harmless cosmetic, or adjust a profile item. Exit normally, allow sync, and verify on the other supported device.

Do not use a major Campaign completion, Premium entitlement purchase, or rare reward as the first test. A small result is easier for support to diagnose.

Record AppID, public build, devices, linked account, time/timezone, and observed progress.

Find the actual local save path after launch

Use first-party support documentation, Steam’s declared cloud file information if exposed, or a controlled filesystem observation after the game writes a save. Verify a candidate by timestamp while the game is closed.

Do not rely on a path from Gears 5, Xbox PC, a Beta, or another Unreal Engine 5 game. Similar engines do not guarantee identical storage.

Once confirmed, document Windows account placeholders without exposing a real username. Separate save data from caches, shader data, logs, and configuration.

Make a non-destructive backup

Close the game and wait for synchronization. Copy the confirmed save files to a dated folder on a separate safe location; do not move or delete the originals. Record game build, Steam account, Xbox identity, and file hashes if the backup is important.

Back up before a platform move, major patch, account-link change, or support-directed repair. Keep multiple dated versions rather than overwriting the only copy.

Never upload save files publicly before checking for account identifiers or tokens.

Resolve a conflict conservatively

If Steam or the game presents two versions, compare device, timestamp, progress, and build. Choose only when the newer intended state is clear. If unclear, cancel, preserve both local states if the official workflow permits, and contact support.

Do not launch repeatedly on both devices; each session can create another competing timestamp. Do not delete cloud data or unlink accounts as a first fix.

Capture the conflict dialog with sensitive identity details redacted.

Separate saves from unlock entitlements

Premium Edition packs, preorder rewards, Beta rewards, purchases, and account-bound cosmetics may be entitlements rather than ordinary local-save fields. Restoring a file should not be expected to recreate store ownership.

Player progression, settings, campaign checkpoints, and multiplayer unlocks can also have different storage owners. Verify each category after a restore.

If only one entitlement is missing, investigate edition/account linkage rather than overwriting otherwise healthy progress.

Saves FAQ

Are roaming saves officially advertised?

Yes. The Steam feature list associates optional account linking with carrying progress through roaming saves.

What is the E-Day local save path?

It is not reliably published before launch, so this page intentionally does not guess one.

Should Beta save files be copied into the base game?

No. Beta progress does not generally carry, and the products use separate AppIDs.

Official sources checked August 8, 2026: the Steam base-game page and Open Beta FAQ. Local paths and sync-conflict behavior remain launch-gated rather than fabricated.

Continue with another focused Gears of War: E-Day guide.

Support

Gears of War: E-Day Beta Access on Steam

Use the official Steam path for the separate E-Day Multiplayer Beta, verify both August windows, resolve a missing digital entitlement, and distinguish retail codes from game codes.

Support

Gears of War: E-Day Controller and Keyboard Settings

Set up controller or keyboard/mouse remapping for cover, shoulder swap, new movement, Active Reload, marking, and repeatable practice.

Support

Gears of War: E-Day Crossplay Guide

Understand E-Day cross-platform invitations, two-to-four-player online co-op, eight-player Versus scope, and account checks for Steam.