Phantom Blade Zero save file location: Steam save folder

The Phantom Blade Zero save file location for the Windows Steam edition is configured under the game’s installation folder, not a generic AppData directory. SteamDB’s published Steam Cloud rules point to PBZ\ProjectPBZ\Saved\SaveGames\Steam\ followed by a folder named for your 64-bit Steam ID. The matching files use the .sav extension. This is a configuration-based location, not a claim that we have opened a finished retail save on a player’s PC. As checked on October 28, 2026, the game’s Steam unlock is scheduled for October 29 at 02:00 UTC; a preload alone may not have created playable save data. Below is the safest way to locate the folder, copy your progress, and deal with a missing save without accidentally overwriting it.

This guide is about locating, preserving, and cautiously restoring local save data. It does not cover the game’s system requirements, DLSS, or rendering settings. The Steam instructions apply to the Windows Steam edition; a PlayStation save is not a Windows .sav file, and a save path for another PC storefront cannot be assumed from Steam’s configuration.

Quick answer: where are the Steam save files?

The strongest game-specific evidence currently available is the Windows Auto-Cloud configuration indexed by SteamDB for Steam app 4115450. The root is gameinstall, the install directory is named PBZ, the relative path is ProjectPBZ/Saved/SaveGames/Steam/{64BitSteamID}, and the configured filename pattern is *.sav. Valve’s Steamworks documentation explains that an Auto-Cloud gameinstall root refers to the installed game’s directory and that {64BitSteamID} is substituted with the current Steam account’s 64-bit ID.

Configured Windows Steam path:

[Steam Library]\steamapps\common\PBZ\ProjectPBZ\Saved\SaveGames\Steam\{64BitSteamID}

Example on a default Steam installation:

C:\Program Files (x86)\Steam\steamapps\common\PBZ\ProjectPBZ\Saved\SaveGames\Steam\{64BitSteamID}

The braces denote a variable, not a literal folder name. In a real installation, the last folder should be a string of digits identifying the Steam account. If you installed games to a second SSD, replace the default C: Steam Library with the actual library containing Phantom Blade Zero; do not create the example path by hand and assume the game will use it.

A Steam Cloud rule describes the files the client is configured to synchronize. It is valuable evidence of the intended location, but it does not prove that a preorder preload already includes saves or that the developer will never revise its directories. If the folder is absent before you have launched the full game and reached a save point, that is not, by itself, a bug.

Find the save folder in Windows without guessing a drive letter

The most reliable method is to start from the installed game shown in your own Steam library. That removes the biggest source of incorrect directions: many players keep Windows on C: but install large games on D: or another SSD.

Start at Steam’s installed files

1. Open the Steam desktop client and sign in to the account used for the game.
2. Select Library, find Phantom Blade Zero, and right-click its entry.
3. Select Properties, then open Installed Files. Steam’s official support documentation confirms this Properties → Installed Files route for working with a game’s installation.
4. Use the Browse option in Installed Files to open the installation directory if your current Steam client presents it. If its wording differs, use Steam’s installed-drive information and open the game directory in File Explorer instead.
5. In the folder named PBZ, navigate through ProjectPBZ → Saved → SaveGames → Steam. Look for a numeric account folder, then inspect .sav files inside it.

Expected result: File Explorer shows an installation rooted at ...\steamapps\common\PBZ\ with the configured save subfolders if the game has created them. A folder full of executables or large .pak assets is not itself proof you have found progress data; you should be looking for the account-specific SaveGames folder and the configured file pattern.

If the folder is missing: First confirm the game has unlocked and that you have actually created a save or checkpoint in a normal playable session. The SteamDB data currently identifies a future unlock at October 29, 2026, 02:00 UTC, and SteamDB has shown the product in a preload-only state. A preload may install content without generating a character’s save files. Do not generate an empty SaveGames hierarchy and present that as a successful fix.

Navigate directly once you know the installed library

Suppose Steam’s Browse action opens D:\SteamLibrary\steamapps\common\PBZ. Click the File Explorer address bar and append the verified relative location below, then press Enter:

ProjectPBZ\Saved\SaveGames\Steam

Alternatively, open the directories one at a time to reduce the risk of pasting a malformed path. If more than one numeric folder appears because different people have played under different Steam accounts, do not combine their contents. Identify the active account and compare timestamps after making read-only copies; using an account’s Steam64 identifier is more reliable than choosing the folder with the largest number of files.

You can also search within the known PBZ installation directory for *.sav in File Explorer. Searching only inside this installation avoids mixing results from unrelated games. Windows file indexing, permissions, or a game that has not yet saved can make the search return nothing; no result is not proof of a missing cloud save.

Tell save data apart from installation and cloud metadata

