How to Save Your First Blend File

Beginner20-30 minutesWindowsBlender

Lost work is not an edge case. In every active modeling community, modelers lose sessions to power failures, application crashes, accidental overwrites, and the simple error of closing Blender and clicking "Quit Without Saving" when they intended to click "Save and Quit." The hours represented by a lost session are not recoverable. The geometry, the UV mapping, the material assignments, the modifier stack — none of it comes back without a saved file.

Blender provides four distinct mechanisms that protect against work loss: the manual save, the Save As dialog with a new filename, the automatic backup file written alongside every save, and the application-level autosave written to a temporary directory at regular intervals. Each mechanism handles a different failure mode. Understanding all four — and the conditions under which each one is available — is the difference between a recoverable incident and a permanent loss.

This article documents each mechanism in sequence, from the simplest manual save to the complete power-loss recovery procedure. The article is part of the 57 Studios™ Blender setup track. It is written with the Unturned™ mod development workflow in mind, which means file naming conventions, save locations, and save cadence recommendations reflect the specific structure of a 57 Studios mod project.

Prerequisites

Before beginning this article, the following must be true:

• Blender is installed and open.
• The default startup scene is visible, or a scene with some geometry has been created.
• The modeler has a folder designated for the current mod project. If no folder exists yet, create one before proceeding. The folder structure matters for the save location recommendations in this article.
• Windows File Explorer is accessible for navigating to save locations.
• The modeler has read the previous article on deleting the default cube. The scene state referenced in the save procedures assumes the cube has been handled.

What you will learn

By the end of this article, the reader will be able to:

• Save a .blend file to a specific folder using File → Save As.
• Apply a consistent file naming convention appropriate for Unturned mod source files.
• Understand why the save location relative to the Unity project folder matters.
• Use Ctrl+S to save incrementally during a session.
• Locate and use the .blend1 backup file that Blender writes automatically.
• Locate the autosave directory and recover a session from it after a crash.
• Execute the complete power-loss recovery procedure when the last known save pre-dates the crash by more than a few minutes.
• Implement a save cadence that limits the maximum amount of work that can be lost in any single incident.
• Use Save As versioning to maintain a linear history of a model across multiple sessions.

The cost of unsaved work

Before any procedure, the following framing is necessary. A modeling session in Blender accumulates work continuously. A single hour of productive modeling might produce a completed base mesh, clean edge loops across a curved surface, accurate proportions derived from a reference image, and a UV unwrap that took thirty minutes to execute cleanly. None of that work exists anywhere except in the current session's memory until a save is executed.

The total cost of losing one hour of Blender work is not one hour. It is the one hour of work plus the time spent re-establishing context on the return to the project, plus the demoralization that accompanies re-doing work that was previously completed. In practice, a modeler who loses a significant session produces inferior work on the re-do because the original session contained decisions that were made through iteration and are not fully recoverable from memory.

Every minute of unsaved work is at risk

Blender holds the current session entirely in RAM. A power failure, a system crash, a kernel panic, a driver crash that takes the GPU, or a force-kill of the Blender process will destroy every unsaved change in the current session. The autosave system provides a partial recovery, but only up to the most recent autosave interval. Work performed after the last autosave is not recoverable from any mechanism other than redo from scratch.

The procedures in this article are not optional safety measures. They are the minimum operational discipline required to work on a project that has real value. A Unturned mod that takes twenty hours to build is worth protecting. A file save takes two seconds.

The four protection mechanisms

Blender's work-loss protection operates at four levels, each covering a different failure scenario.

Mechanism	Triggered by	File location	Recovers from
Manual save (Ctrl+S)	Modeler action	Modeler-chosen location	Normal session end, planned recovery
Save As (Ctrl+Shift+S)	Modeler action	Modeler-chosen location	Version branching, rename, first save
Backup file (.blend1)	Blender, on every save	Same folder as the .blend file	Overwrote the file with a bad save
Autosave	Blender, every N minutes	Temporary directory	Crash, power loss, force-kill

Each mechanism is described in full in the sections that follow. A modeler who understands all four can recover from any single failure event. A modeler who knows only Ctrl+S can recover from a planned session end but not from a crash between saves.

The flowchart above maps every failure scenario to a recovery path. The only unrecoverable scenario is a power loss that occurs before the first autosave of the session and before any manual save. This scenario has a recovery time of zero seconds for the recovery procedure itself — because there is nothing to recover — and a cost equal to the full duration of work since the last session end.

Step-by-step — First save using Save As

The first save of any new project must use Save As, because the file has not yet been given a name or a location. Ctrl+S on a new unsaved scene behaves identically to Ctrl+Shift+S, opening the Save As dialog.

Step 1 — Decide where the file will live

Before opening the Save As dialog, decide the destination folder. For a 57 Studios Unturned mod project, the correct location depends on the relationship between the Blender source files and the Unity project.

The recommended folder structure is:

C:\<your projects folder>\<mod name>\
    Unity\                          ← Unity project root
        Assets\
            Models\                 ← .fbx files go here (Unity imports these)
    Blender\                        ← .blend files go here (NOT inside Unity)
        <ModelName>_v1.blend
        <ModelName>_v2.blend

