The scene looks simple, yet the file is hundreds of megabytes and every save takes a while. A .blend keeps much more than what you see in the viewport.
What makes a .blend heavy
- Packed files. Images, HDRIs and fonts packed into the .blend (File > External Data > Pack Resources) are stored inside it, at full size.
- Data kept with a Fake User. A block with a Fake User (the shield icon) stays in the file even if nothing uses it: old materials, test meshes, imported assets.
- Leftovers of deleted objects. Delete an object and its mesh and materials stay in the file for a while. Blender does not save a block that nobody uses, but a material used only by an unused mesh still counts as used, so the chain goes away one save and reload at a time.
- Duplicates. Appending the same asset twice gives
Wood.001,Wood.002: the same material and its images, several times. - Heavy geometry and caches: high-poly meshes and simulation caches.
With Blender alone
See the unused data: in the Outliner, switch the display mode to Unused Data (called Orphan Data in older versions). It lists the blocks nothing uses.
Remove it: File > Clean Up > Purge Unused Data. Turn on the recursive option to remove the whole chain (the mesh, then its material, then its images) in one go, then save.
Unpack big files: File > External Data > Unpack Resources writes packed files back to disk next to the .blend.
What to know:
- Purge removes everything unused at once, without showing you what goes.
- Blocks with a Fake User are never purged. To find them you look through the Blender File view of the Outliner.
- Missing external files are a separate check (File > External Data > Report Missing Files).
With DataSweep: see it all, then choose
DataSweep is a Blender add-on that scans the open file and lists what is left over before you remove anything:
- Orphan blocks: nothing uses them and they have no Fake User.
- Protected blocks: kept only by their Fake User.
- Missing blocks: they point to an external file that is not on disk and not packed.
- Linked blocks: they come from another .blend, read only.
From that list you can:
- Filter by status, type, name or size, and sort.
- Remove one block, the checked blocks, or everything visible.
- Protect blocks with a Fake User, or take it away.
- Keep blocks out of every scan with the Safe List, for a material library you keep on purpose.
- Relink missing files from a folder and its subfolders, all in one go.
- Export a report as CSV, HTML, JSON or Excel, as proof for a client.
Smaller files, faster saves, a clean, light scene. DataSweep also comes with Conduit in the Conduit + DataSweep bundle.