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

Game Hub / Save Reference

Persona 4 Golden Save Files & Tools

Persona 4 Golden PC save location, backup, file-format, launcher, cloud-sync, and compatibility reference. This Game Hub documents save-file facts without implying that a game-specific Save Editor is available.

PC

01 / Overview

Save reference at a glance.

Game Hubs separate documented save-file facts from actual Tool support. A Game Hub can be useful even when no custom editor exists.

Developer
Atlus
Publisher
Sega
Platforms
PC
Save extensions
.bin, .binslot

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.

For this PC reference, the documented storage is Windows: Steam: <Steam-folder>userdata<user-id>1113000remote ; Microsoft Store: %LOCALAPPDATA%PackagesSEGAofAmericaInc.D0cb6b3aet_s751p9cej88mtSystemAppDatawgs<user-id>. The known file or folder pattern is Steam commonly uses dataXXXX.bin with corresponding dataXXXX.binslot metadata; cloud metadata also resides in the remote directory.. 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.

Backup guidance: 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. Steam Cloud and Xbox Cloud are documented. Launcher and cloud context matters because 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.

Compatibility and recovery should stay conservative. 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. If the expected progress is not visible, 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. SaveEditor.com only labels a game-specific editor as available when a separate linked Tool has a verified operational runtime; this reference page by itself is not an editor claim.

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.

02 / Save locations

Where the save files are stored.

Paths are displayed only when they have been explicitly documented for this Game Hub. Environment variables and launcher-specific differences should remain visible instead of being silently normalized.

Windows
Steam: <Steam-folder>userdata<user-id>1113000remote ; Microsoft Store: %LOCALAPPDATA%PackagesSEGAofAmericaInc.D0cb6b3aet_s751p9cej88mtSystemAppDatawgs<user-id>

Launcher / edition differences

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.

03 / File format

Files, extensions, and format notes.

This section documents only known file names and structures. Format notes can later connect directly to SaveEditor.com parsers, checksum engines, and converters.

Extensions

.bin .binslot

File names / patterns

  • Steam commonly uses dataXXXX.bin with corresponding dataXXXX.binslot metadata
  • cloud metadata also resides in the remote directory.

Format notes

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.

Launchers / stores

Steam / Microsoft Store

Cloud save notes

Steam Cloud and Xbox Cloud are documented.

04 / Tools

Actual linked Tool support.

No verified game-specific Save Editor is currently listed. This Game Hub remains useful for save locations, file details, backup guidance, and other linked utilities.

No active game-specific Tool is currently listed.

Planned and deprecated Tool records are intentionally excluded. The save-reference information on this page remains separate from Tool availability.

05 / Backup

Protect the original before editing.

Save editing should be reversible. Keep an untouched copy outside the active save directory before replacing, converting, repairing, or modifying a save.

  1. 01
    Close the game.

    Avoid modifying a save while the game or launcher may still be writing to it.

  2. 02
    Copy the entire relevant save set.

    Some games use multiple files, profile folders, metadata, or companion files rather than one isolated save.

  3. 03
    Store the backup elsewhere.

    Use a separate folder or archive so cloud sync or the game cannot overwrite the untouched backup.

  4. 04
    Edit a copy, then validate.

    Follow the exact compatibility and processing notes on the Tool page before replacing the active save.

Game-specific backup note

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.

06 / Troubleshooting

When a save is missing or rejected.

Start with reversible checks. Do not delete or overwrite the only copy while diagnosing a path, cloud-sync, version, or format problem.

Game-specific notes

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.

A

Confirm the correct profile.

Games, launchers, and operating systems may keep separate save folders for different users, editions, or profiles.

B

Check cloud synchronization.

A cloud service can restore an older file or overwrite a local change. Preserve both copies before resolving a conflict.

C

Check Tool compatibility.

A matching filename does not prove a matching format. Verify platform, game version, extension, and Tool support state.

D

Restore the untouched backup.

If the game rejects a modified save, return to the original backup before attempting another change.

07 / FAQ

Persona 4 Golden save-file questions.

Answers are generated only from visible Game Hub metadata and actual linked Tool states, plus universal backup guidance.

Where are Persona 4 Golden save files stored?

The currently documented save locations are listed in the Save locations section above. Use the location that matches your platform or environment.

What save-file extension does Persona 4 Golden use?

The extensions currently documented on this page are: .bin, .binslot.

Does SaveEditor.com have a verified Persona 4 Golden Save Editor?

No verified game-specific Save Editor is currently listed. This Game Hub remains useful for save locations, file details, backup guidance, and other linked utilities.

Should I back up the save before using a Tool?

Yes. Keep an untouched copy outside the active save directory before modifying or converting the file. Some games use multiple companion files, so back up the relevant save folder when in doubt.

Are there cloud-save considerations for Persona 4 Golden?

Steam Cloud and Xbox Cloud are documented.

Editorial review

Game-specific metadata on this hub was last reviewed on 2026-08-08. Individual Tool pages maintain their own verification dates and compatibility notes.

Verification notes

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