News

Revit model performance: slow models, crashes and damaged files

Revit model performance in 2027: seven causes of a slow model, the order to clean it, Purge Unused, Review Warnings, the Audit box and backup recovery.

  • Dr. Nguyen Manh Tuan
  • 10 min read
Six steps for cleaning a heavy model, in the order they have to be done Photo: Diagram by the Institute of Information Technology in Civil Engineering

Poor Revit model performance is rarely the machine's fault. Most of it comes from what accumulates inside the file: warnings piling up, families never once placed, draft views left behind, every link loaded at once.

This article shows how to find those, clear them in the right order, and what to do once a file is already damaged. To learn modelling and documentation end to end, see the Revit Architecture course.

Seven common reasons a Revit model runs slowly

CauseWhat to do
Too many views openEvery open view is another region to redraw. Use Close Inactive on the View tab
Detail level too highFine on a wide view forces Revit to draw every construction layer. Work at Coarse
3D trees and peopleImage-heavy families slow down every operation
Nested groupsA group inside a group makes every edit recalculate several times over
Every link loadedUnload the links you do not need to see
Accumulated warningsEach warning is a constraint Revit re-checks after every change
Shadows left on while modellingTurn Cast Shadows off unless you are producing imagery

The last two deserve most attention because few people think of them. Shadows left on mean every orbit is recomputed, and warnings quietly accumulate.

Unloading links is covered in linking Revit models, and nested groups in groups in Revit. Autodesk gathers its performance advice on Memory Usage and Instability.

Revit review warnings: a list that only ever grows

Revit records every warning the user has dismissed. That list never shortens by itself, and a model carrying a few thousand warnings is both slow and hard to trust.

Both commands live on the Manage tab, Inquiry panel.

CommandWhat it does
Select by IDPaste an element id and Revit selects that exact element
Review WarningsOpens the list of every warning in the model
The warnings dialog Photo: The warning tree, three action buttons and Export
No.ComponentWhat it means
1The warning treeGrouped by message. Expand a branch to see each individual case
2Three buttonsShow jumps to the element; More Info explains further; Delete Checked deletes the ticked elements
3Export and CloseExport writes the list to a file so several people can share the work

Delete Checked deletes elements, not warnings. Read carefully before clicking: most warnings are cleared by correcting the model, not by deleting what it contains.

The dialog does not lock the screen. Most view navigation still works while it is open, so the list can be read while orbiting the model. Autodesk documents the command on Review Warning Messages.

Sorting warnings by how serious they are

Not every warning is worth the effort. Three groups make the order of work obvious.

LevelWhat belongs in it
Fix nowOverlapping elements, unenclosed rooms, orphaned components. These make quantities and drawings wrong
Should fixUnsatisfied constraints, duplicated elements. These slow the model and make later edits harder
Can waitOverlapping tags, text running out of its box. These affect only the sheet and are settled at layout
Review Warnings on a large project Photo: The three commonest warning types once a model has grown
No.ComponentWhat it means
1The first two warningsElements that join but do not intersect, and one element wholly inside another. The two commonest geometric faults
2Overlapping areasArea and perimeter collapse into one region while the others read Redundant. Schedules are wrong as a result
3The Export and Close buttonsExport writes the whole list out. On a large project this is the only way to share the fixing between several people

On a large model the warning list never quite reaches zero. The model manager's job is to keep it short, and free of the faults that corrupt numbers.

The cheapest routine is a weekly slot: open Review Warnings and clear the fix-now group. Fifteen minutes a week costs far less than three days spent cleaning a model that has reached two thousand warnings.

Purge Unused in Revit, and the number 1160

A model grows heavier as it goes, and most of that weight is material never used. Purge Unused, on the Manage tab, Settings panel, clears it out.

The Purge Unused dialog Photo: The Views and Families groups with the checked item count
No.ComponentWhat it means
1ViewsUnused views. The 2027 release folds views into the purge list, not only families as very old releases did
2FamiliesFamilies and types never once placed in the model. This is most of the list
3Number of items checkedHow many entries are ticked. On an almost empty test project the figure was already 1160

That number is worth remembering: it is everything the template carries that nobody has used. A real project of a few months usually carries considerably more.

