Skip to content
Game save workbench
Local-first tools No installation Support status shown
DEVICE-LOCAL Favorites and recent pages stay in this browser.

Save File Formats

Persona 4 Golden Save File Format Reference

Persona 4 Golden save-file format reference covering the known PC file or folder pattern, documented format characteristics, compatibility boundaries, and what should not be inferred from an extension alone.

Editorial state
Reviewed
Reading time
3 min
Difficulty
Beginner
Last reviewed

Before you start

Work from a copied save rather than the live file. Use the documented path and filename/folder pattern to identify the correct record before inspecting bytes or text.

Key takeaways

What this guide establishes.

  • Use the documented save directory for the PC storefront/profile you actually play.
  • Back up the complete save boundary before restore, migration, repair, or editing.
  • Treat cloud synchronization as a separate copy that can overwrite a manual restore.
  • Do not infer editability from a filename extension; format and version compatibility must be verified.

Persona 4 Golden illustrates why a save “slot” can be more than one file. Steam stores data under app ID 1113000, and documented cross-platform workflows pair each dataXXXX.bin with a companion .binslot structure whose checksum may need to agree. A backup of only the visibly largest file is therefore incomplete. SaveEditor recommends copying the whole remote directory first, then treating any conversion or editor workflow as a separate operation on duplicates. Microsoft Store is again represented by WGS and is not presented as drop-in compatible.

Known Persona 4 Golden save-file structure

The researched filename or folder pattern is Steam commonly uses dataXXXX.bin with corresponding dataXXXX.binslot metadata; cloud metadata also resides in the remote directory.. File-extension context: .bin, .binslot The documented format notes are: Steam stores the save set under app ID 1113000. Community-documented Vita/PC and edited-save workflows note a checksum relationship between dataXXXX.bin and dataXXXX.binslot. Microsoft Store uses WGS.

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. Edited or cross-platform slot data can fail if companion checksum metadata no longer matches. Avoid mixing a .bin from one snapshot with a .binslot from another. 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: Steam: <Steam-folder>userdata<user-id>1113000remote ; Microsoft Store: %LOCALAPPDATA%PackagesSEGAofAmericaInc.D0cb6b3aet_s751p9cej88mtSystemAppDatawgs<user-id>. Storefront context: Steam, Microsoft Store. A .bin slot and its .binslot metadata should be treated as a pair. Microsoft Store WGS transfer is a separate conversion problem, not a simple rename. 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

Back up the entire 1113000remote directory before changing a slot. Preserve the matching .bin/.binslot files and cloud metadata together so the original pairing can be restored. 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 and Xbox Cloud are documented. 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 a slot warns or fails to load, restore the matching pair. When moving from Microsoft Store, verify the transfer workflow for the current game version instead of treating WGS blobs as Steam files. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.

Verification context: Reviewed against current PCGamingWiki Persona 4 Golden save-location and Vita-transfer/checksum notes.

Troubleshooting

If the expected result does not match.

Game-specific note: If a slot warns or fails to load, restore the matching pair. When moving from Microsoft Store, verify the transfer workflow for the current game version instead of treating WGS blobs as Steam files.

Verification and sources

How this guide was checked.

Phase 27 generated this Guide from the reviewed Phase 23/24 Game Hub evidence for Persona 4 Golden. The file/folder naming and documented format boundary were cross-checked against the same public references recorded on the Game Hub. No unsupported game-specific editor, checksum, encryption, or cross-platform conversion capability is implied.

  1. www.pcgamingwiki.com