Three similarly named places serve different purposes. First, PBZ\ProjectPBZ\Saved\SaveGames\Steam\... is the title-specific directory reflected in the published Auto-Cloud rule. Second, steamapps\common\PBZ is the broader game-install directory containing many files you do not need to back up just to preserve progress. Third, Steam also uses its own userdata tree for account-specific cloud-related information. Valve documents that generic Steam location, but its existence does not replace the title-specific gameinstall rule above.

Some third-party prelaunch guides propose a folder under %localappdata%\PhantomBladeZero. That is a prediction, not the path shown in this game’s currently indexed Steam Auto-Cloud configuration. Likewise, the general path Steam\userdata\[account]\4115450\remote should not be presented as the verified main save directory for Phantom Blade Zero unless its contents can actually be inspected. Checking speculative locations is a secondary diagnostic only after the configured install directory and live game behavior have been examined.

Back up Phantom Blade Zero progress safely

A good backup protects existing data before an update, Windows reinstall, drive migration, Steam Cloud conflict, or experimental troubleshooting step. It should be a copy, not a cut-and-paste operation. Nothing about the game’s Cloud badge makes a separate offline backup unnecessary: Valve’s own Steam Cloud guidance says synchronization can fail, and missing cloud saves may not be recoverable by support.

Make a copy without changing the live files

1. Reach an ordinary in-game save/checkpoint if the released game provides one. Exit to the title screen or quit using the game’s normal menu; avoid terminating it during a save animation or write operation.
2. Return to Steam and let any visible Cloud synchronization finish. If Steam reports a sync error, stop and preserve what is already on disk rather than repeatedly reopening the game.
3. From Library → Phantom Blade Zero → Properties → Installed Files, open the install location, then follow ProjectPBZ\Saved\SaveGames\Steam to the folder for your account.
4. In File Explorer, right-click the account folder and select Copy. Paste it into a separate folder, such as Documents\Game Save Backups\Phantom Blade Zero\2026-10-28-before-update or an external drive. The date is just an example naming convention; use the actual date of your backup.
5. Preserve the entire numeric account folder, including subdirectories and original filenames. Do not rename .sav files or extract them into a different game account folder.
6. Open the backup destination and confirm that files are present and that their sizes are nonzero where expected. Compare the original and copied file counts, names, and sizes. This verifies the copy operation, although only a later successful load can fully validate a usable backup.

Expected result: There are now two independent copies of the same save set: the game’s original files in the installation directory and a copy outside that directory. The second copy should survive a game reinstall that removes the original installation, provided its separate backup location is not also erased.

Do not rely on Steam’s Backup and Restore Games feature alone to preserve player progress. Steam’s support documentation explains that backing up installed game files is not a universal guarantee that saved games are included. For this title, a direct copy of the confirmed local save directory is the clearer precaution.

A small pre-update checklist

Before you update graphics drivers, move the Steam Library, reinstall Windows, or test an unofficial mod, check four things: the game was closed normally; Steam finished any sync attempt or its failure was recorded; the account-specific .sav directory was copied outside PBZ; and the copy contains the files you expect. If you have multiple Steam accounts on the PC, label the backup with the correct account so you do not restore one player’s progress over another’s.

You do not need to disable Steam Cloud to make an ordinary copy. The least risky backup action is to leave existing sync settings alone and copy the original files when the game is closed. Changing sync behavior is a separate, higher-risk decision that should not be the first step in a guide about finding a folder.

What to do if the save folder is empty or missing

The meaning of “my save is missing” depends on when you looked and what the game actually did. Work through the likely cases in order rather than downloading a replacement save from an unknown website.

The game has not reached its scheduled unlock

This is especially important for readers finding this guide in late October 2026. The game has a listed U.S. Steam store date of October 28, while SteamDB expresses its unlock as October 29 at 02:00 UTC. These are compatible time-zone representations, not evidence of two distinct launches. Before that instant, and until the full game is playable, a local save file may not exist at all. Do not mark a missing folder as save corruption based solely on an installed preload.

Steam is installed on another drive

Use Steam to find the library rather than assuming C:\Program Files (x86)\Steam. For example, on a machine using E:\Games\SteamLibrary, the matching location would begin E:\Games\SteamLibrary\steamapps\common\PBZ. The relative portion, ProjectPBZ\Saved\SaveGames\Steam, is the meaningful part of the Steam Cloud configuration. Your drive letter and higher-level Steam Library name are local choices.

After finding the PBZ root, check the full relative path before searching Windows globally. A Windows-wide *.sav search can produce unrelated games’ saves, making it easy to mistake an old file for a Phantom Blade Zero backup.

The account folder is there, but the game cannot see progress

