A SketchUp model that crashes on opening, or a Revit project that says it cannot be read, can stop an architecture or design practice in its tracks, especially a day before a client presentation or a planning submission. The good news is that both programs quietly keep backup copies, and many “corrupt” files can be brought back without any specialist help. The bad news is that the wrong first move, such as saving over the file or letting someone “tidy up” the project folder, can destroy those copies. This guide explains where to look and what to avoid, and when the real problem is the disk or server underneath.
First: stop and protect what is there
Before you try anything, make a copy of the whole project folder, not just the one file, to another drive. Then work only on that copy. In particular:
- Do not keep re-saving a model that is behaving strangely; each save can replace a good backup with a damaged one.
- Do not delete files with unfamiliar extensions such as
.skbor.0001.rvt. They are often the very backups you need. - If the file lives on a shared server or NAS that is also showing errors or running slowly, stop working from it altogether. That is a sign of a hardware problem rather than a software one.
SketchUp: backup and AutoSave files
SketchUp normally writes a backup copy when you save a model. On Windows this sits in the same folder as the model and has the extension .skb. It is the previous saved version of the model, so it may be missing your most recent changes, but it is often intact when the main .skp file is not.
- Copy the
.skbfile somewhere safe. - Rename the copy so it ends in
.skp(for exampleHouse-v3-backup.skp). - Open it in the same version of SketchUp, or a newer one, and save it under a new name.
SketchUp also auto-saves while you work. If the program crashed before you saved, look for a file whose name begins with AutoSave_. Its location is set under Window > Preferences > Files (on a Mac, SketchUp > Settings). If you have not changed it, it is usually a temporary folder in your user profile, so look there before you restart the computer or run any clean-up tool.
If a model opens but behaves oddly, Window > Model Info > Statistics > Fix Problems can repair some internal errors. Run it on your copy, not on the original.
Revit: numbered backups, central models and local copies
Revit keeps a set of numbered backup copies alongside a standalone project, named like Project.0001.rvt, Project.0002.rvt and so on, with the highest number being the most recent. How many are kept depends on the Maximum backups setting in the Save Options. If the main file will not open, copy the newest backup, rename it to a new project name and try opening that.
Workshared projects are different:
- The central model has a folder next to it ending in
_backup. It holds the history Revit uses for Restore Backup (on the Collaborate tab). Never copy files out of this folder by hand or delete it to save space. - Each team member also has a local copy on their own computer. If the central model is lost or damaged, a recently synchronised local copy can often be used to create a new central model. Ask everyone not to synchronise, and not to delete their local files, until you have decided what to do.
When opening a troublesome Revit file, tick Audit in the Open dialog. Revit then checks the file and fixes what it can. It can take a long time on a big model, so let it run.
When the file itself is not the problem
Corruption in large design files is often a symptom rather than the cause. Be suspicious of the storage if you see any of these:
- Several different files, or files from different programs, start failing at the same time.
- Saves take far longer than usual, or the program freezes while saving.
- Files show as 0 KB, or a whole project folder has gone missing.
- The workstation or server is clicking, rebooting, or reporting disk or RAID warnings.
In that case, repeated attempts to open, audit or copy files will put more strain on a failing drive and can make things worse. Shut the machine or server down and treat it as a hard drive recovery job. For a practice server or NAS holding the shared projects, see our server data recovery page. Do not rebuild a RAID or reinstall the server operating system first; that can overwrite the very data you need.
How a lab can help
When the disk has failed, the first job is to make a complete, sector-by-sector copy of it in a controlled way. Recovery then happens from that copy, which means the original is not stressed any further. From there it is often possible to get back the project folders as they were, including the .skb, .0001.rvt and _backup files that give the best chance of a usable model. It also helps to tell us which projects matter most and roughly when they were last saved, so those can be checked first.
Preventing it next time
- Keep a regular backup of the project server that is separate from it, including at least one copy that is offline or off site.
- Leave SketchUp’s backup and AutoSave options switched on, and do not set Revit’s Maximum backups to 1.
- Archive finished projects and test that you can actually open them from the archive.
If a SketchUp or Revit project is on a drive or server that has failed, call Data Doctor on 020 7394 2529 for a free initial consultation before anyone tries a rebuild or repair.