The Blender source files do not go inside the Unity project folder. They go in a sibling folder alongside it. The reason is that Unity's asset importer scans the Assets folder and any folder under it. A .blend file inside the Assets folder will be processed by Unity's importer, which may produce unexpected mesh imports. The source files are tools for producing the exported FBX; they are not assets to be imported directly.

Unity's FBX importer and .blend files

Unity can import .blend files directly if Blender is installed and the Unity editor is configured to recognize it. However, the 57 Studios workflow exports FBX from Blender and imports the FBX into Unity. Direct .blend import is not part of the documented workflow and introduces dependency on a specific Blender installation path that can break on other machines. Keep .blend files outside the Unity Assets folder.

Step 2 — Open the Save As dialog

Choose File → Save As from the menu bar, or press Ctrl+Shift+S. The Save As dialog opens. The dialog is a file browser built into Blender. It is not the standard Windows file picker; it uses Blender's own panel-based interface.

The left side of the dialog shows a list of locations: Recent, Home, Desktop, Documents, and any folders that have been bookmarked. The center shows the contents of the current folder. The top shows the current path. The bottom contains a text field for the filename and a "Save As" button.

Step 3 — Navigate to the destination folder

Use the file browser in the Save As dialog to navigate to the Blender\ subfolder of the mod project. To navigate:

• Click a location in the left sidebar to jump to it.
• Double-click a folder in the center panel to enter it.
• Click the arrow at the top left of the dialog to go up one folder level.

If the destination folder does not exist yet, create it from within the Save As dialog by clicking the "New Folder" button at the top right of the dialog, entering the folder name, and pressing Enter.

Step 4 — Enter the filename

Click inside the filename field at the bottom of the dialog and type the filename. Follow the naming convention described in the next section before typing. Press Backspace to clear the default filename if one is already present.

Step 5 — Click "Save As" or press Enter

Click the "Save As" button at the bottom right of the dialog, or press Enter. The file is written to the selected folder with the specified filename. The title bar of the main Blender window updates to show the full path of the newly saved file.

After a successful save, the title bar should read something like:

Blender 4.2.5 LTS (Hash ...) - C:\Mods\iron_crate\Blender\iron_crate_v1.blend

If the title bar still shows C:\Users\<username>\AppData\Local\Temp\... or a similar temporary path, the save was not applied to the intended destination.

File naming conventions for Unturned mod sources

Consistent file naming prevents confusion when a project grows to multiple models, multiple versions, and multiple sessions. The following naming convention is used throughout the 57 Studios documentation.

The convention

<asset_name>_v<version>.blend

• <asset_name> — lowercase letters, digits, and underscores only. No spaces. No special characters. Use the name that will appear in the Unity project and the Tebex store listing, converted to snake_case.
• _v<version> — a version number starting at 1 and incrementing on every major save event. Not padded with leading zeros.
• .blend — the Blender file extension. Always lowercase.

Examples

Asset	Version 1 filename	Version 2 filename
Iron storage crate	iron_crate_v1.blend	iron_crate_v2.blend
Military jeep	military_jeep_v1.blend	military_jeep_v2.blend
Concrete barrier	concrete_barrier_v1.blend	concrete_barrier_v2.blend
Radio tower segment	radio_tower_seg_v1.blend	radio_tower_seg_v2.blend

Spaces in filenames cause problems

A filename with spaces — such as Iron Crate v1.blend — can cause issues in command-line operations, Python scripts, and some Unity import configurations. Use underscores instead of spaces. This is a strict convention in the 57 Studios workflow and applies to all files in the mod project: .blend files, .fbx files, texture files, and configuration files.

The version number in the filename

The version number in the filename is not the same as Blender's undo history. It is a snapshot of the file at a meaningful milestone: a completed base mesh, a completed UV unwrap, a completed material assignment, or a completed export pass. The version number should advance when the modeler has completed a unit of work they would not want to lose. It should not advance for every save; only for milestone saves.

Naming examples to avoid

Pattern	Why it is problematic
untitled.blend	The Blender default name. Provides no information about the asset.
Iron Crate.blend	Spaces in the filename.
iron_crate_FINAL.blend	"FINAL" is not a version number and does not increment.
iron_crate_FINAL_v2.blend	Mixing descriptive labels and version numbers.
IC_v1.blend	Abbreviation that becomes ambiguous as the project grows.
v1_iron_crate.blend	Version number prefix rather than suffix; harder to sort alphabetically.
iron crate v1.blend	Spaces in the filename.
Iron_Crate_V1.blend	Mixed case. Stick to lowercase throughout.

The incremental save — Ctrl+S during a session

After the first save with Save As, every subsequent save during the session uses Ctrl+S. This overwrites the file at the current path with the current state of the session. The title bar shows an asterisk (*) before the filename when there are unsaved changes; the asterisk disappears after a successful save.

Do not ignore the asterisk

The asterisk in the title bar means the current session contains changes that have not been written to disk. Every minute the asterisk is present is a minute of work at risk. Pressing Ctrl+S takes less than one second. There is no cost to saving frequently and significant cost to not saving.

Recommended save cadence

The 57 Studios documentation recommends saving every ten minutes at minimum during an active modeling session. The following table contextualizes the recommendation:

Save interval	Maximum work at risk	Recovery time after a crash
Every 5 minutes	5 minutes of work	Under 1 minute to reopen and return to state
Every 10 minutes	10 minutes of work	2–5 minutes to reopen and assess what was lost
Every 20 minutes	20 minutes of work	5–10 minutes to reopen and re-do recent changes
Every 30 minutes	30 minutes of work	10–20 minutes to re-establish context and re-do
Every 60 minutes	60 minutes of work	30–60 minutes to recover from memory
Never	Entire session	Full session must be re-done

The modeler's goal is to minimize the maximum work at risk at any moment in the session. Ten minutes is the recommended ceiling. Five minutes is better. The autosave system provides a backstop at whatever interval it is configured to, but the autosave is a recovery mechanism, not a replacement for manual saves. Autosave files require an explicit recovery step; manual saves do not.

A physical save trigger

Experienced modelers develop physical habits that trigger Ctrl+S. Common triggers: reaching a point where re-doing the last step would be painful (completing a loop cut series, finishing an extrusion, placing the last UV island), finishing a symmetrical operation, completing any operation that took more than two minutes, and returning from a break. These triggers are more reliable than a fixed timer because they associate the save with meaningful work completion.

The .blend1 backup file

Every time Blender saves a .blend file, it creates or updates a backup file with the extension .blend1. The .blend1 file contains the state of the session from immediately before the save that just occurred. It is written automatically with no user action required.

The .blend1 file lives in the same folder as the .blend file and has an identical name with the .blend1 extension:

C:\Mods\iron_crate\Blender\
    iron_crate_v1.blend      ← current save
    iron_crate_v1.blend1     ← previous save (automatic backup)

When the .blend1 file saves you

The .blend1 file is useful when the most recent save overwrote good work with a bad state. Examples:

• The modeler saved immediately after accidentally deleting a large portion of the mesh, before noticing the damage.
• The modeler saved with an incorrect modifier applied permanently, flattening the model.
• The modeler saved with the wrong layer visible, hiding the work in progress and saving an empty scene.

In each case, the .blend1 file contains the state from the save before the damaging save. The modeler can open the .blend1 file directly from Blender's open dialog.

The .blend1 file is one save behind

The .blend1 file contains the state from the previous save, not the current state. If the modeler saves multiple times between the good state and the bad state, the .blend1 file may contain neither. The .blend1 mechanism protects against a single bad save. It does not provide a full version history.

Procedure — recovering from a bad save using .blend1

1. Open Blender's file browser with File → Open.
2. Navigate to the folder where the .blend file is saved.
3. In the file browser, enable the display of .blend1 files. Blender's file browser may filter them by default; look for a filter toggle in the file browser and confirm that all file types are visible.
4. Click the .blend1 file and click "Open" or press Enter.
5. Blender opens the previous save state. Verify that the state is correct.
6. Immediately save the recovered file using File → Save As with a new version number, to preserve the recovery as a distinct milestone. Do not overwrite the damaged .blend file directly.

Blender also writes .blend2

Blender can be configured to maintain additional numbered backup levels: .blend1, .blend2, .blend3, and so on. The setting is in Edit → Preferences → Save & Load → Save Versions. The default is 1, meaning only .blend1 is maintained. Increasing this value to 3 or higher provides a deeper recovery window. The additional files consume disk space proportional to the size of the .blend file.

The autosave system

Blender's autosave system writes the current session state to a temporary directory at a regular interval, independent of the modeler's manual save actions. The autosave is a safety net that catches crashes and power losses.

Autosave location

The autosave files are written to the Windows temporary folder:

C:\Users\<username>\AppData\Local\Temp\

The filenames follow the pattern <random-number>.blend. On a computer where Blender is the only application writing to the temp directory, the most recent Blender autosave file can be identified by its modification timestamp. On a computer with many applications active, the temp directory may contain hundreds of files; sort by "Date modified" descending to find the Blender autosave.

Blender identifies its own autosave files by name: they use an eight-digit number followed by .blend. The number corresponds to the Blender process ID.

Where to find your username

If the username is not known, open a PowerShell window and type $env:USERNAME. The response is the Windows username used in the AppData path. The full autosave path can also be found in Blender's preferences: Edit → Preferences → Save & Load → Temporary Directory.

Default autosave interval

The default autosave interval in Blender is two minutes. The interval can be changed in Edit → Preferences → Save & Load → Auto Save Temporary File (set the timer value). The minimum supported interval is one minute. There is no maximum; modelers who want the safety net to fire every two minutes should leave the default unchanged.

Setting	Value	Where to configure
Auto Save Temporary File	Enabled by default	Edit → Preferences → Save & Load
Timer (minutes)	2 (default)	Same location
Save Versions	1 (default)	Same location — controls .blend1/.blend2/etc. count
Temporary Directory	C:\Users<username>\AppData\Local\Temp\	Same location

Verify the autosave is enabled

Before beginning any significant modeling session, confirm that autosave is enabled. Open Edit → Preferences → Save & Load and verify that "Auto Save Temporary File" is checked and the timer shows a value of 2 minutes or less. If autosave is disabled, enable it now. An unchecked checkbox here means the autosave recovery procedure described in the next section will have no file to recover from.

Power-loss recovery procedure

