Recovering a Corrupted Revit Central Model: Step-by-Step Disaster Recovery
Diagnostic and recovery procedures for corrupted Revit central models, including worksharing recovery, journal file rollback, and backup restoration techniques.

Recovering a Corrupted Revit Central Model: Step-by-Step Disaster Recovery
A corrupted central model in Revit is every BIM coordinator's nightmare. I've been the person everyone stares at when the central model won't open and 12 people can't sync their work. Over the years, I've dealt with corrupted centrals more times than I'd like to admit, and I've learned that there's a definite escalation path — start with the gentle stuff, and only go nuclear if you have to. Here's my recovery playbook, ordered from least to most aggressive.
Understanding Central Model Corruption
Revit's worksharing architecture stores all project data in a central model file (.rvt). Each team member creates a local copy that synchronizes with the central model. Corruption can occur in:
- The central model itself: The
.rvtfile on the network server is damaged. - Worksharing metadata: The internal database that tracks element ownership and worksets is inconsistent.
- Local model conflicts: A user's local copy has diverged from the central model in a way that causes sync failures.
Common causes include network interruptions during synchronization, storage drive failures, improper shutdowns while Revit is saving, and exceeding the 2 GB file size threshold for RVT files.
Method 1: Reload Latest from Central
The simplest recovery is to discard the local model and reload from central. This works when the central model is intact but a local copy has become corrupted.
- Close Revit.
- Navigate to the local model file and rename it (e.g.,
Project_Local.rvttoProject_Local_corrupt.rvt). Do not delete it — you may need it for element recovery later. - Open Revit and go to File > Open.
- Check the "Create New Local" option in the Open dialog.
- Navigate to the central model on the network server and click Open.
- Revit creates a fresh local copy from the central model.
If this resolves the issue, the corruption was limited to the local model. If the central model itself is corrupted, proceed to Method 2.
Method 2: Use the Revit Backup Folder
Revit automatically maintains backup copies of the central model in a backup folder. The folder is named by appending _backup to the central model filename.
Locate the Backup Folder
If the central model is at:
\\server\projects\ProjectA\ProjectA_Central.rvt
The backup folder is at:
\\server\projects\ProjectA\ProjectA_Central_backup\
Inside this folder, you will find numbered backup files (typically up to 20 backups are retained):
0001.rvt
0002.rvt
0003.rvt
...
The highest-numbered file is the most recent backup.
Restore from Backup
- Close Revit on all workstations. Ensure no user has the central model open.
- Rename the corrupted central model:
ProjectA_Central.rvttoProjectA_Central_corrupt.rvt. - Copy the highest-numbered backup file from the backup folder to the project directory.
- Rename the copied file to
ProjectA_Central.rvt. - Open the restored file in Revit.
- Go to File > Save As > Project.
- Overwrite the central model location and configure worksharing settings.
Data loss: The backup may be missing the most recent synchronization. Any work done after the last backup will need to be recreated. Inform the team and identify which users had unsynchronized work.
Method 3: Use the Journal File to Identify the Last Good State
Revit maintains a journal file that records every operation performed during a session. The journal can help identify exactly when corruption occurred and which elements were affected.
Locate the Journal File
Journal files are stored at:
%LOCALAPPDATA%\Autodesk\Revit\Autodesk Revit 2026\Journals\
Files are named revit.log####.txt where #### is a sequential number. The most recent session has the highest number.
Analyze the Journal
Open the journal file in a text editor and search for:
Error: General errors logged during the sessionCorruption: Specific corruption warningsException: Unhandled exceptions that may indicate the corruption eventDBG_WARN: Warnings about element integrity
Look for the timestamp of the first corruption-related entry. This tells you when the problem began, which helps you identify which backup to restore from.
Roll Back Using Journal
Revit can replay a journal file to restore the model to a specific state:
- Close Revit.
- Copy the journal file to a safe location.
- Open a command prompt and navigate to the Revit installation directory:
cd "C:\Program Files\Autodesk\Revit 2026" - Launch Revit with the journal file:
Revit.exe /j "C:\Path\To\revit.log0123.txt" - Revit replays all operations from the journal, rebuilding the model state up to the point of corruption.
This method is time-consuming and not always successful, but it can recover work that was not yet synchronized to the central model.
Method 4: Audit and Recover from within Revit
Revit includes built-in audit tools that can repair internal database inconsistencies.
Open with Audit
-
Go to File > Open.
-
Check the "Audit" checkbox in the Open dialog.
-
Select the central model and click Open.
-
Revit performs a comprehensive integrity check:
- Validates all element references
- Repairs corrupted parameter data
- Removes orphaned elements
- Rebuilds the worksharing metadata
-
After the audit completes, review the warning dialog for the number of issues found and fixed.
-
Save the file and synchronize to central.
Open with Detach from Central
If the audit fails or the file still crashes after audit:
- Go to File > Open.
- Check "Detach from Central."
- Select the central model and click Open.
- In the Detach dialog, select "Detach and discard worksets."
- The file opens as a standalone model without worksharing.
- Go to File > Save As > Project.
- Save as a new central model with worksharing re-enabled:
- Check "Create central model" in the Save As dialog.
- Set the central model location on the network server.
This strips all worksharing metadata and creates a clean central model. The tradeoff is that all workset assignments are lost and must be recreated.
Method 5: Extract Elements from a Corrupt Local Model
If a user's local model contains unsynchronized work that you need to recover:
- Open Revit and create a new blank project.
- Go to Insert > Link Revit.
- Link the corrupted local model into the new project.
- If the link loads successfully, use the "Select All Instances" tool to select all elements from the linked model.
- Go to Modify > Copy/Monitor > Copy Select.
- Copy the elements from the linked model into the new project.
- Save the new project and use it to recreate the local model.
This method works because Revit's link loader uses a different code path than the direct file opener, and can sometimes read files that fail to open directly.
Method 6: Worksharing Monitor and Workset Recovery
If the corruption is specifically in the worksharing metadata (e.g., elements show as "borrowed" by a user who is no longer on the project):
-
Open the central model with Audit enabled (Method 4).
-
Go to Manage > Worksets.
-
Look for worksets with unusual status (e.g., "Not Editable" when no user has them checked out).
-
For each problematic workset:
- Right-click and select "Make Editable."
- If prompted that another user has it, select "Force Release."
- Save the change to central.
-
Go to Manage > Relinquish All Mine.
-
Synchronize to central.
This clears stale ownership locks that can prevent synchronization and cause apparent corruption.
Preventing Future Corruption
Configure Frequent Backups
Increase the number of Revit backups retained:
- Go to File > Save As > Project.
- Click "Options" in the Save As dialog.
- Set "Maximum backups" to
20(default is 1-3). - Click OK and save.
With 20 backups, you have a wider window to restore from if corruption occurs.
Enable Worksharing Monitor
Install the Autodesk Worksharing Monitor (available from the Autodesk Account portal) on all team workstations. It provides real-time alerts when:
- Synchronization fails
- A user loses connection to the central model
- The central model becomes unavailable
Early detection allows users to save their work locally before corruption propagates.
Split Large Models
Revit models exceeding 500 MB are at significantly higher risk of corruption. If your model exceeds this threshold:
- Use Revit links to split the model by discipline (Architecture, Structure, MEP).
- Use Revit links to split the model by building wing or phase.
- Use Worksets to isolate large groups of elements that can be closed when not in use.
Each linked file should be under 300 MB for optimal stability.
Educate Users on Proper Sync Workflow
Establish a team protocol:
- Synchronize to central at least every 2 hours.
- Never close Revit without synchronizing first.
- Never force-quit Revit during a synchronization.
- Report any sync errors immediately to the BIM manager.
- Do not work offline for more than 1 day without syncing.
When to Contact Autodesk Support
If all recovery methods fail, contact Autodesk Support through the Account portal at https://manage.autodesk.com. Provide:
- The corrupted central model file
- The most recent backup file
- The journal file from the session when corruption occurred
- The Revit version and build number (Help > About Revit)
- A description of the symptoms and when they began
Autodesk has internal tools that can sometimes extract data from severely corrupted RVT files that no desktop method can recover.
Source Verification
More Revit Guides
performance
Optimizing Revit Family Files: Reducing Bloat and Improving Load Performance
12 min read
standards
Fixing Missing Parameters in Revit IFC Exports: Mapping and Configuration Guide
14 min read
performance
Optimizing Revit Performance for Large Models: RAM, Pagefile, and Storage Configuration
13 min read
troubleshooting
Resolving Revit Worksharing File Locks and Corrupted DWL Files
12 min read
Related Troubleshooting Guides
Similar troubleshooting content for other CAD tools
3ds Max
•troubleshooting
3ds Max FBX and OBJ Import: Missing Materials, Broken UVs, and Texture Path Recovery
11 min
3ds Max
•troubleshooting
3ds Max Plugin DLL Errors: Missing Files, Load Failures, and plugin.ini Repair
9 min
3ds Max
•troubleshooting
3ds Max Random Crashes: Memory, Driver, and Crash Log Analysis Guide
10 min
Altium Designer
•troubleshooting
Fixing Altium Designer DRC Errors: Common Clearance and Routing Violations
9 min