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.
Identify the exact save you intend to edit
The researched Persona 4 Golden PC save location is Windows: Steam: <Steam-folder>userdata<user-id>1113000remote ; Microsoft Store: %LOCALAPPDATA%PackagesSEGAofAmericaInc.D0cb6b3aet_s751p9cej88mtSystemAppDatawgs<user-id>. Known file/folder pattern: Steam commonly uses dataXXXX.bin with corresponding dataXXXX.binslot metadata; cloud metadata also resides in the remote directory.. 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. Do not edit a similarly named file from a different profile, edition, or cloud cache.
Make an untouched backup first
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. Keep that copy outside the live save directory and do not overwrite it with later experiments. Cloud context: Steam Cloud and Xbox Cloud are documented. If a launcher can synchronize the save, prevent it from silently replacing either the original or edited copy while testing.
Understand the format boundary
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. File-extension context: .bin, .binslot Compatibility note: 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. These facts help identify the save but do not automatically reveal every field, checksum, encryption rule, or version-specific structure inside it.
Use only a Tool whose claim matches the file
Generic viewers and diff tools can inspect bytes without claiming game-specific semantics. A game-specific editor should be used only when its Tool page explicitly lists Persona 4 Golden, a matching supported version/container, and a Verified operational runtime. A planned URL or Game Hub is not evidence that an editor exists.
Test the edited copy safely
Write to a new output file when the Tool supports it, keep the original backup, restore the edited copy into the correct profile/storefront location, and launch the game only after the file operation finishes. If the game rejects it, 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. Return to the untouched backup before trying another change.
Verification context: Reviewed against current PCGamingWiki Persona 4 Golden save-location and Vita-transfer/checksum notes.