The following procedure applies when Blender was running at the time of a power loss, system crash, or force-kill, and the modeler wants to recover the most recent work from the session.

This is a time-sensitive procedure. The autosave file in the temporary directory persists until the temporary directory is cleared. Windows may clear the temporary directory during a disk cleanup operation. Execute this procedure before running any disk cleanup.

Assessment — determine which recovery path applies

Before opening any file, assess the situation:

1. Was the .blend file saved at any point during the session that was interrupted?
2. When was the last manual save relative to the power loss?
3. Has any disk cleanup been run since the power loss?

Situation	Recovery path
Last save was less than 10 minutes before the loss	Reopen the .blend file directly — minimal work lost
Last save was more than 10 minutes before the loss	Use autosave recovery
No manual save was ever made	Use autosave recovery — risk of total loss if before first autosave
Disk cleanup has been run	Autosave may be gone; .blend file or .blend1 file are the only options

Recovery procedure — step by step

Step 1 — Open File Explorer. Press Windows+E to open File Explorer.

Step 2 — Navigate to the temporary directory. In the address bar of File Explorer, type the following path and press Enter:

C:\Users\<your-username>\AppData\Local\Temp\

Replace <your-username> with the Windows username. If the AppData folder is not visible, it is hidden by default. Enable hidden folders in File Explorer with View → Show → Hidden items.

Step 3 — Sort by Date Modified, descending. Click the "Date modified" column header once to sort ascending, then again to sort descending. The most recently modified files appear at the top.

Step 4 — Identify the Blender autosave file. Look for files with an eight-digit numeric name and the .blend extension. The most recently modified file with this pattern is the most recent Blender autosave. The modification timestamp on the file indicates when the autosave was last written — which corresponds to when the last autosave interval fired before the interruption.

Do not open the autosave file from File Explorer

Double-clicking a .blend file in File Explorer opens it in Blender and may write a new autosave over the existing one. Instead, note the full path to the file and open it from within Blender using File → Open.

Step 5 — Open Blender. Launch Blender normally. If Blender offers a "Recover Last Session" option in the splash screen, that option accesses the same autosave file. Using it is equivalent to Step 6.

Step 6 — Use File → Recover → Recover Auto Save. In the Blender menu bar, choose File → Recover → Recover Auto Save. A file browser opens, pointed directly at the temporary directory. The autosave files appear in the browser. The most recent file by modification time is the one to open.

Step 7 — Open the autosave file. Click the most recent autosave .blend file in the browser and click "Recover Auto Save" or press Enter. Blender opens the recovered session.

Step 8 — Assess the recovered state. Examine the recovered scene. Identify what work is present and estimate how much time has elapsed since the autosave that is being recovered. The autosave represents the session state at the time the autosave was written, which may be up to two minutes before the interruption (depending on the autosave interval and when in the cycle the power loss occurred).

Step 9 — Immediately save as a new version. Do not work from the recovered autosave file. It lives in the temporary directory and will be overwritten or deleted. Immediately perform File → Save As and save the recovered state to the project's Blender folder with the appropriate version number.

Save the autosave immediately after recovery

The autosave file in the temporary directory is not a permanent save. It will be overwritten the next time Blender's autosave fires — which happens two minutes after Blender is open. A modeler who recovers the autosave and begins working without performing File → Save As risks having the recovery overwritten by the next autosave cycle, which may not yet contain the re-established work.

Step 10 — Confirm the permanent save. After File → Save As completes, confirm the file appears in the project's Blender folder using File Explorer. The title bar of the Blender window should show the full path to the new file in the project folder, not a path in the temporary directory.

Recovery procedure sequence diagram

The "Recover Last Session" path

Blender maintains a separate recovery file for the most recent session at C:\Users\<username>\AppData\Roaming\Blender Foundation\Blender\<version>\config\quit.blend. This file is written when Blender exits normally — including when the user clicks "Quit Without Saving" — and represents the session state at the moment Blender closed.

The quit.blend file is accessed through File → Recover → Recover Last Session. It is distinct from the autosave in the temporary directory: the autosave is written at intervals during the session, while quit.blend is written only when Blender exits cleanly. After a power loss, quit.blend may not have been updated because Blender did not exit cleanly. In that case, the autosave in the temporary directory is the more current recovery source.

Recovery source	Written	Contains	Access method
Autosave (.blend in temp)	Every N minutes during session	Session state at last autosave	File → Recover → Recover Auto Save
quit.blend	On clean Blender exit	Session state at the moment of exit	File → Recover → Recover Last Session
.blend file	On manual Ctrl+S or Save As	Session state at last manual save	File → Open, or recent files
.blend1 file	On every manual save	State from the save before the last	File → Open, navigate to .blend1

quit.blend is written only on clean exit

A power loss does not trigger a clean exit. The quit.blend file may be one or more sessions out of date after a power loss. Use the autosave recovery path rather than Recover Last Session when the interruption was uncontrolled.

Save-as versioning — maintaining a history

For a Unturned mod that develops across multiple sessions, the version number in the filename is the primary mechanism for maintaining a usable history. The following convention applies:

• v1 — the first save of the session, typically covering the base mesh blockout.
• v2 — completed base mesh with clean topology.
• v3 — UV unwrap complete.
• v4 — material assignments complete.
• v5 — export-ready state; FBX has been exported from this version.
• vN+1 — any revision made after the previous version was exported or shared.