Do not rename a numeric SteamID folder to match an account guessed from its display name. The path variable specifically denotes a 64-bit Steam ID, which Steamworks uses for per-user save separation. Check that Steam is signed into the account that created the save. Copy the full account folder to safety, then note the current file modified times, the game build and whether Steam displayed a Cloud error.

The .sav extension identifies a synchronization pattern; it does not tell you that individual saves can be edited, merged, or transferred between accounts safely. A different Steam account, future game update, or integrity scheme may prevent a file from loading. If the game recognizes files but reports them invalid, the safe next step is developer support with your non-sensitive error details, not trial-and-error deletion.

Steam Cloud: why the save may also appear elsewhere

The Steam store lists Steam Cloud for Phantom Blade Zero, and its indexed configuration names a group of *.sav files to synchronize. Steam Cloud is a transfer mechanism, not a promise that the latest progress exists forever on every device. Valve documents that the sync client may use an account-specific userdata directory and that missing or outdated files can arise when synchronization fails.

Check whether Cloud sync is enabled

1. Open Steam → Library, right-click Phantom Blade Zero, and select Properties.
2. In General, locate the Steam Cloud synchronization control if it is presented for the game. Steam Support documents a per-game Cloud toggle there.
3. Observe whether it is enabled; do not change it as a routine first step. Return to the game’s Library page and look for any visible sync status or warning.
4. If a warning says files did not synchronize, avoid launching the game on a second PC or blindly choosing a cloud/local version until you have copied the available local saves.

Expected result: You know which Steam account and sync setting apply. A Cloud badge confirms an integration exists, but only a completed successful synchronization after a real save shows that the latest local changes have been sent from that machine. If no option is visible before launch, verify the game’s release state and client version rather than inventing a missing menu setting.

Do not treat userdata as a second guaranteed backup

Valve’s default Windows Cloud-related directory is C:\Program Files (x86)\Steam\userdata, with game-specific paths nested under account identifiers and app IDs. Steam app 4115450 can therefore help you recognize title-related metadata if present. However, the current game-specific Auto-Cloud rule explicitly selects a path relative to the game installation. A file found in userdata may be an account or cloud-management artifact, not an interchangeable copy of the game-save .sav directory.

The actionable distinction is simple: start with the PBZ install-root save directory when making a backup; consult userdata only to understand Steam’s account/sync bookkeeping or under official support guidance. Do not overwrite either structure with the other.

Restore a copied save without destroying newer progress

Restoring is riskier than copying because Steam may have a different version in the cloud and the installed game may already have created newer progress. A backup can also be incompatible with an updated game or a different Steam account. Treat the following as a controlled recovery procedure, not a guarantee that any .sav file will work in every build.

1. Preserve what is there now. Close the game and make a fresh copy of the current numeric SteamID save folder. Store it in a clearly different location from your older backup.
2. Confirm you have the correct build and Steam account. Check that the original backup belongs to this account and was made from the Steam Windows edition. Keep the game updated through Steam rather than replacing executable files with material from unknown sources.
3. Review the Steam Cloud state. If there is a sync conflict, preserve both the current local copy and the older backup before selecting any resolution. Do not assume that the newest timestamp always means the most advanced in-game progress.
4. Exit the game and Steam before changing active files. If you have decided to test a restore, copy your old account folder’s contents into the corresponding account-specific SaveGames folder. Preserve the original folder structure and do not paste files into a different account’s directory.
5. Reopen Steam carefully. If Steam presents a local-versus-cloud conflict, examine which version you intend to retain. If the choices are unclear, cancel and seek official assistance rather than making a destructive selection.
6. Verify in-game. Launch the game, inspect the expected checkpoint and settings, then exit normally and check the sync result. If the save is missing or incompatible, stop instead of repeatedly replacing files; you still have the pre-restore copy.

For advanced troubleshooting, temporary offline testing or temporarily changing per-game Cloud synchronization may isolate which copy is loading, but these actions can lead to later conflicts. They are not required for routine backups and should only be considered after making redundant copies and understanding that Steam may upload or replace files when synchronization resumes.

If two devices have different progress

Do not open both copies and try to merge .sav files manually. On each device, close the game, preserve an independent local copy, and identify the machine that actually contains the wanted progress. Afterward, resolve the Steam Cloud status from one device at a time. Steam Support warns that the service cannot reliably recover lost data after a bad sync; having both original copies is what lets you reverse a mistaken choice or escalate a problem without losing your only evidence.

If no local backup exists and Cloud sync was never completed, the missing progress may be unrecoverable. A Steam reinstall or game-file integrity check cannot reconstruct a deleted player save unless another surviving copy exists. This is why a manual backup before major changes matters even for a single-player game with Steam Cloud enabled.

