Getting Started · Beginner · 11 min
Understand UE5 Project Files and Saving (So You Never Lose Work)
Learn exactly what Ctrl+S saves, how Save All works, what every folder in your project does, which ones are safe to touch, and how autosave quietly has your back.
Before this: Install Unreal Engine 5 and Open It for the First Time, Navigate the UE5 Viewport Like You've Done It for Years
- Save a level with Ctrl+S and save everything with Save All
- Recognise what each top-level project folder does and stores
- Know which folders are safe to touch and which to leave alone
- Configure and trust Unreal's autosave so a crash never costs you much
Why this boring-sounding lesson saves your project
Every Unreal beginner eventually loses an hour of work to a crash, a power cut, or simply closing the editor and clicking 'Don't Save' by accident. The fix isn't talent — it's a five-minute habit, plus understanding what's actually happening when you save.
Unreal doesn't keep your whole project in one file. Your work is split across many files in a folder on your disk, and 'saving' means writing the things you've changed back out to those files. Once you understand which file holds what, saving stops being a mystery and the dreaded asterisk (*) next to a tab name starts making perfect sense.
This lesson covers two things: the saving habits that protect your work, and a quick, honest tour of your project folder so you know what's safe to touch. Short, but genuinely important — let's go.
Save your level and everything else
Open any project (the Third Person project from earlier lessons is perfect). Move something in the viewport so you have an unsaved change to practise on, then work through these.
- 1Notice the unsaved-changes marker
After you edit something, look at the viewport tab and the title bar. An asterisk (*) appears next to the level name — for example 'ThirdPersonMap*'. That star means 'this has changes that aren't on disk yet'.
It's Unreal's polite warning. As long as the star is there, a crash would lose those changes.
TipMake a habit of glancing for that asterisk. No star = your level is safe on disk.
- 2Save the current level with Ctrl+S
Press Ctrl+S (Cmd+S on a Mac). This saves the level you're currently editing — and only that level.
The asterisk disappears. That's your confirmation it worked. Ctrl+S is the shortcut you'll press most often, so build the reflex now: change something, then Ctrl+S.
TipIf it's a brand-new, never-saved level, Ctrl+S opens a 'Save As' dialog asking for a name and a folder inside Content. Give it a clear name like 'MainLevel'.
- 3Understand what Ctrl+S does NOT save
Ctrl+S saves the level (the .umap), but a level isn't the only thing you change. Edit a Material, a Blueprint, or a mesh, and those are separate asset files that Ctrl+S on the level won't touch.
This is the number-one beginner trap: you press Ctrl+S, see the level star vanish, and assume everything is saved — but your edited Blueprint is still unsaved.
- 4Use Save All to save everything at once
From the menu, choose File → Save All, or press Ctrl+Shift+S. This saves the level AND every modified asset in the project in one go.
When you're about to take a break, close the editor, or simply want to be sure, Save All is the safe button. It's the 'save my whole project' command.
TipCtrl+Shift+S (Save All) is the one to press before you walk away from the desk.
- 5Spot unsaved assets in the Content Browser
Unsaved assets show a small marker on their icon in the Content Browser (an asterisk-style overlay). You can right-click a folder and choose 'Save All' to save just that folder's changes.
If a 'Save Content' or 'unsaved changes' prompt pops up when you close the editor, it's listing exactly these modified assets — read it rather than blindly clicking 'Don't Save'.
TipWhen the close prompt appears, the safe choice is 'Save Selected' (with everything ticked). 'Don't Save' really does throw the changes away.
The saving shortcuts to memorise
- Ctrl S Save the current level only (Cmd + S on Mac)
- Ctrl Shift S Save All — the level plus every modified asset
- Ctrl S (inside an asset editor) While a Blueprint or Material is open in its own editor window, Ctrl+S saves THAT asset
Where your project actually lives
When you created your project, Unreal made a folder for it on your disk (somewhere like Documents/Unreal Projects/MyProject). Open that folder in your file explorer and you'll see one file and several folders. Knowing what each one is removes a lot of fear — and tells you what you can safely back up, copy, or delete.
Here's the honest breakdown. Two things are precious, and the rest can be rebuilt by Unreal if they go missing.
Your project folder, term by term
Tap a card to flip it
What's safe to touch vs leave alone
A quick reference. The rule of thumb: Content and the .uproject are sacred; the rest is either settings or disposable cache.
- BACK UP: the Content folder and the .uproject file — together they ARE your project
- KEEP (but edit via the editor): the Config folder — your project settings
- SAFE TO DELETE (editor closed): the Intermediate folder — pure temporary cache, rebuilt automatically
- SAFE TO DELETE (editor closed): the Saved folder — logs, autosaves and caches; you'll lose autosave history but nothing you've saved properly
- NEVER hand-edit files inside Content in a text editor — they're binary assets and you'll corrupt them; always change them through the Unreal editor
- If you also have Binaries and DerivedDataCache folders, those are likewise rebuildable and safe to delete when closed
Autosave: your safety net (not your save button)
Unreal autosaves in the background by default. Every so often it writes recovery copies of your modified levels and assets into the Saved folder, so a crash doesn't wipe out everything since your last manual save.
Two honest caveats. First, autosave is a backup, not a replacement for Ctrl+S — recovered files are a separate copy you choose to restore, not your real saved work. Second, an autosave can briefly interrupt you with a 'Saving…' pause. You can tune how often it runs (or turn it off) in Editor Preferences under the Loading & Saving section.
You pressed Ctrl+S, the level's asterisk vanished, then the editor crashed. When you reopen, your Blueprint edits from just before the crash are gone. What happened — and how do you avoid it next time?
Ctrl+S only saved the level (the .umap). Your Blueprint is a separate asset file, and editing it had left it unsaved — the level's vanished asterisk told you nothing about the Blueprint's state.
Avoid it by getting into the Save All habit: press Ctrl+Shift+S (or File → Save All) instead of plain Ctrl+S whenever you've touched more than just the level. And let autosave help — if it ran before the crash, Unreal may offer to recover a copy of the Blueprint from the Saved folder when you reopen the project.
QuizCheck yourself
1You press Ctrl+S after editing a level and a Blueprint. What actually got saved?
Ctrl+S saves the current level only. To save the Blueprint too, use Save All (Ctrl+Shift+S) or save the asset directly.
2Which two things together effectively ARE your project and must be backed up?
Content holds all your assets and levels; the .uproject opens the project and records its engine version and plugins. Everything else can be rebuilt.
3The editor is closed and you want to free up disk space. Which folder is always safe to delete because Unreal regenerates it?
Intermediate is temporary build/compile cache. Deleting it while the editor is closed is harmless — and a common fix when a project misbehaves.
Prove to yourself you understand saving and recovery. Move an actor in the viewport, edit any asset (rename a material or tweak a Blueprint), then deliberately save the right way. Finally, open your project folder in your file explorer and identify each top-level folder out loud.
Hint 1
Watch the level tab for the asterisk as you make the first change.
Hint 2
Don't reach for Ctrl+S here — you changed more than the level, so use the all-in-one save.
Hint 3
To find the project folder fast: in the editor, right-click a folder in the Content Browser and choose 'Show in Explorer', then go up one level out of Content.
Move an actor (level tab shows 'MyLevel*'), then edit an asset (its Content Browser icon gains a star overlay). Press Ctrl+Shift+S (Save All) — both stars disappear, confirming the level and the asset are now on disk.
Open the project folder: you should see MyProject.uproject (double-click target), Content (your assets — precious), Config (settings — keep), and Saved plus Intermediate (auto-generated — safe to delete when closed). Naming them confidently means you'll never panic about a folder again.
Save All vs Ctrl+S — when to use which
You've only been moving, placing, or tweaking actors in the current level and nothing else.
It's quick and targeted, which is why it's the most-pressed shortcut. Just remember its scope is the level alone.
You've touched anything beyond the level — a Blueprint, material, mesh, or several levels — or you're about to close the editor or step away.
Save All (Ctrl+Shift+S) sweeps up every modified asset, so it's the no-regrets choice whenever you're unsure. Many people just use it by default.
Mark this lesson complete
We'll remember it on your Academy page and unlock the next lesson below.
Questions beginners ask
What's the difference between Ctrl+S and Save All?
Ctrl+S saves only the level you're currently editing. Save All (Ctrl+Shift+S, or File → Save All) saves the level plus every modified asset in the project — Blueprints, materials, meshes and so on. If you've changed anything beyond the level, Save All is the safe choice.
Can I delete the Intermediate and Saved folders?
Yes, when the editor is closed. Both are auto-generated: Intermediate holds temporary build/compile cache, and Saved holds logs, autosaves, crash reports and editor layout. Unreal rebuilds them on the next open. Deleting Intermediate is a common first fix when a project starts misbehaving. Never delete the Content folder or the .uproject file — those are your actual project.
Does autosave mean I don't need to press Ctrl+S?
No. Autosave is a background safety net that writes recovery copies into the Saved folder so a crash doesn't cost you everything since your last manual save. But recovered files are separate copies you choose to restore — they're not a substitute for properly saving your work with Ctrl+S or Save All. You can adjust how often autosave runs (or disable it) in Editor Preferences under Loading & Saving.
How do I move my project to another computer?
Copy the Content and Config folders plus the .uproject file. That's everything that defines your project; Unreal regenerates the Saved, Intermediate, Binaries and DerivedDataCache folders automatically the first time it opens the project on the new machine. This also keeps your backup small.