The version number advances with File → Save As using a new filename. The previous version is not overwritten; it remains on disk as a permanent record of that milestone state. The working file is always the highest version number.

What versioning costs

Each version is a full copy of the .blend file. A .blend file for a simple prop might be 500 kilobytes. A complex vehicle with packed textures might be 50 megabytes. At ten versions, the space cost is ten times the single-file size. For most mod assets, this is a negligible disk space expenditure in exchange for a complete rollback history. If disk space is constrained, keep the last three versions and archive earlier ones.

Version naming for parallel asset development

When developing multiple assets simultaneously — which is common when building out a complete mod pack — the version number applies per asset, not per session. Two assets in development at the same time maintain independent version counters:

C:\Mods\iron_pack\Blender\
    iron_crate_v1.blend
    iron_crate_v2.blend
    iron_crate_v3.blend       ← current for iron_crate
    iron_locker_v1.blend
    iron_locker_v2.blend      ← current for iron_locker
    iron_barrel_v1.blend      ← current for iron_barrel

Do not use a shared version counter across assets. The version number is meaningful only within the history of a single asset.

Configuring autosave preferences

The autosave system is configured in Edit → Preferences → Save & Load. The relevant settings are:

Preference	Default	Recommended for 57 Studios workflow
Auto Save Temporary File	Enabled	Enabled
Timer (minutes)	2	2 or less
Save Versions	1	3
Compress File	Disabled	Disabled

Why Save Versions = 3

Setting Save Versions to 3 causes Blender to maintain .blend1, .blend2, and .blend3 backup files alongside each .blend file. Each backup contains the session state from the Nth-to-last save. This provides three incremental rollback points for the cost of approximately three times the .blend file size in additional disk space. For a simple prop at 500 kilobytes, three backups cost 1.5 megabytes — negligible.

Why not compress the file

The Compress File setting reduces the size of the .blend file on disk but increases the save time. For autosave, a slow save is worse than a large file, because a slow autosave holds Blender briefly while the file is written. With compression disabled, the save completes faster. The disk space savings from compression are minor on modern drives.

Common save failures and their recovery paths

Failure	Symptom	Recovery
Saved to the wrong folder	Title bar shows unexpected path	File → Save As to the correct folder
Saved with the wrong filename	Wrong asset name in title bar	File → Save As with the correct filename
Saved over a good version with a broken mesh	Mesh is damaged but was the last save	Open the .blend1 backup from File → Open
Closed without saving (Quit Without Saving)	All unsaved work is gone from RAM	File → Recover → Recover Last Session (if Blender exited cleanly) or Recover Auto Save
Autosave fired during a destructive operation	Autosave captured a partially-complete operation	Use the .blend file (last manual save) instead; skip the autosave
File corrupt after power loss mid-write	.blend file fails to open with an error	Try the .blend1 backup; if also corrupt, use the autosave

A save mid-write during power loss may corrupt both the .blend and .blend1 files

In rare cases, a power loss that occurs while Blender is actively writing the .blend file will corrupt the file. Blender writes the new file first, then renames the old file to .blend1. If power is lost between the write and the rename, neither file may be complete. In this case, the autosave in the temporary directory is the last uncorrupted state. This is the worst-case scenario for the .blend + .blend1 protection mechanism, and it is one of the reasons the autosave system is an independent third layer of protection.

Save location for team and multi-machine workflows

A modeler working on a Unturned mod for the 57 Studios ecosystem may work from multiple machines or share source files with a collaborator. The following save location recommendations apply:

Scenario	Recommended location
Solo project, single machine	Local drive at C:\<projects>\<mod>\Blender\
Solo project, multi-machine (e.g., desktop and laptop)	Google Drive-synced folder; ensure Drive is fully synced before opening on either machine
Collaborative project	Shared cloud folder (Google Drive shared drive) with a clear ownership convention: one person edits at a time
Archive or milestone submission	Zip the entire Blender folder and keep the zip as a dated archive

Do not save .blend files to a folder that is syncing while Blender is open

Cloud sync clients (Google Drive, OneDrive, Dropbox) can attempt to sync a .blend file while Blender is writing to it. In some cases, the sync client reads a partially-written file, uploads an incomplete version, and then locks the file briefly. This can cause Blender's save to fail or produce a corrupt file. Either disable the sync client while working, or save to a local drive and move the file to the synced folder at the end of each session.

Post-save verification procedure

After every major save — including the first save and every version advance — execute the following two-step verification. It takes ten seconds and confirms that the save was applied correctly.

Step 1: Open File Explorer and navigate to the save location. Confirm the .blend file exists with the expected filename and modification timestamp. The modification timestamp should be within the last minute.

Step 2: In Blender, confirm the title bar shows the full path to the saved file without an asterisk. An asterisk after the filename means there are unsaved changes since the last save, which should not be the case immediately after a save.

The title bar is the save status indicator

The Blender title bar is the fastest single-glance indicator of save state. No asterisk and the correct path means the file is saved and the path is correct. An asterisk means unsaved changes exist. A path containing AppData\Local\Temp\ means the file is being worked on from a temporary location and has not been saved to the project folder.

