There’s nothing worse than being in the zone, cruising through a project, clicking “Save”… and BAM! “Bolt.new failed to save your project.” Panic. Frustration. Confusion. We’ve all been there. But don’t worry — let’s fix this together and have a little fun while we’re at it.

TL;DR

If you’re getting the “Bolt.new failed to save your project” error, it usually means Bolt has trouble writing to a file or directory. This can be caused by permission issues, corrupted files, or cloud sync conflicts. Stay calm, check your project folder, and follow our easy steps below. You’ll be back to building cool stuff in no time!

What is Bolt.new, anyway?

Bolt is a visual scripting tool for Unity. It’s super handy if you want to create game logic without writing code. When you use it, Bolt creates a bunch of files to save your project setup and brains (literally, they call parts of it a “Macro” and “Graph”).

When it says “Bolt.new failed to save your project,” what it really means is that it hit a wall while trying to write something important. Let’s help it out!

Step 1: Turn it off and on again

Yes, we know. This sounds like a tech cliché. But it works more often than you’d think.

  • Close Unity completely.
  • Restart your computer.
  • Open Unity and reload the project.

If the problem goes away — congratulations! You win. If not, let’s pop open the toolbox.

Step 2: Check your file and folder permissions

Sometimes Bolt freaks out because it doesn’t have the right to change a folder or file. On Windows or Mac, right-click the project folder and get into its properties or Get Info panel.

  • Make sure the folder is not “Read-only.”
  • Give write access (not just read) to your user account.
  • Try running Unity as admin (Windows) or with elevated permissions (Mac).

If Bolt can’t write, it can’t save. So giving it the pen (aka write access) usually helps.

Step 3: Look for conflicting apps

This one’s sneaky. Apps like Dropbox, Google Drive, iCloud, and OneDrive might be trying to sync your project files while you’re editing them. That’s a problem.

Here’s what to do:

  • Temporarily pause syncing.
  • Move your Unity project to a folder that’s not monitored by cloud apps.
  • Re-open the project in Unity.

Once the syncing fight is over, Bolt should feel calmer.

Step 4: Check for corrupted graphs or macros

Bolt saves your flows in “graph” or “macro” files. These can sometimes get corrupted — especially if Unity crashed or you had a power outage mid-save.

Try this:

  1. Go to your Assets folder in your Unity project.
  2. Look for subfolders like Macros or Graphs.
  3. Check modified dates — anything weird?
  4. Try removing (or backing up) any recently created files.

Then reopen the project and see if Bolt starts behaving. You might lose a tiny bit of progress, but at least you’ll be back to saving again.

Step 5: Peek at the Console

Unity’s Console is like the project’s gossip column. It tells you all the dirt — what crashed, what’s missing, what’s broken.

To view it:

  • Go to Window > General > Console.
  • Look for red text (errors).
  • Click on errors related to Bolt or “Save”.

If it says something specific, like “Could not write file:…” — that’s your clue! You now know which file is acting up.

Step 6: Rebuild Bolt from scratch (it’s not as scary as it sounds)

Sometimes a clean slate is the best fix. Here’s how to refresh Bolt setup:

  1. Back up your entire Unity project (just in case).
  2. Delete the Bolt folder from Assets.
  3. Go to Package Manager and reinstall Bolt.
  4. Reinstall your Bolt Assets or Graphs from backup if you saved them.
  5. Run Bolt’s setup again via Tools > Bolt > Setup Wizard.

You don’t lose much this way, and it can clear out whatever mystical bug was in there.

Bonus Fix: Use version control

If you’re not already using version control… welcome to your new best friend.

Git, for example, helps you:

  • Keep track of changes.
  • Revert to earlier versions before the error happened.
  • Keep your files safe from unexpected crashes or deletion.

So even if something weird starts happening, a simple git restore can bring your project back to life.

Still Broken? Try This Superpower

If none of this works, there’s one secret weapon: Unity forums and Discords.

Post the exact error, a screenshot if you can, and what you’ve tried already. One of the Unity Jedi is bound to help.

Places to visit:

Final Thoughts

This error can feel like the end of the world, especially if you’re in a groove. But remember: it’s usually just a permissions issue, a syncing conflict, or a tiny corrupted file. No monsters under the bed.

With a bit of detective work, some patience, and a whole lot of saving backups, you’ll squash this bug and keep creating!

Now go out there and make something awesome. Bolt’s got your back — as long as you hit SAVE!