The command is safe — only unconstrained, unused entries can go. But it also removes types you were deliberately keeping, so clear their ticks before clicking OK.

Run it three times over: the first pass removes unused families, which in turn leaves some materials and types unused, so a second pass still finds more. Autodesk also advises backing the file up first, on Purge Unused Objects.

The shortcut is PU, from the same group as ML and IF in Revit keyboard shortcuts.

Six steps to reduce Revit file size, in order

The order matters more than any single command. Purging before the warnings are fixed wastes most of the effort.

  1. Open Review Warnings and clear the fix-now group.
  2. Delete draft views no longer in use, and abandoned sheets.
  3. Unload the links you no longer need to see.
  4. Run Purge Unused, clearing the ticks on types you want to keep.
  5. Close the file and reopen it through Open with the Audit box ticked.
  6. Record the file size before and after, to learn whether the cleaning worked.

Step 6 is the one usually skipped. Without measuring, next time you still will not know which step earned its time.

Audit a Revit file, and how often to run it

The File, Open menu Photo: The sub-items of the Open command
The Open dialog with the Audit box Photo: The Audit box at the lower left of the Open dialog
No.ComponentWhat it means
1AuditMakes Revit check the whole file structure and repair what it finds while opening. Far slower than a normal open
2WorksharingDetach from Central and Create New Local, active only on a workshared file

Audit is the first move whenever a file behaves oddly: very slow to open, an error on saving, or one view that refuses to open. Run it, save, and most cases are settled.

On frequency there are two different recommendations, and both are worth knowing. Autodesk advises a weekly audit, more often on a fast-changing model, on Best Practices: Preventing Data Corruption. The practice taught at the Institute is narrower: run it on symptoms and before each major issue, because an audit is slow and does nothing for a healthy file.

Recover a corrupt Revit file from a backup

On every save, Revit keeps the previous version as a backup in the same folder, its name carrying a sequence number. How many are kept is set in Save As, under Options.

Backups rescue more files than anything else: rename a backup to .rvt and it opens as an ordinary project.

What can and cannot be rescued Photo: Three groups of symptoms and the treatment for each
SymptomTreatment
Unusually slow to openRecoverable. Run Audit, then Purge Unused
One view errors when openedUsually recoverable. Delete that view and rebuild it
Revit quits while opening the fileTry the most recent backup. If that is damaged too, step further back
File truncated by a power cut mid-saveUsually not recoverable. Use a backup
Saved by a newer Revit releaseCannot be opened by an older release, and there is no way to downgrade

That last row is why a team must agree one Revit release at the start of a project. One person upgrading and saving forces everyone to follow, with no way back.

Try it: clean a model and measure the result

A thirty-minute exercise. It works through Revit model performance end to end; use a copy of a real model, never the live file.

  1. Record the file size before starting.
  2. Go to Manage, Inquiry panel, click Review Warnings. Note the total.
  3. Sort them into the three severity groups, then clear the fix-now group.
  4. Click Export to save the remaining list to a file.
  5. Delete draft views and unused sheets.
  6. Go to Insert, Manage Links, and unload the links you do not need.
  7. Run Purge Unused, note the Number of items checked, then click OK.
  8. Run it a second and third time, noting the figure each time.
  9. Close the file, reopen through Open with Audit ticked, then save.
  10. Record the final file size and compare it with step 1.

Step 8 shows most clearly why the command has to be run repeatedly: the second figure is rarely zero.

Frequently asked questions

Can Purge Unused delete something I am using?

No. It removes only unused, unconstrained entries. It does remove types you were deliberately keeping, so clear their ticks before clicking OK.

Should I audit the file every day?

Autodesk recommends a weekly audit. In practice, running it when the file shows symptoms and before each major issue is enough, because an audit is slow.

Can I clear warnings with Delete Checked?

Better not. That button deletes elements rather than warnings. Most warnings are cleared by correcting the model.

A file was saved in a newer Revit release. How do I open it in an older one?

You cannot, and there is no downgrade path. Someone with the newer release has to export an intermediate format.

About the author

Dr. Nguyen Manh Tuan — BIM lecturer at the Institute of Information Technology in Civil Engineering – Hanoi University of Civil Engineering