Sharing and Recovering Blender Projects: 7 Steps for External Files

When you send a Blender project to another computer, sharing only the .blend file may not be enough to transfer all of the scene’s assets. Blender’s official documentation explains how to pack eligible external files into a project, preserve relative paths when moving files together, and recover work after an unexpected shutdown. This guide walks through those methods for project delivery and archiving. Menu names follow the wording in Blender’s current online manual.

1. Identify the project’s external assets

Blender projects can reference assets stored outside the .blend file, such as images. If these files are moved or their location changes, Blender may not be able to find them when the project is opened. The documentation describes two ways to reduce this risk: store external assets inside the .blend file or move them alongside the project file.

Packing can give you a single file to share, but not every external file can be included this way. The documentation notes that some large files, such as Sequence Editor videos and Movie Clips, cannot be packed. Before delivery, check which files the scene depends on and whether they can be packed.

2. Pack eligible assets into the .blend file

1. Open the project in Blender and go to File › External Data › Pack Resources. This command marks packable external assets used by the .blend file for packing.

2. Save the .blend file. Packing happens the next time the file is saved, not as soon as you run the command. If you quit Blender without saving, the packing process will not be completed.

3. To have resources packed automatically, enable File › External Data › Automatically Pack Resources. This marks eligible files, both existing and newly added, for packing; you still need to save the file for the change to take effect.

4. To manage an asset individually, use the small gift-box icon next to its file path field. The documentation explains that this icon lets you selectively pack a single file.

Turning off automatic packing does not unpack files that have already been packed. It only stops future external assets from being packed automatically. Linked libraries also have a separate command, File › External Data › Pack Linked Libraries; its effect likewise takes place on the next save.

3. Preserve relative paths if you’re sharing a folder instead of a single file

If you don’t want to embed assets in the .blend file, you can keep the project file in a folder with its linked images and other external files. When selecting an external asset in Blender, a relative path is the default. It defines the asset’s location in relation to the directory containing the .blend file. This makes it easier to preserve links when moving the .blend file and its assets together.

When saving the file to another location, the Remap Relative option in Save As remaps relative paths to the new location. Keep in mind that relative paths cannot be used in a new, not-yet-saved .blend file: save the project before linking external assets.

4. Don’t run scripts automatically in files you don’t trust

If Trusted Source is enabled when opening a .blend file, any Python scripts and drivers it contains will run automatically. The official manual recommends enabling this option only if you created the file yourself or trust the person who sent it. Check this setting carefully when opening a file from someone else.

If you don’t want the workspace layout inside the file to change your current interface, you can turn off Load UI in the file browser. This setting determines whether the screen layout and workspaces saved in the file are loaded; it does not perform the same function as packing external assets.

5. Build a saving and backup routine

File › Save or Ctrl-S saves the current .blend file. For a new project, this command opens the save dialog. Use Save As to choose a different name or location. Pay attention to the warning in the save dialog if you may be overwriting an existing file with the same name.

You can use Save Copy to create a copy of the current work and continue editing the original file. If you need incremental naming, Save Incremental creates a numbered file without overwriting existing files. To reduce file size, use the Compress option in Save As; however, the documentation notes that compression can increase save and load times and may also slow down automatic backups.

6. Try the recovery options after an unexpected shutdown

When Blender opens, File › Recover › Last Session loads the quit.blend file that was automatically saved before the program closed. File › Recover › Auto Save opens a file browser in the temporary directory to locate the nearest auto-save. You can configure the auto-save interval and behavior in Auto Save Preferences.

These methods won’t restore every change. Blender keeps only one auto-save per project; changes made since the last auto-save may be lost during recovery, and older auto-saves are not retained. Auto-save also does not save changes made in Sculpt, Texture Paint, and Edit modes. Don’t treat recovery as a substitute for saving regularly.

7. Common mistakes

• Closing the file without saving after running the packing command: packing happens on the next save.

• Sending only the .blend file and forgetting unpacked external assets: the project may not look as expected if Blender cannot find those assets.

• Breaking the relative path structure when moving files: for relative paths to work, linked assets must also be moved in suitable locations.

• Assuming auto-save covers every editing mode: the documentation specifically notes its limitations for changes made in Sculpt, Texture Paint, and Edit modes.

• Enabling Trusted Source without considering the risks in a file you don’t recognize: this setting allows Python scripts and drivers in the file to run automatically.

Impact on architectural visualization workflows

For architectural scenes that use textures and linked libraries, packing can reduce a delivered project’s dependence on external assets. For teams that keep assets separate, moving a folder organized with relative paths alongside the .blend file is a practical alternative. The right choice depends on whether the file will be handed over as a single .blend or as a folder structure.

For offices, adding a packing and reopening check before delivery can help manage the risk of missing assets. Large files, media that cannot be packed, and the effect of compression on save and load times should also be considered. Rather than relying on auto-recovery, combine regular saving with the option to create a separate copy. Since this documentation does not provide information about hardware requirements or licensing costs, no specific conclusions can be drawn on those topics.

Scope: These steps are based on features in Blender’s current online manual. The manual states that the compression algorithm was Gzip before Blender 3.0 and that Zstandard has been used since 3.0. This version note is limited to the history of the compression algorithm.

Safest check before sharing a project: Pack eligible assets, save the .blend file, and, if possible, reopen the copy you plan to deliver to verify its links.