FAQ

How large will my .blend files get? A simple prop with no textures will typically be between 200 kilobytes and 2 megabytes. A complex vehicle or map object with packed textures can reach 50 to 100 megabytes. The size depends primarily on texture count and whether textures are embedded in the file or linked externally. For Unturned modding, textures are typically kept external to the .blend file and placed in a dedicated textures folder.

Should I pack textures into the .blend file? Not for Unturned modding work. Packing textures increases the .blend file size significantly and makes the texture files harder to update. Keep textures in a separate Textures\ folder within the mod project, linked externally. The FBX export process handles the texture references independently of the .blend file's packing state.

What is the difference between File → Save and File → Save As? File → Save (Ctrl+S) overwrites the current file at its current path. File → Save As (Ctrl+Shift+S) opens a dialog that allows the modeler to choose a new path or a new filename. For version advances, Save As is the correct command; it writes the new version without touching the previous version file.

Can I rename the .blend file in File Explorer while Blender is open? No. Blender holds the file at the current save path and will continue to save to the old filename even if the file has been renamed in File Explorer. Close Blender before renaming files, or use File → Save As within Blender to rename the active file.

What happens if the disk is full when Blender tries to save? Blender will report a save failure. The file on disk remains in its previous state; the partial write is discarded. Free disk space before retrying the save. A save failure that appears to succeed without a disk-full error but produces a zero-byte file is a sign of a more serious storage problem and should be investigated.

How do I know how old my most recent autosave is? Open File Explorer, navigate to the temporary directory, and check the modification timestamp on the most recent Blender autosave file. The difference between that timestamp and the current time is the age of the most recent autosave. If the autosave was two hours ago, either the autosave system was disabled during the session or something prevented it from running.

Will the autosave fire if Blender is minimized? Yes. The autosave runs on a timer regardless of the Blender window's visibility or focus state. It fires every N minutes as long as Blender is running, whether the window is minimized, maximized, in the foreground, or in the background.

Does Blender keep autosaves from previous sessions? Blender writes new autosave files without deleting old ones. The temporary directory accumulates autosave files from all previous sessions until it is cleared. When recovering, the modeler should select the file with the most recent modification timestamp for the session being recovered.

Can I change the autosave location to something outside the temp directory? Yes. The temporary directory path can be changed in Edit → Preferences → Save & Load → Temporary Directory. Enter any writable path. A dedicated autosave folder on a non-system drive is a valid configuration. The trade-off is that the autosave folder must be available (the drive must be mounted) for the autosave to function.

What if I accidentally overwrite a version I needed to keep? If the overwrite was recent, check the .blend1 file in the same folder. It contains the state from before the overwrite. If multiple versions were overwritten, check whether the older version files still exist under their original version-number filenames. If those files were also overwritten, the work may not be recoverable through any file-based mechanism; the undo history in the current session is the only remaining option.

Should I save before doing a risky operation like applying a modifier or running a destructive script? Yes, always. Before any operation that cannot be undone or that significantly restructures the mesh, save the file first. The save creates a recovery point that is independent of the undo history, which has a fixed depth and can be exhausted. A save before a risky operation costs two seconds; losing the work costs the time it took to produce it.

Is there any reason to keep old version files? Yes. Old version files serve as rollback points. If a texture-painting session in version 5 introduces errors that are not discovered until version 8, the version 5 file can be opened and the mesh state at that point examined. Without the old versions, the only rollback option is the undo history, which does not persist across sessions. Keep old versions until the project ships.

Summary of all save commands

Action	Command	When to use
Save (overwrite current file)	Ctrl+S	Every 10 minutes during a session
Save As (new name or location)	Ctrl+Shift+S	First save of a session; version advances
Save Copy	File → Save Copy	Save a copy without changing the working file path
Recover Auto Save	File → Recover → Recover Auto Save	After a crash or power loss
Recover Last Session	File → Recover → Recover Last Session	After an accidental "Quit Without Saving"
Open .blend1 backup	File → Open, navigate to .blend1	After a bad save overwrote good work

Appendix A — Full power-loss recovery checklist

The following checklist is the complete power-loss recovery procedure in sequential order. Execute each step before proceeding to the next. This checklist can be printed and kept at the workstation.

Step	Action	Expected result
1	Power is restored and the computer has booted	Desktop is visible
2	Do NOT run Disk Cleanup	Temp directory still contains autosave files
3	Open File Explorer	File Explorer window opens
4	Navigate to C:\Users\<username>\AppData\Local\Temp\	Temp directory contents visible
5	Sort by Date Modified, descending	Most recent files at the top
6	Identify the most recent .blend file (8-digit numeric name)	File with most recent modification timestamp located
7	Note the full path to the autosave file	Path recorded mentally or in a note
8	Launch Blender	Blender opens with splash screen
9	Choose File → Recover → Recover Auto Save	Blender file browser opens at temp directory
10	Select the most recent autosave .blend file	File highlighted in browser
11	Click "Recover Auto Save" or press Enter	Recovered session appears in viewport
12	Assess the recovered state	Identify what work is present
13	Immediately choose File → Save As	Save As dialog opens
14	Navigate to the project's Blender folder	Correct destination visible
15	Enter the version-incremented filename	Filename field populated
16	Click Save As or press Enter	File written to project folder
17	Verify file in File Explorer	File present with current timestamp
18	Verify title bar shows project path	No temp directory path in title bar
19	Resume work from recovered state	Session continues

