Fixing the “Failed to Save Game Error Code 804 BG3”: Guide to Saving Your Progress

The “Oh No” Moment, you know that feeling. You just spent two hours perfectly positioning your party for a boss fight, or maybe you finally nailed that high-DC persuasion roll you’ve been dreading. You hit F5 to quicksave, expecting that reassuring “Game Saved” text.

Instead? You get slapped with a message that makes your stomach drop: failed to save game error code 804 bg3.

Look, I’ve been there. I remember staring at my screen at 2 AM, realizing I might have to replay the entire Goblin Camp. It’s frustrating, it’s scary, and honestly? It makes you want to rage-quit. But before you close the game (don’t do that yet!), take a breath.

Axeetech is going to fix this. Together.

This isn’t just a list of robot-generated steps. This is me, walking you through what actually works, based on the dozens of times Baldur’s Gate 3 decided to be temperamental with its save files.

Fun Post: Try BG3 Cheat Table

What is this Error Code 804, Anyway?

Before we start tearing apart your settings, let’s understand the enemy.

In my experience troubleshooting Larian games, the failed to save game error code 804 bg3 is almost always a “traffic jam” issue. It’s rarely about your computer being broken. Instead, it’s usually a conflict between where the game wants to put the save file and something blocking it—usually a cloud sync issue or a “too many saves” bottleneck.

Think of it like trying to shove a book onto a shelf that’s already full, or worse, a shelf that someone else (like Steam Cloud) is currently painting.

Here is the battle plan to get your saves working again.

Solution 1: The “Cross-Save” Suspect (Try This First)

If you only try one thing from this guide, make it this one.

When Larian launched BG3, they introduced Cross-Saves so you could jump between PC and PS5. It’s a brilliant feature… when it works. But right now? It is the number one cause of the failed to save game error code 804 bg3. The game gets stuck trying to upload your save to Larian’s servers, times out, and throws the error.

Here’s the fix:

1. Open your Settings menu in-game.
2. Head over to the Gameplay tab.
3. Scroll down until you see Cross-Save.
4. Turn it OFF.

Why this works: You’re telling the game, “Hey, stop trying to talk to the server. Just save the file to my hard drive.” In 90% of cases, this clears the traffic jam instantly. Try saving again immediately after unchecking this.

Do Check: Rimiot501 Internal Error Fixed

Solution 2: The Steam Cloud Conflict

If disabling Larian’s cross-saves didn’t do the trick, Steam might be the one causing the headache. Sometimes Steam Cloud holds onto a save file “lock” a little too tight, preventing the game from overwriting it.

It’s annoying, I know—we rely on cloud saves for backup—but for troubleshooting, we need to temporarily cut the cord.

How to handle it:

1. Close the game (I know, I said don’t close it earlier, but if Solution 1 didn’t work, we have to risk it. Hopefully, you have an older auto-save).
2. Right-click Baldur’s Gate 3 in your Steam Library.
3. Select Properties.
4. Under the General tab, look for the Steam Cloud section.
5. Toggle the switch to OFF.

Pro Tip: After you do this, wait about 60 seconds before launching the game again. Let Steam “breathe” and realize it doesn’t need to sync. Launch the game and try to create a new manual save.

Solution 3: The “Spring Cleaning” Method (Deleting Temporary Files)

Okay, if you’re still reading, the easy fixes didn’t stick. That’s okay. We’re going to get a little more technical, but I promise it’s safe.

Sometimes, BG3 accumulates “digital lint”—temporary files that get corrupted. Specifically, the LevelCache. Think of this as the game’s short-term memory. If it gets confused, the game forgets how to write new memories (saves).

Let’s clear the cache:

1. Make sure the game is closed.
2. Open your File Explorer (Windows Key + E).
3. Paste this into the address bar: %localappdata%\Larian Studios\Baldur's Gate 3
4. You’ll see a folder called LevelCache.
5. Delete the contents of this folder. (Don’t worry, the game rebuilds this automatically next time you launch).

While you are here, if you have a massive amount of save files (like, 200+ auto-saves), the game engine might be choking on the index.

• Go into the PlayerProfiles/Public/Savegames/Story folder.
• If you see hundreds of folders, try moving (cut and paste) some of the older ones to a backup folder on your desktop. Give the game some breathing room.

Solution 4: The “Nuclear” Option (Digital Hygiene)

Still seeing the failed to save game error code 804 bg3? Alright, let’s look at security software.

It sounds paranoid, but sometimes Windows Defender or your antivirus sees a new save file being created and thinks, “Aha! Malware!” It blocks the file creation, and boom—Error 804.

The sanity check:

• Run as Admin: Right-click the game executable (bg3.exe or bg3_dx11.exe in your installation folder) and choose Run as Administrator. This gives the game “permission” to override security doubts.
• Whitelist the Game: Go into your Antivirus settings and add the entire Larian Studios folder to the “Exceptions” or “Allow” list.

Do Read: gsm 0.23 ntsc-1 full buffer

Summary of Fixes

I know that was a lot of info. Here is the cheat sheet to keeping that failed to save game error code 804 bg3 away for good:

Method	Likelihood of Success	Difficulty
Disable Cross-Saves	High (Start here!)	Very Low
Disable Steam Cloud	Medium	Low
Clear LevelCache	Medium-High	Medium
Run as Admin	Low (But possible)	Low

FAQ: Your “Wait, But What About…” Questions Answered

Q: Am I going to lose all my progress?
A: Probably not! That’s why our first fixes are non-destructive. We always back up before deleting. Your saves are likely recoverable.

Q: Which fix works the most often?
A: In my experience and from helping countless others, the combination of disabling cross-saves + verifying files or the manual folder reset (Fix 3) resolves the majority of error code 804 bg3 cases.

Q: Is this a bug with the game? Should I report it?
A: It’s often a system-environment issue, but yes, you can and should report persistent issues to Larian at support.larian.com. It helps them identify wider patterns.

Q: How can I prevent this from happening again?
A: Regularly prune your save files in-game (don’t keep hundreds), maintain good disk health, and be mindful of cloud service conflicts. I make a manual backup of my save folder every few play sessions—it’s a lifesaver.

Also Read: Fixing Error hf-xet-1.1.10-py310h63875d3_0

A Final Thought from One Gamer to Another

I know how disheartening it is to lose progress. It’s not just about the time; it’s about the story you were weaving.

When I first ran into error 804, I thought my 80-hour campaign was toast. But it wasn’t. It was just a sync error. By following these steps—specifically turning off those pesky cross-saves—I was able to rescue my Tav and finish the story.

You’ve got this. Try the cross-save fix first, take a deep breath, and get back to saving the Sword Coast.

Next Step for You: Open your game right now and check that “Cross-Save” setting in the Gameplay tab. If it’s on, toggle it off and try a quicksave immediately. Let me know if that green “Game Saved” text pops up!