What is not verified for Epic, PlayStation, or future updates?

This article’s exact directory comes from a Windows Steam Auto-Cloud rule. It should not be repurposed as an official path for Epic Games, a console, a future Microsoft Store edition, or Linux running Steam Proton. Different platforms can use different storage systems, account identifiers, and transfer restrictions. In particular, the presence of a Windows .sav file does not imply the game allows PlayStation-to-PC save conversion or cross-progression.

Before launch, third-party posts that propose AppData\Local\PhantomBladeZero\Saved\SaveGames or a named Epic folder are speculative unless the relevant build or publisher explicitly confirms them. The more reliable release-day check is to open the game on the storefront you actually use, create a small new save, exit normally, and observe which directory changes. Then compare that result with current official documentation and the already indexed Steam configuration; document any change rather than quietly rewriting the path as though it had always been known.

Because the Steam Cloud rule can be edited and later patches may change data handling, anyone publishing long-lived instructions should recheck the game-specific rule and, ideally, a real installed game after each meaningful update. A single guide written before release should not claim permanent, universal accuracy.

Tools That Help

• Steam desktop client (free): Use Library → game Properties → Installed Files to find the actual installation drive, and General to inspect Steam Cloud availability. This is the first tool for the Windows Steam edition.
• Windows File Explorer (built in): Open the configured PBZ\ProjectPBZ\Saved\SaveGames\Steam path, identify the account folder, and copy the entire folder to another location. Windows 11 users can select View → Show → File name extensions to inspect .sav endings; on Windows 10, use the View → File name extensions option.
• A separate backup destination (existing storage is enough): A second internal volume, external drive, or already available backup folder prevents a game reinstall from erasing the only copy. No additional purchase is needed if you already have a safe location outside the game’s installation folder.

These are storage and verification tools, not save editors. Avoid unofficial downloads that promise to “repair” or unlock saved progress by replacing arbitrary .sav files. A wrong account, game version, or synchronization conflict needs diagnosis first.

Frequently asked questions

Is the save in AppData or the Phantom Blade Zero installation folder?

For the Windows Steam edition, the Steam Cloud configuration currently identifies a directory inside the game installation, under PBZ\ProjectPBZ\Saved\SaveGames\Steam\{64BitSteamID}. An AppData path circulated in some guides is not established by that configuration. Check your actual install folder first, and verify behavior after the full game unlocks.

What is the Phantom Blade Zero Steam app ID?

The app ID is 4115450. It identifies the game in SteamDB and Steam-related account data, but an app ID is not the last folder of the configured save path. That last folder represents the player’s 64-bit Steam ID.

Can I see save files before launch if I preloaded the game?

Not necessarily. Preloading game assets is different from the game generating a player save. As of this guide’s October 28, 2026 research, SteamDB lists an October 29, 02:00 UTC unlock. Check the directory again only after the released build becomes playable and you complete a normal save.

Does Steam Cloud mean I do not need a local backup?

No. Steam Cloud can help synchronize progress between devices, but Valve cautions that failed syncs and conflicts can result in lost saves that support cannot restore. A separate manual copy provides a recovery option independent of what the cloud currently holds.

Can I move a Steam save to another PC?

A careful file transfer might be possible for the same Steam account and a compatible build, but cross-device loading has not been independently verified for this game’s launch build. Preserve both systems’ saves, install the game normally, and resolve Steam Cloud state before testing. Do not promise cross-account or console compatibility.

Is the Steam userdata folder the same as the save folder?

No. userdata is a generic Steam location used for account-specific cloud-related files. The specific Phantom Blade Zero Windows Auto-Cloud rule currently references the game’s installation root. Do not assume the files in these locations can be interchanged.

What should I do if my copied .sav files do not work?

Stop overwriting files. Preserve both the original and restored copies, check the Steam account, verify that the game is fully updated, and inspect the Cloud conflict status. If the game reports corruption or an incompatible version, escalate to official game support with the error message and build details; do not upload save data publicly unless support explicitly requests a secure transfer.

Final Thoughts

For Windows Steam users, the best-supported Phantom Blade Zero save file location is the Steam installation’s PBZ\ProjectPBZ\Saved\SaveGames\Steam\{64BitSteamID} directory. This conclusion is grounded in the game’s published Steam Auto-Cloud rule, with the important pre-release limitation that actual retail save creation still requires confirmation. Once the playable game is unlocked and you have made a save, open Steam → Library → Phantom Blade Zero → Properties → Installed Files, browse to the correct drive, and copy the entire account-specific save folder outside the game installation. Confirm the backup’s files before experimenting with updates, reinstalls, or Cloud conflicts.