Appendix B — Autosave configuration verification procedure

Before beginning any modeling session, execute the following two-minute verification to confirm the autosave system is active and correctly configured.

Check	Menu path	Expected value
Autosave enabled	Edit → Preferences → Save & Load → Auto Save Temporary File	Checkbox is checked
Autosave interval	Edit → Preferences → Save & Load → Timer (minutes)	2 or less
Save versions	Edit → Preferences → Save & Load → Save Versions	3
Temp directory	Edit → Preferences → Save & Load → Temporary Directory	A path on a writable drive

If any value is not as expected, correct it before beginning work. Close the Preferences window after verification; changes take effect immediately.

Appendix C — Project folder structure template

The following folder structure is the 57 Studios standard for a Unturned mod project that includes Blender source files. Create this structure at the start of every new mod project, before the first save.

C:\<your projects folder>\<mod_name>\
│
├── Blender\
│   ├── <asset_name>_v1.blend        ← working file, current version
│   ├── <asset_name>_v1.blend1       ← Blender-generated backup (automatic)
│   └── (additional assets and versions as the project grows)
│
├── Unity\
│   └── Assets\
│       ├── Models\
│       │   └── <asset_name>.fbx     ← exported from Blender
│       ├── Textures\
│       │   └── <asset_name>_d.png   ← diffuse texture
│       └── (additional Unity asset folders)
│
├── Textures\
│   └── <asset_name>_d.psd           ← source texture files (not imported by Unity)
│
└── Reference\
    └── (reference images, dimension sheets, community photos)

The Blender\ folder and the Unity\ folder are siblings at the top of the mod project directory. The Blender\ folder never sits inside Unity\Assets\. The separation prevents Unity from attempting to import the .blend files directly.

The Textures\ folder at the project root holds the source texture files (Photoshop .psd, Krita .kra, or equivalent). The exported .png textures used by Unity live inside Unity\Assets\Textures\. This separation preserves the source texture files while keeping the Unity project import-ready.

Appendix D — The .blend file format internals

Understanding what a .blend file contains helps the modeler make informed decisions about file size, backup strategy, and what will be lost if a file is not recoverable.

A .blend file is a binary container. It stores every data block that Blender has allocated for the current session: objects, meshes, materials, textures, images, cameras, lights, world settings, render settings, workspace layouts, node trees, and the undo history. The format is structured as a sequence of blocks, each with a header identifying the block type and a body containing the block data.

Data category	Stored in .blend	Notes
Object transforms (position, rotation, scale)	Yes	Exact values preserved
Mesh geometry (vertices, edges, faces)	Yes	Complete topology
UV maps	Yes	All UV layers
Materials and shader node trees	Yes	Unless linked externally
Image textures — embedded	Yes	Increases file size significantly
Image textures — linked externally	Path only	Texture data lives in the external file
Modifier stack	Yes	Including modifier settings
Armatures and pose data	Yes
Scene settings and render properties	Yes
Workspace and panel layout	Yes
Undo history	Yes, partially	Limited by undo step count setting
Python add-on code	No	Add-on code lives in the Blender installation
Linked library data	Path only	Data lives in the linked .blend file

The distinction between embedded and linked textures is particularly relevant for file size. A .blend file that has textures packed into it using File → External Data → Pack Resources will be significantly larger than one with textures linked externally. For the 57 Studios workflow, textures are kept external: they live in the project's Textures\ folder and are referenced by path from the .blend file. This keeps the .blend file smaller, makes texture updates independent of the .blend save cycle, and allows the same texture to be shared between multiple .blend files without duplication.

Linked textures and file moves

A .blend file that references textures by path will report missing textures if the file is moved to a different folder or a different machine. The texture paths recorded in the file no longer point to existing files. When moving a project, move the entire folder structure together, preserving the relative paths between the Blender\ folder and the Textures\ folder. Blender's File → External Data → Make Paths Relative command converts absolute texture paths to relative paths, which remain valid as long as the folder structure is preserved.

Appendix E — Versioning with Save Copy vs. Save As

Blender provides a third save-related command that is distinct from both Save (Ctrl+S) and Save As (Ctrl+Shift+S): File → Save Copy. The three commands behave differently in a way that matters for version management.

Command	Writes a new file	Changes the working path	Keeps unsaved flag	Use case
File → Save (Ctrl+S)	No — overwrites current	No — path unchanged	No	Incremental save during a session
File → Save As (Ctrl+Shift+S)	Yes — new file at new path	Yes — Blender now works from the new file	No	Version advance; first save; rename
File → Save Copy	Yes — new file at specified path	No — Blender continues working from the original	Yes	Snapshot without disrupting the working session

Save Copy is useful when the modeler wants to create a milestone snapshot of the current state without advancing the working file to a new version. For example, a modeler working on version 3 of an asset who wants to save an exploratory branch without committing to it as the new working version can use Save Copy to write the branch to disk, then continue working in the version 3 file.

Save Copy for sharing

