Keep your Revit model lean by routinely purging unused families and types to improve performance, reduce file size, and cut sync/open times.
Safe, repeatable workflow:
- Create a detached copy (or a new local from central). Save a timestamped backup.
- Close unnecessary worksets before starting to limit memory footprint while reviewing.
- In the Project Browser, quickly audit likely culprits (multiple similar wall/door/window types, legacy detail items, old titleblocks, view templates you no longer apply).
- Run Manage > Purge Unused. Expand the tree to review what will be removed; deselect anything you expect to use later.
- Run Purge Unused multiple times until nothing remains. Some dependencies are exposed only after the first pass.
- Compact on save (and recreate the central if applicable) to realize the full size reduction.
What Purge Unused targets effectively:
- Unplaced family types (doors, windows, detail items, profiles, etc.).
- Unused system types (wall/roof/floor types, line styles, fill patterns, filters, view templates).
- Unused imported styles and obsolete pattern/line pattern definitions.
Important cautions:
- Schedules that filter by a type with zero instances do not “protect” that type; purge can remove it, breaking that filter. Either place a hidden instance on a non-printing workset or revise the schedule filter before purging.
- View Templates and Filters referencing categories or patterns you still need will prevent purge; clean or consolidate them first.
- Groups, Design Options, and nested families can hold references. Review those containers before assuming a type is safe to remove.
- Materials tied to appearance assets or to unpurged types may persist. Consider consolidating duplicate materials and removing unused assets in the Materials dialog after the purge.
Smart housekeeping habits:
- Adopt naming standards so duplicates are obvious (e.g., “Wall – INT – GWB 1hr – 4-7/8” vs “Wall-Interior-1hr”).
- Maintain a “Parking” drafting view for sample types you intentionally keep (legend components, annotation samples). Place a single instance there to prevent accidental purging.
- Replace rarely used “one-off” in-place content with reusable loadable families where possible to reduce bloat.
- Use Transfer Project Standards sparingly; bring in only the specific styles/line patterns you need to avoid reintroducing clutter.
- Track file size and open/sync times; if growth spikes after milestones, schedule a purge cycle.
Verification checklist after purging:
- Open key sheets and coordination views to confirm graphics and tags are intact.
- Review discipline-specific schedules (doors, finishes, equipment) for missing filters or type rows.
- Synchronize and have teammates reload latest to validate that no borrowed elements or view templates were impacted.
Tip: For large offices, automate a “zero-instance” report with Dynamo or the API before purging to document what’s being removed. Need tools, training, or licensing support? Explore Autodesk Revit solutions at NOVEDGE. If you accidentally remove a needed standard, you can quickly reload the family from your library or use Transfer Project Standards from a clean template sourced via NOVEDGE.






