01 / 21

Purging &
Performance

Learn to purge unused items and manage model size so your Revit projects stay fast, lean, and collaborative.

Autodesk Revit

What is Model Bloat?

Every time you load a family, create a type, import a CAD file, or add a material, Revit stores that data inside the project file: even if you later delete the element that used it. Over weeks and months, these orphaned items accumulate and inflate your file size.

Why Performance Matters

Open/Save Time
Bloated models take longer to open, save, and sync: costing minutes every hour.
Collaboration
Large central files slow every team member's worksharing sync and reload.
Navigation
Excess data bogs down view regeneration, orbiting, and section box adjustments.

The Anatomy of File Size

Families
Views
Imports
Other
\(\sim 35\%\) : loaded families & types
\(\sim 20\%\) : views & sheets
\(\sim 20\%\) : CAD imports & images
\(\sim 25\%\) : materials, patterns, etc.
Typical Revit file composition

The Purge Principle

If an element, family, type, material, or imported file is not placed in any view or referenced by any other element, it is safe to purge. Revit tracks these references internally: the Purge Unused tool simply queries that database.

Load
Place
Delete
Orphan
Purge
Lifecycle of an element in a Revit project

Using Purge Unused

1
Open the tool: Manage tab → Settings panel → Purge Unused.
2
Check All: The dialog lists every category with unused items. Click "Check All" to select everything.
3
Review selectively: Uncheck families you plan to place later (e.g., placeholder types for future phases).
4
Click OK. Revit removes all checked items from the project database.
5
Repeat \(2\) – \(3\) times. Some families reference other families: purging once may unlock new orphans.

Purge vs. Delete

Purge Unused Delete
What it targets Unplaced types, families, materials, line patterns Specific placed instances in views
Removes from project? Yes: removes the definition entirely Only the instance: the type stays behind
Risk level Low: only removes items with zero references Medium: may delete elements others need
Reversible? Only via Undo (before save) Only via Undo (before save)

Beyond Purge: Performance Strategies

Worksets
Close worksets you're not editing to reduce memory usage and view regeneration time.
Linked Files
Use Revit links instead of importing: links stay external and keep the host file small.
View Detail
Set Detail Level to Coarse or Medium when fine detail isn't needed.

Step-by-Step Cleanup Workflow

1
Audit the file: Open with "Audit" checked to repair database errors first.
2
Remove CAD imports: Check Manage Links & Imported Categories. Delete anything not essential.
3
Delete unused views & sheets: Views consume memory even if never printed.
4
Run Purge Unused \(3\) times: Each pass can reveal newly orphaned items.
5
Compact the file: Save As → Options → check "Compact Central Model" to reclaim disk space.

Example 1: Simple Purge

Before
\(185\) MB
After
\(108\) MB
\(-42\%\)
Steps taken:
1. Deleted \(12\) unused CAD imports
2. Ran Purge Unused \(3\) times (removed \(340+\) families)
3. Saved with Compact option

Example 2: Identifying Heavy Families

Not all families are equal. Some families contain imported geometry (meshes, DWG solids) that makes them disproportionately large. You can spot them by checking the family file size before loading.

Chair (native)
\(0.3\) MB
Chair (imported mesh)
\(4.8\) MB
Tree (native)
\(0.5\) MB
Tree (SketchUp import)
\(12\) MB

Example 3: Team Cleanup Protocol

On a workshared project, only the BIM manager should run Purge Unused on the central file. Running it from a local file can cause sync conflicts.

Central File
BIM Manager
Purge + Compact
Team Members
Team Members
Sync only
Sync only

The CAD Import Trap

Importing a DWG or DXF file embeds every layer, block, and hatch into the Revit project. Even a small CAD file can add hundreds of line styles and fill patterns to the database.

Link (preferred)
CAD data stays external. Easy to update or remove. Minimal file impact.
Import (avoid)
CAD data merges into the project. Hard to fully remove. Inflates line styles.

Managing Views for Speed

1
Delete working views: Temporary 3D views, test sections, and duplicates add up quickly.
2
Close inactive views: Every open view tab consumes RAM. Close views you're not actively editing.
3
Use View Templates: Consistent settings prevent accidental detail-level overrides that slow regeneration.

Common Mistakes

✕ Purging Only Once
Nested families create chains of dependencies. A single pass may leave orphans that are only exposed after the first purge.
✕ Importing Instead of Linking
CAD imports embed hundreds of styles. Always link CAD files: then delete the link when you're done referencing them.
✕ Never Compacting
Purging removes data from the database, but the file on disk may not shrink until you "Save As" with the Compact option checked.

Performance Cheat Sheet

Strategy Impact Frequency
Purge Unused (\(3 \times \)) High Weekly
Remove CAD Imports High After each trace
Delete Unused Views Medium Bi-weekly
Close Worksets Medium Daily
Compact on Save Medium Weekly
Audit on Open Low-Medium Monthly
Rebuild Heavy Families High As discovered

Question 1 of 5

Where do you find the Purge Unused command in Revit?

Question 2 of 5

Why should you run Purge Unused multiple times in a row?

Question 3 of 5

Which approach is preferred when you need to reference a DWG floor plan in Revit?

Question 4 of 5

After purging unused items, your file is still the same size on disk. What step did you likely skip?

Question 5 of 5

On a workshared project, who should typically run Purge Unused on the central file?