Save Copy is also useful for sharing a file with a collaborator. The modeler uses File → Save Copy to write the current state to a path the collaborator can access, without disrupting the modeler's own working file path or version counter. The copy is a complete independent .blend file; the collaborator can open and modify it without affecting the original.

Appendix F — Recovery decision tree

When a session ends unexpectedly and the modeler is uncertain which recovery path to take, the following decision tree provides a step-by-step guide to identifying the correct starting point.

The decision tree terminates in one of four outcomes: reopening the manual save directly, opening the .blend1 backup, recovering from autosave, or re-doing work from the last good state. The last outcome is the only one that represents an unrecoverable loss.

Appendix G — Session save log discipline

Experienced modelers who work on long projects maintain a session save log: a short text file kept alongside the .blend files that records the date, the version number saved, and the state of the model at that version. The log is not required by the 57 Studios workflow, but modelers who maintain one report that it significantly reduces the time spent re-establishing context at the start of a new session.

A simple session save log looks like this:

iron_crate — Save Log
=====================

2026-05-14  v1  Base mesh blockout complete. Eight-sided cylinder top, box body. No UV.
2026-05-15  v2  Topology cleanup. Loop cuts for lid detail. No UV.
2026-05-16  v3  UV unwrap complete. Checker texture applied for distortion check.
2026-05-17  v4  Material assignments. Four materials: body, lid, handle, latch.
2026-05-18  v5  Export-ready. FBX exported to Unity\Assets\Models\iron_crate.fbx.

The log requires less than one minute to update at the end of each session. It answers two questions that are otherwise answered by opening the .blend file and examining its state: "Where did I leave off?" and "What version is the working file at?" Both questions arise at the start of every return session, and answering them from a text file is faster than answering them from the .blend file itself.

The log also serves as the definitive record of which version was exported to Unity at each milestone. When a modeler discovers a mesh error in Unity and needs to know which Blender version corresponds to the imported FBX, the save log provides the answer.

Workflow placement

The first file save occupies the third position in the 57 Studios Blender setup track: after installation and after the default cube deletion, but before any real modeling begins. Establishing the correct file path and naming convention before modeling starts means every subsequent save in the session lands in the right place. A modeler who delays the first Save As until after significant modeling work risks discovering that all their intermediate saves went to a temporary or default location rather than the project folder.

Closing notes

The save procedures described in this article are not complex. Each one — Ctrl+S, File → Save As, locating the .blend1 file, running File → Recover → Recover Auto Save — takes seconds to execute once learned. The difficulty is not in the execution; it is in the discipline of executing them at the right intervals and in the right situations.

A modeler who saves every ten minutes during an active session, advances the version number at each meaningful milestone, and verifies the save location in the title bar after each Save As will not lose more than ten minutes of work to any single failure event. A modeler who does none of those things will eventually lose a session they cannot recover. The difference between these two outcomes is not hardware, not software version, and not luck. It is procedure.

The 57 Studios workflow documentation treats save discipline as a professional practice because the consequence of not practicing it is real and quantifiable: hours of work, permanently gone. A Unturned mod that represents twenty hours of modeling, UV work, and material setup is worth protecting with ten seconds of Ctrl+S every ten minutes.

The save cadence and the creative flow

A common objection to frequent saving is that it interrupts the creative flow of a modeling session. This objection misunderstands what Ctrl+S does. The shortcut takes less than one second on any modern computer with a solid-state drive. The visual confirmation — the title bar asterisk disappearing — takes one additional second to observe. Two seconds out of every ten minutes is 0.3% of the session's time. The creative flow is not interrupted by a two-second save. It is permanently interrupted by a crash that destroys an hour of unsaved work.

Glossary

Term	Definition
.blend file	Blender's native binary file format. Contains the complete session state: objects, geometry, materials, settings, and undo history.
.blend1 file	An automatic backup of the previous save state. Written by Blender to the same folder as the .blend file every time a save occurs.
Autosave	A Blender feature that writes the current session state to the temporary directory at regular intervals, independent of manual saves.
Save As	The Blender command (Ctrl+Shift+S) that opens a file browser, allowing the modeler to specify a new filename or path. The working file path changes to the new file after Save As completes.
Save Copy	A Blender command that writes a copy of the current state to a specified path without changing the working file path.
Temporary directory	The folder where Blender writes its autosave files. Default: C:\Users\<username>\AppData\Local\Temp\.
Orphaned data block	A data block in Blender's memory that is no longer referenced by any object. Removed by File → Clean Up → Purge All.
Title bar	The bar at the top of the Blender window that displays the application name, version, and the full path of the current file. An asterisk before the filename indicates unsaved changes.
quit.blend	A recovery file written by Blender when it exits cleanly. Located in the user preferences folder. Accessed via File → Recover → Recover Last Session.
Save Versions	A Blender preference that controls how many numbered backup files (.blend1, .blend2, etc.) are maintained alongside each .blend file.
FBX	Filmbox format. The exchange format used to transfer geometry from Blender to Unity for Unturned mod assets.
Snake case	A naming convention that uses lowercase letters and underscores in place of spaces. Used for all file and folder names in the 57 Studios workflow.

Next steps

Continue to How to Navigate the Blender Viewport to learn the mouse and numpad controls for moving through a three-dimensional scene. Every navigation action builds on the saved file established in this article.