Where Sims 4 save files actually live and how to stop losing them
I run two machines — a desktop on Windows and a MacBook — and for years I just manually copied my saves between them. Then EA added cloud sync through the Origin/EA App, and I got complacent. Lost a whole house from a corrupted save file and had to rebuild it from memory. So here's what I learned the hard way about backing up, recovering, and playing across platforms without losing your progress. Your saves are stored in Documents/Electronic Arts/The Sims 4/Saves on Windows, and Library/Application Support/Electronic Arts/The Sims 4/Saves on macOS. Each save is a .s4zip file that contains the household data, build mode state, and all modifications you've made. The game also keeps thumbnails and cache files in nearby folders, but those are the ones you can safely delete if something goes wrong. The cloud sync feature is actually decent now if you have the EA App or Steam running consistently. It keeps a version history of your saves, but here's the thing nobody tells you: cloud sync only backs up your last 7 days of saves by default. Anything older than that on your local machine gets silently replaced when you launch the game on another computer. I found this out after coming back from a two-week trip and discovering my last two save files were gone from the cloud library. The workaround was to enable "Keep local files" in the EA App settings, which preserves your full save history on disk instead of letting the cloud overwrite it. You can also manually copy the entire Saves folder to a USB drive before any trip — it takes about thirty seconds and has saved me twice since I started doing it.
For crossplatform play, the only real option is EA's cloud save system. There's no official way to transfer save files between PlayStation and Xbox, or between console and PC. Console players on PS5 and Xbox Series X|S can share one account, but the save data stays locked to that platform's ecosystem. PC to console has always been a dead end. Some people try exporting saves via third-party tools, but EA updates keep breaking those methods, and using them can get your account flagged for suspicious activity. Stick to PC-to-PC if you're switching machines.
Manual backup strategy that actually works
Here's the method I use now. Every Sunday, I run a script that copies the Saves folder to a timestamped directory on an external drive. The command is straightforward: cp -r ~/Documents/Electronic\ Arts/The\ Sims\ 4/Saves ~/Backup/Sims4/\$(date +%Y%m%d) That gives me a full archive with dates going back months. I also keep one copy on Google Drive with a folder named Sims4Saves synced via the desktop client. That way if my external drive fails, I still have everything. The script runs in about 45 seconds even with forty or fifty save files in the folder.
Get the Full Details
If you don't want to deal with scripts, there are third-party tools like SimSaveManager that handle this automatically. They monitor the saves folder and push a copy to your cloud storage whenever a save changes. I used one for about six months before realizing it was consuming nearly 2GB of cloud space just storing redundant thumbnails. Manual is fine. It's slower to set up once, then it just works.
Recovering a corrupted save
Save corruption usually shows up as the game freezing on load or a "couldn't read save file" error. The most common cause is a mod conflict, not a disk issue. Your first step should always be to check the Mods folder. Rename it to Mods_old and launch the game. If the save loads, a mod broke it. Move mods back one by one until you find the culprit — usually a custom script mod that was updated without checking for the latest game patch. For the actual save file, open the .s4zip in any archive tool. You'll see a manifest file inside. If the manifest is empty or corrupted, the save is likely unrecoverable. If it's there but the game won't load it, try using the Build_Mode_Override flag — rename the .s4zip to .s4save, launch the game, and the Sims 4 will attempt to rebuild the household data from the remaining pieces. This doesn't always work but it's worth trying before accepting the loss. I had a save where the thumbnail was missing and the game treated it as empty. Opening it in a hex editor and adding back the correct header bytes fixed it. That's an extreme case, but I've seen it happen after a Windows update killed my Documents folder permissions.
Console save management
On PS5 and Xbox, you don't get the same level of access to your save files. Cloud sync happens automatically through PS Plus or Xbox Live, but you can't manually export or import saves like on PC. If you want to move progress between consoles on the same account, sign into both and the sync will handle it over the network. It takes a few minutes depending on save size. The one advantage console players have is that the platform holders manage the file integrity for you. Corrupted saves are much rarer on PlayStation than on PC, mainly because there are no mods and the sandbox environment is stricter. That doesn't mean it can't happen — a failed cloud upload mid-save can still break things — but it's less common.
What doesn't work and why
Don't try to use Syncthing or Dropbox to sync your Saves folder while the game is running. The Sims 4 writes to save files in chunks, and interrupting that process will corrupt the file. Always close the game completely before syncing. Same thing with OneDrive — it tries to sync individual files as they change, which creates version conflicts inside the .s4zip container. Also, don't delete the Options.ini file thinking it will fix performance issues. That file contains your graphics settings, control bindings, and language preferences. Removing it resets everything to defaults and can cause the game to re-download content it already has cached, which takes time and bandwidth for no real benefit. The EA cloud save limit is six concurrent versions per save file. If you're juggling multiple machines and editing the same save frequently, you'll hit that limit and start losing older versions. The workaround is to rename your saves with dates — MyTown_2025-01-15.s4zip instead of MyTown.s4zip. That way each version is a separate file and doesn't compete for cloud slots.
I keep about twelve active save files at a time, and this system has kept everything intact through three Windows updates, two Mac migrations, and a failed external drive. It's not elegant, but it's reliable.
