Revit Tip: Compact Central and Backup Strategy for Workshared Revit Models

Today’s tip: keep your workshared models healthy with Compact Central and disciplined backup management.

Why it matters

• Reduces file bloat and fragmentation, improving open/sync times.
• Lowers risk of data corruption in busy, multi-user projects.
• Gives you reliable recovery points when something goes wrong.

Pre-compact checklist (for server-hosted central models)

• Have all users Synchronize with Central, Relinquish all, and close Revit.
• In Worksets > Users, confirm no one is connected to the central.
• Temporarily disconnect automated backups or antivirus scans on the central’s folder.

Two reliable ways to compact a central (file server workflows)

• Quick method (during sync):
  • Open a fresh local.
  • Collaborate > Synchronize. In the dialog, check “Compact Central Model.”
  • Finish the sync, then prompt the team to recreate locals.
• Full refresh (recommended after heavy cleanup/upgrades):
  • Open the central with Detach from Central and Audit enabled.
  • Save As > Project. In Options, check “Compact File” and “Make this a central model after save.”
  • Archive the old central; instruct the team to delete locals and create new locals from the refreshed central.

Cloud worksharing (Autodesk Docs/BIM 360)

• Server-side maintenance handles compaction; you won’t see the same “Compact Central” option.
• Best practice: users regularly Create New Local, Relinquish all before close, and Publish milestones.
• Periodically clear Collaboration Cache when troubleshooting stale performance.

Backup strategy that works

• Central backups: Set 20–50 backups for active projects (File Save Options). Balance with IT storage policies.
• Local backups: 3–5 is plenty; recreate locals frequently.
• Milestone archives: After major sync + compact, eTransmit to a read-only archive with all links.
• Restore from backup: File > Open > select the model > “Restore Backup” > choose a version. Recreate central/locals after restore.

When to compact

• Weekly on active projects; immediately after Purge/cleanup or large link updates.
• Before deliverables and before upgrading to a new Revit version.
• When central size spikes or sync times noticeably increase.

Risk reducers

• Never copy/move a central with Windows Explorer—use Save As from Revit.
• Avoid WAN/VPN access to a file-based central; use Revit Cloud Worksharing or Revit Server for distributed teams.
• Keep links clean (audit/purge) before loading; compact again after heavy changes.

Operational tip

• Maintain a lightweight log: date, who compacted, method used, backup count settings, and notes. It speeds up troubleshooting later.

Need licensing, cloud collaboration guidance, or add-ins? Connect with NOVEDGE. For Revit subscriptions, upgrades, and expert advice, start here: NOVEDGE | Revit. Their team can help you tailor backup policies and maintenance workflows for your environment.

You can find all the Revit products on the NOVEDGE web site at this page.